Working in many companies as consultant, delivery manager or tech lead I have always seen the same mistakes made in test automation process. I could count successful cases on fingers of one hand. Sometimes people don’t understand the true value of test automation, sometimes just could not organize this process spending lots of money and time without any significant result. I want to share 5 top mistakes aggregated from whole my practice and solutions I recommend for them.

1. 5 easy ways how to ruin your test
automation
Mikalai Alimenkou
http://xpinjection.com
@xpinjection

4. Disclaimer
This talk is based on
personal experience

5. #1. Dedicated automation team

6. It is hard to test
untestable application
Historical scenarios
is not in team top
priority
No team responsibility
for quality

7. #2. Developers are not involved

8. Bad test design and
missed standards
Many decisions are
based on
assumptions
Developers don’t care
and break tests

9. #3. QA responsible for test failures

10. Lack of team
responsibility
Not enough
knowledge for high
effectiveness
Stupid full time job for
QA engineers

11. #4. Missed test strategy

12. Testing efforts are not
distributed
Lack of common
vision on test
automation
Too much efforts in
complex tests

13. #5. Invite your own framework

14. Theoretical needs are
covered in framework
“Senior” QA engineers
leaving when
framework is done
ROI is not always taken
into account

16. @xpinjection
http://xpinjection.com
mikalai.alimenkou@xpinjection.com