How to fix Unstable UI Automation Tests ?
Flaky or unstable automation tests are headache for automation testers. In most of organisation where automation is priority, They have large amount of automation tests divided into the suits. From them lots of test cases are not that stable, specially UI tests. So when overnight automation run triggers and they get report there are few automation tests are red. The guy who analyse report is not sure if that tests case is failed due to bug in build or script issue? Sometime people know these tests are unstable and ignore the report and that way they may miss the bugs. So these unstable automation tests either should be removed or fixed. So How to fix Unstable UI Automation Tests ?
How to fix Unstable UI Automation Tests ?
1. Why are Tests failing frequently ?
- Run Test suit multiple times and check pattern
- If possible, Observe on UI
2. Performance Issue ?
- Page loading taking time ?
- Improper use of waits?
- APIs are slow?
3. ElementNotFound?
- Xpath issues?
- Unwanted flow?
- Element is right there in front of my Eyes but not working.
4. Sequencing issue?
- Tests are dependent
- Not getting expected Data
5. State of Application
- Prerequisites not set correctly
- Execution Start point is not stable
6. Network Issues
Internet is not stable
High usage of Internet
7. Actual Bug !
- Go and report it
- Skip test until it got fixed
No comments