However, also in agile projects, the product has to be tested sufficiently. Agile testing means that when selecting, planning and implementing test activities, the team follows the principles of the Agile Manifest and consequently applies them to testing.
In an agile project, especially when working according to Scrum, every iteration or every sprint aims to produce a potentially shippable software, also called “potentially shippable product”. For the test, this means the following: Testing needs to take place in sync with the iterations. Therefore, all necessary test and QS activities have to be included mandatorily during the sprint.
In order to succeed permanently and sustainably, testing has to be accelerated and automated by tools as far as possible. Manual testing remains important, as well. In particular, there is not enough time for every feature that is developed from scratch to realize the related test automatization in the same sprint.
Apart from an automatization of the test implementation, test management requires also a good and efficient tool support of the procedures and activities, too. An especially suitable tool has to be able to quickly and easily answer two significant questions every team member will have:
- Which test-relevant tasks are awaiting me?
- Which level of quality has our product or do we have a “shippable product”?
In the .NET environment, the Microsoft Team Foundation Server (TFS) is the often used platform for collaborative software projects. Via the TFS projects can be planned, created and maintained.
The complementary use of a specialized agile test management tool, however, offers some advantages. A new representative in this category is TestBench Cloud Services.
TestBench Cloud Services consequently realize the objective to provide the team with a continuous feedback on the state of the test activities of the project quality in a maximum simple way. For this purpose, the system is not only able to capture and maintain test tasks, test cases and defects but also epics and user stories. The tool creates the link between all elements so that all information can be directly read from the elements relevant to the agile team, the user stories: Test procedures, test data, test results and defects.
TestBench Cloud Services display to the user not only tasks to be done but show also their urgency and cumulate this information even to the level of user stories and epics.
The states of the test cases are visualized on all levels so that the current state of the test results is readable at any time. In doing so, the reference between a found defect and the related user story is not visible at any time:
In addition to the mistakes found but not yet corrected, the product quality secured by tests is also described. In this context, the product quality is calculated from the number of test cases “passed” in relation to the user stories covered with deposited test cases.
Conclusion: TestBench Cloud Services provide agile teams with a quick and easy solution for organizing tests and quality assurance in an agile way. With this tool, the agile team needs not to invest in any resources in order to complexly adjust or retrofit a generic task management tool. The team can fully concentrate on handling the actual tasks and leave the test management and reporting to TestBench Cloud Services, instead.