Recently, I attended to a webinar called “Where Agile Testing and Test Management Collide” http://www.pushtotest.com/agile-testing-test-management, that mainly focused on two tools for Test Management and testing: Zephyr and TestMaker.  Basically, Zephyr is Test Management software and TestMaker is a tool for performance and automated testing (the demo of these two products took most of the time of the webinar, my opinion is that it was missing more information about how Agile Testing is performed).

In this post I will first analyze what Agile software development is, how testing in this model is achieved, and what features are needed in a Test management tool.

Agile Testing basically adapts to Agile software development.  If you do a search for Agile development you will find the “Agile Manifesto”, written by a group of developers in 2001. According to the Manifesto, there are 12 principles of the model:

    1.       Satisfy customer through early and continuous delivery of valuable software
    2.       Welcome changing requirements even late in development
    3.       Deliver working software quickly
    4.       Business people and developers work together daily through the project
    5.       Build project with motivated individuals
    6.       To obtain information the most efficient method is face-to-face conversation
    7.       Working Software is a measure of progress
    8.       Agile processes promote sustainable development
    9.       Continuous attention to technical excellence and good design
    10.   Simplicity is considered to be the art of maximizing the amount of work not done
    11.   The best architecture, requirements and design emerge from self-organized teams
    12.   At regular intervals, team should talk about how to become more effective  and adjust their behavior 
    (Agile Manifesto)

In the Agile model, a project is divided in iterations that include: analysis, design, development, testing and acceptance testing when the product is demonstrated to stakeholders. Each one can last up to four weeks. The measure of progress is working software, so the goal of each is to have an available release with the minimum amount of bugs.  At the end of each iteration, stakeholders and a customer representative need to review the progress and redefine the priorities of the project. (Wikipedia – Agile Model )

In Agile development, a project needs to adapt to changes quickly, there is not enough time for detailed documentation. When developers find questions, a customer representative needs to be available to respond and stakeholders need to produce documentation as required.  As principle #6 in the manifesto mentions, face-to-face conversation is the most efficient way to obtain information; this applies to communication with the client as well as within the team.  In Agile projects, there is usually a quick, daily meeting attended by the whole team, a customer representative and any other stakeholder.  During these meetings, each member reports what they did the day before, develops the plan for the current day and reports any blocker.  (Wikipedia – Agile Model )

In an Agile model, the testing team needs to adapt to a rapid development cycle, test with a customer perspective and have a constant communication with the whole team. Testers need to provide testing results as soon as possible so the developers can resolve any bugs; thus producing the least number of bugs at the end of an iteration. As mentioned before, in the Agile model communication is essential; therefore, the testing team needs to have a good relationship with the developers.

In Agile development, the test manager needs to ensure that the testing team is reporting issues, communicating these issues to the development team and giving daily reports about critical issues. See the testing cycle in the following graphic:

 

(Zephyr)

In this scenario, a test management tool ideally needs to have the following features:

  • Divide testing into Releases/Iterations
  • Link test cases with requirements
  • Assign test cases to testers
  • Create, edit and reuse test cases
  • Link test cases with bugs
  • Reporting 
  • Allow sharing of the results with the whole team

These features will help the Test Manager to adapt testing to a rapid development cycle and to keep the team updated with the current status of the project.  In an Agile model, “the measure of success is working software”, so it is very important that the Test Management tool helps to keep the team informed about critical issues in each iteration.

Finally, I feel that a good Test Management tool is very helpful in Agile Software development; however, the Test Manager should never lose attention of the other aspects, like testing with end-user perspective and having good relationships with developers and clients, needed to achieve a collaborative and successful project.

References

Agile Alliance: http://www.agilealliance.org/

Agile Manifesto: http://agilemanifesto.org/

Wikipedia Agile Sofware Development: http://en.wikipedia.org/wiki/Agile_software_development

Wikipedia Agile Testing: http://en.wikipedia.org/wiki/Agile_testing

Manage Agile Testing Methodology Effectively with Zephyr: http://www.getzephyr.com/resources/zephyr_qa_methodologies.php