Last month, QASource and Sauce Labs partnered together to present a webinar, Reducing False Positives in Automated Testing. We wanted to provide you with some answers to the most commonly asked questions in response to this webinar. Please feel free to comment with additional questions and let us know how the techniques to reducing false positives have impacted your automation testing.
Q: Are there specific tests to avoid while automating to eliminate false positives in automated testing?
A: When automating tests, first you must define your goal to determine which types of test to automate. While setting your goal, you should avoid the following:
- Unstable areas or areas with frequent UI changes
- Scenarios which are not supported by your automation tool. For example, if you are using Selenium, you shouldn’t go for tests that require interaction with Windows 32 components because Selenium does not support desktop based applications.
- Areas which have been identified to have performance issues
- Areas which cannot be identified using unique locators
Q: How do you identify a well written automated test?
A: A well written automated test is defined by the way we structure our test script, workflow, and tear down fixture. The script should only contain these strips and verifications points. This will allow test cases to have 1:1 mapping. In addition, well written automated tests should not contain any hardcoded data and exceptions should be handled. All well written automated tests should follow best coding practices, commenting and naming conventions. (more…)