The software industry is changing fast. Many of the companies software testers work for have to re-adjust their working patterns, release cycles and project approaches in response to this change. It’s never been more important to remain relevant to the company you work for. Yet a surprising number of people are ignoring the needs of the business they work for, clinging to outdated approaches to work and running away from change.
As DevOps is now a new important approach for rapid software delivery, how do you perform software testing in this context of reduced cycle times. In his article, Gopinath C H explains how to perform testing in continuous integration and continuous deployment workflows, providing examples based on the Visual Studio 2015 and Team Foundation Server tools.
A test monkey is an automated tool uses for random application testing. Unlike automated regression tests, test monkeys explore the system in a new way each time the test is run. In the book ” Experiences of Test Automation”, there is an interesting chapter that explains the benefits and limitations of test monkeys.
10 years ago, Dan North first came up with the idea of Behaviour-Driven Development (BDD): using examples in conversation to explore the behavior of systems, then carrying those examples into code. Since then, we have learned a lot about how BDD works, how it works best, and how it can fail horribly! Even the most experienced BDD practitioners have learned a lot from their failures… but what were they? And how are we failing now?
TestInsane Technologies has created a repository of software testing mind maps. A mind map is a diagram used to visually organize information. It is often created around a single concept to which associated representations of ideas such as images, words and parts of words are added. Major ideas are connected directly to the central concept, and other ideas branch out from those.