-
AuthorPosts
-
August 13, 2015 at 12:09 pm #9031@ronanOnly available when logged in
I read a blog post recently and came across these slides on the sins of test automation.
It seems to be a popular way of discussing some aspects of testing that you should avoid with automation. What do you make of the list? Do you think it’s a fair reflection on what you should not do in automation or are they missing something?
1. ENVY
Flawed comparison between manual testing and automation2. GLUTTONY
Over indulging on commercial testing tools3. LUST
Loving the UI so much that all tests are executed through the UI4. PRIDE
Too proud to collaborate when creating tests5. SLOTH
Too lazy to maintain automated tests6. RAGE
Frustration with slow, brittle or unreliable tests7. AVARICE (GREED)
Trying to cut costs through automationAugust 17, 2015 at 7:24 am #9047@bas-dijkstraOnly available when logged inI think this sums up most of the traditional ‘dont’s’ of test automation rather nicely.
The only improvement I would suggest is to replace ‘overindulging on commercial test tools’ for gluttony with ‘trying to automate all tests’. That’s something I see happening far more often.
To quote Alan Page: you should automate 100% of the tests that should be automated. Nothing more, nothing less.
August 17, 2015 at 2:29 pm #9060@dlongmanOnly available when logged inThat’s a great list! Bas’ replacement for gluttony sounds like a good one to me. Not sure where it would fit but another anti-pattern I’d add is running all the tests, all the time just because you can even though they are not 100% reliable, then spending hours reviewing the failures.
August 31, 2015 at 12:57 am #9193@alexsiminiucOnly available when logged inHOW ABOUT IGNORANCE ?
Ignoring the fact that test automation projects are development projects, ignoring all development good practices when creating test automation scripts.I dont think that ignorance is a sin, though.
Alex
-
AuthorPosts
You must be logged in to reply to this topic.