@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 🙂
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic.
Learn Exploratory TestingYou Don't want to Miss this Event
Learn the basics of Exploratory Testing in this insightful session
Privacy & Cookies
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.