How Is Agile Testing Different?
Software development with Agile helps vendors significantly reduce time-to-market, incorporate user story feedback faster, and generate returns more quickly from the first iteration onward. At the same time, Agile testing requires changing both the mindset and tools.
How is testing different with Agile?
First, Agile development is highly iterative and incremental. There is no big upfront test planning, and test cases are created within each iteration. Moreover, the testing is performed – not against detailed requirements, but against high-level product backlog items that are often based on user stories extended with just-in-time details.
Second, Agile involves close collaboration between business and development team members. Ideally, it should be a cross-functional team of testers, developers, and even engineers – working closely together. Real-time conversations are used to exchange information and make decisions, helping to reduce documentation as much as possible.
Finally, the highest priority of Agile development is to deliver valuable, functional software in the shortest time possible.
Considering the fact that most testing tools support the “phased” approach to software development, from planning to deployment,
It’s time to forget about old tools. Instead, look for something more lightweight, and that is in line with your new approach. A way that allows you to do short planning and test feature-by-feature during the next 1 to 4 weeks.
Testuff is a handy tool whether you are using Scrum, XP, or a pragmatic mix of Agile methodologies and practices. With Testuff you can easily create tests just-in-time, organize test cases by iterations and releases, and see the progress for each created user story.
Let’s go through all these steps.
During Iteration planning meetings, it’s easy to take all user stories from the Iteration backlog and add them to Testuff using the Requirement dialog.
There is no need to create separate requirements; the whole list of user stories can be added within one dialog box.
The next step for the development team is to create a set of tests for each user story.
For that purpose, use the Assign more tests tab for the selected user story in the Requirement dialog.
- In the Assign more tests tab, right-click the empty area.
- Click Quick add tests in the popup menu.
- Select default suite and press Enter in the Suite selection dialog.
With the Quick Add Tests dialog, you are able to sync all the required tests to the user story pretty quickly without going too deep into details.
- In the Tests box, type in tests, and click OK to confirm.
- Then to assign a test to the user story, right-click a test and click Assign tests to in the popup menu:
In the example above, the tests are added to the Sprint1_US-02_Edit account story.
Click the Tests in this requirement tab to verify that tests are assigned.
The tests can easily be linked with releases and iterations through the Lab dialog.
What makes Testuff convenient is that tests can easily be reassigned to different iterations, which reduces the time and effort required for regression testing.
When a user story is implemented, it’s time to run all your prepared tests. This is also easy to do from the Requirement dialog.
- In the Requirements tab, click the user story you want to test.
- Right-click a test in the Tests in this requirement tab.
- Click Run in the popup menu, or click Mark test as passed (if you’ve already run the test and it passed).
For each user story, we have statistics, including: how many tests were assigned, how many of them passed or failed, and how many open defects still exist for any given user story.
Testuff helps development teams plan, design, run, and track results for each user story in an easy and fast manner. Agile development with Testuff becomes truly rapid and agile.