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 20, 2018 at 11:39 am #19218@alishahendersonOnly available when logged in
You start a new business and get delivered an automation project built a few years ago.
Various teams worked on it during this time and created a few thousands of tests.
The tests run with a 40% fail/error rate.
The code has
- it holds various applications (mobile site, desktop site)
- Various static delays and implicit waits
- classes with thousands of lines of code
- tons of duplication
The page object model is implemented inaccurately with each page class having different rules for clicking, typing, getting the value of each element.
The test environment is shared with other manual test teams.
The test data is very challenging to configure and recreate.
It is your responsibility to clean the project up, to stabilize it by reducing the fail/error rate and to bring the project in shape.
You must be logged in to reply to this topic.