Why I Created a Selenium Recorder But Rarely Use it myself?
I am against using recorders for test automation, except for two situations:
- Training
“Selenium IDE is the place to start with Selenium, but it is Selenium on training wheels” — Jason Huggins, the creator of Selenium v1 at AAFTT Workshop 2009
However, with the advancement of Browser (Chrome) and testing tools (such as TestWise I created. By the way, iTest2, TestWise’s former name, was demonstrated at this AAFTT Workshop 2009), I found using recorders was no longer necessary. Attendants of my training verified that.
2. Writing tests with many similar steps
This is very rare. I only remembered one case. It was testing a set of law document pages (generated from a software) containing many “Yes or No” radio buttons. Recorder helped me with that.
As I stated in my book ‘ Practical Web Test Automation’ 10 years ago: “test script recording is only useful if the steps are refactored to maintainable form immediately”. If you do a google search of ‘record/playback’ review, it is almost all negative. Yet still, there are no short of ‘new test automation record/playback tools’.
Record/Playback scripts are notoriously costly from a maintenance perspective. — ‘Agile Testing’ book, p315.
