Agile Testing: How to Shift Left to Get It Right Shifting left means moving towards testing software at the development stage instead of afterward. Testing conducted at the development stage is preventative rather than diagnostic; by proactively dealing with issues before the build moves forward, less time is wasted trying to find these issues later on. Shifting left can solve some of the main challenges in Agile, including catching defects as early as possible and improving code coverage. Some ways to get started with shift left testing are: - Using test automation to improve continuous delivery and minimize problems associated with broken code—for example, by using automated regression tools;
- Encouraging developers to code with testability in mind, which improves the reliability of the testing framework and speeds up the testing cycle;
- Defining quality controls at all stages of the software development life cycle. Such controls lead to corrective actions at the relevant stage instead of later on, ultimately improving the project's health.
It’s important to remember that metrics are still very relevant in the shift-left testing approach. You still need to evaluate tests to improve them, and test metrics provide the evidence required to make intelligent decisions about future software tests. Always gather data from the moment the testing effort begins.
|