Learn to adapt your test cases into a more agile context
- Matthew Archer
As organisations move to a leaner way of working it’s not uncommon for teams to blend both traditional and agile practices to create their own unique software delivery pipeline. From a software testing perspective, this can sometimes mean continuing to use manual test scripts.
This bringing together of new and old is often accompanied by a fresh set of challenges and risks. For many teams, gone are the days when hours or even days can be spent creating and maintaining manual test scripts. The pace of agile software delivery will rarely tolerate it.
And here lies the problem. If it is the desire of your organisation or team to use manual test scripts, how can you do so in a way that is compatible with the values and pace of agile software delivery?
This online video course explores how this incompatibility risk can be minimised by challenging you to think about what information is included in your manual test scripts, the language used to describe that information and whether a manual test script is the right location for this information.
In this course you will learn how to
Highlights the risks associated with test scripts allowing you to evaluate whether these risks are likely to become a reality for you and your project team
Apply the YAGNI principle is applicable to software testers and how to apply this principle to removing the unnecessary information from your test scripts
Refactor duplicate steps in your test scripts into a single common location
Optimise your test scripts by merging and generalising less important steps while identifying more important steps, allowing you and others in your team to quickly understand the purpose of your tests