Daniel Knott, a software quality assurance expert, recently made an interesting point about why total automation is unhealthy — "Customers don't care if your software is automated to 100%. They care, for example, if the final product still has critical issues."
When preparing a test team for automation, be sure to allow enough time for them to work with the system before the start of actual testing. Daniel Knott offers the following advice to avoid making this mistake:
- Start by sitting down and making a plan. What do you want to automate? What are the critical parts of your product that needs to be automated?
- Determine the things that are likely to change often, and start simple — don't write too many tests for complicated features.
- Check those features that people interact with first.
- Talk to your developers; they know how a product is supposed to work. Discuss with them what features you should focus on first and what features can be tested later.
Conclusion: automation is great, but you must be careful not to go overboard.
Learn more common mistakes every QA manager should avoid - in my team’s recent blog article.
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.
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)