April 15, 2018 at 5:32 pm #19170@darwinOnly available when logged in
As bad automation test suites are not easy to notice, I would like to hear your thoughts on how to identify the problems with bad automationApril 22, 2018 at 9:54 pm #19231@darwinOnly available when logged in
@alishahenderson, when a test run has a 40% of fail rate, of course, it is the responsibility of the AT engineer who created such tests to make the code more reliable and thereby it is easy to identify a bad automation test suit, also code quality will be reviewed with every pull request he makes.. But when there is a 100% pass rate one cannot be always sure that the application under test is bug-free,
So I would like to give a list of suggestions to go through and check if the tests are crafted in such a way, else more likely it would lead to a bad test automation.
– Being more specific on expected results
– Tests should follow the user approach rather than taking an easy way
– Review the test results (ex: screen-shots)
– Assess the test suite and tests frequently to ensure coverage.
If there are more points to add, feel free to add your comments 🙂
You must be logged in to reply to this topic.