Roadmap for Success: Agile Testing Methods

Software testing requires a tight focus. It's easy to try to test too much. Before you start to develop test cases in a system and, obviously, after you have taken the time to learn the product reasonably well. You need to figure out what you might test, then what you should test, and finally what you can test. Determining the answers to these questions and to find new perspectives for the planning of testing of software products in agile projects was objective for writing this Master Thesis. This Master thesis provides directions to reach a desired destination, software is tested and accepted. Test strategy is highest level activity with software testing. Test strategy determines all of testing activities. Test plan Test plan describes how the testing will be done and what kind of environment, tools and methods will be used. Software projects usually proceed with one of the selected process model. The most common process models split project to different phases. Project models can be used in several variations, but general in all models have separate planning, specification, design and implementation phases. All of these phases contain also testing activities. All project members have own role in project. Software testing is and will continue to be a fundamental activity of software engineering. To engineering the test process, we need to collect evidences for such information to be able to find the most effective pattern for testing a system. This can routinely do, when for instance functional testing based on the requirements is combined with measures of code coverage adequacy. Practices need to be backed up by a systematic effort to extract and organize recurring and proved effective solutions to testing problems into test patterns, similarly to what is now a well-established scheme for design patterns approaches. Keywords: Software testing, Scrum, process model, testing levels, test plan, testing technique