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 Quick Add Requirements dialog.
There is no need to create separate requirements; the whole list of user stories can be added within one dialog box. To do this, go to Requirements tab, click on the three dots More Actions menu at right of the Add Requirement button and select the Quick add many option. The Quick Add Requirements dialogue will display where you may outline all user stories according to your backlog.
The next step for the development team is to create a set of tests for each user story.
For that purpose, go to Tests tab page, if you do not count with a Suite for this purpose you may add one clicking on the Add Suite button.
In the Quick Add Tests section, you may add all the required tests to the user story pretty quickly without going too deep into details.
Once you are done adding your tests click on the Create button to save the new Suite with all the tests.
Now we need to assign those tests to our user stories. Go back to the Requirements page, select the desired user story and click on Click to assign tests button. The Assign tests to the requirement dialogue will popup with all available tests. To ease your tests assignment, you may filter by suite as displayed on the following image:
Select those tests that will be assigned to the user story and click the Assign button as shown above. In the example, the tests are added to the Sprint1_US-02_Edit account story.
Verify now that the tests are assigned.
The tests can easily be linked with releases and iterations through Labs.
Create the planned sprints as labs form the Labs page clicking on the Add Lab button. The new labs created will be displayed left of the screen. Now select the Sprint where we will add the tests of their correspondent user story and click on the Click to assign tests button. The Assign tests to the lab dialogue will popup. Once again you may filter by suite in order to appropriately select the user stories test.
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 Requirements.
- In the Requirements tab, select the user story you want to test.
- Hover the test you want to run and see below among others the Run menu option.
- Click Run to track the test execution time and result, or check mark the test and from above menu mark the test as Passed/Failed/Blocked/Won’t Do.
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.