Back

Details for testing

Any defined story may have various impacts on different aspects of the product. Different people may have different viewpoints regarding a story. So, a tester needs to put himself in different contexts such as business people, programmers and everyone involved in the product. In this way, they can design tests that consider all of the impacts of the story.

One good practice in software development is Test Driven Development (TDD). By applying this approach in an Agile framework, coding tasks and testing tasks are written at the same time in iteration planning. Time is estimated for all the tasks by team members. In this way, the development is driven by test cases. Testing tasks may be completed sooner than development tasks to give the programmers guides on how to develop the code. It is also possible that development and testing tasks are defined and merged into one task. Tasks for unit testing and integration testing should also be included in the programmers’ tasks.

Another concern is gathering test data for testers. As it may take quite a lot of time and may need contact with people outside the scrum team and organization, test data is better to be obtained and gathered in the release planning phase and before iteration planning.

When committing for the next iteration, it is important to commit to the number of stories that can be coded and tested completely in the incoming iteration.

Recommended Further Reading

The following materials may assist you in order to get the most out of this course:

Translate »