10 WAYS TO KILL AUTOMATION TESTING ON YOUR PROJECT
Bernie Berger
QA & Test Strategy Leader | Risk-Based Quality | Software Testing Governance
1. Make sure everyone on the team has a different opinion on what the objective of the test automation is.
2. Start immediately by writing automation scripts before worrying about planning an overall automation strategy, which is just a waste of time anyway.
3. Let developers write automation tests whenever they have some spare time.
4. Automate all test cases for 100% coverage.
5. Make sure all tests are automated from the UI.
6. Keep environment and configuration variables in the tests themselves.
7. After the first test run, there’s no need to monitor the test results anymore. The first time is good enough.
8. Keep tolerance values for validation at 100%
9. Write your automation scenarios sequentially, so that the start point for a test is dependent on the result of the preceding test.
10. Expect a quick ROI because everyone on the team is a professional
IT Test and Quality Management
5 年????????
Principal QA Engineer @ CentralReach | CSQE
5 年Amen! #12: assume your automated tests are bug free since, well, they were written by Quality Assurance People
Sr. Director of Business Development
5 年11. You don't need skilled people. Any summer intern can write your scripts for you