Agile Testing – the side of the story R&D Managers tend to forget

Is your company running at least one Agile project these days? I would be very surprised if it wouldn’t; but the real question is how has this modified the way you – the tester – are doing things differently in order to match your ways to this “new beat”.

My experience with Agile Testing has not been as extensive as I would have liked, but on the other hand I’ve had the chance to experiment with multiple teams and this helped me reach some good pointers that are starting to become my set of best practices whenever I jump into a new Agile project.

My 4 Agile Testing Commandments are:

1. Multidisciplinary teams shall include testers.
Make sure testing is in the picture all the time. When working on any task testing should be an integral part of the task, not after the task or in parallel to the task but as part of the task.
As a principle, tasks cannot be marked as completed until the testing aspects have not been completed too.

2. Stand alone testing operations should be stories by themselves.
If you need to perform benchmark, SOAK testing processes or any other important and extensive operation include them as part of your stories. Make sure you and your team understand that when working Agile all the operations around the product (including tests) are managed as a single project.

3. Take responsibility for the unit testing aspects of the operation.
If all your life you’ve told yourself that your work is Testing and not Quality Assurance, this is your opportunity to change it.
Take responsibility for the Unit Testing, if possible implement a TDD (test driven development) process.
Since you will need to make sure your application is stable all the time, you will need as much help as possible and unit tests (running each night!) may be just what you are looking for.

4. Automation is a must.
Now more than ever as you need to have a stable product all the time, make sure your product is conducting regression testing daily.
If your company is serious about Agile make sure they understand that this means budget and headcount for automation (GUI, API, or any other kind you can manage).

There are some more tips and best practices, but these are the ones that come handy all the time. Remember that Agile (development and testing) is about learning and adapting throughout the process.

Keep an open mind, work focused on the next release, and make sure you are ready to (at lease theoretically) release your product at a moment’s notice.

Remember to enjoy (having fun is also part of the Agile principles).

About PractiTest

Practitest is an end-to-end test management tool, that gives you control of the entire testing process - from manual testing to automated testing and CI.

Designed for testers by testers, PractiTest can be customized to your team's ever-changing needs.

With fast professional and methodological support, you can make the most of your time and release products quickly and successfully to meet your user’s needs.

Trackbacks/Pingbacks

  1. Can PractiTest support agile test management? | PractiTest Blog - October 19, 2010

    […] are books that talk about this, and Joel wrote about agile testing in his blog. But in the end there is nothing like the experience from working with many […]

Leave a Reply

shares