See whether traditional testing works better
Here’s a bit of a curveball: the best tip for your Agile testing may be resorting to regular testing. It is a much slower, but also more predictable methodology that makes it easier to ensure high test coverage.
Pilot and Test
Take up Continuous Quality
Adopt shift-left testing
Shift-left testing focuses on performing tests earlier in the lifecycle with a heavier emphasis on unit tests rather than end-to-end or UI tests. This often involves developers writing and running tests before the code even makes it to the QA team.
Adopt shift-right testing
Shift-right testing is post-release testing in the production environment. It also works well with our daily release strategy where we may have changes of different risks and/or known errors. Sometimes, these known issues can be severe enough for the new feature to break existing functionality.
Eliminate bias
Don’t put off covering legacy code
Get your automated tests straight
Adopt Infrastructure as Code
Adopting Infrastructure as Code considerably freed up everyone’s work schedule. The test environment is now created automatically upon new code delivery. The same environment can be used by multiple QA specialists in parallel for running manual and automated tests. Such auto-generated environments practically mirror the production environment, eliminating the need for a dedicated replica (stage environment).
Move to Scrum-minded test management solution
Thank you for reading! You are welcome to learn more about Scrum in Agile testing and my team's experience here
If you want to follow my testing learning journey, follow the "Software Testing Talks" groups I created on Reddit and Linkedin. I share the most interesting QA discussions I find on the web and insights I get during testing work and studies there.
I am also happy to hear your feedback, suggestions, or ideas about what you would like me to write more about. Don't hesitate to text me if you want to say hi or discuss something.
Top comments (0)