Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a web application that we want to start running regression tests on, and one of the things I'm supposed to look for when choosing an alternative is a tool that has a recorder. However, I get the general feeling that it is frowned upon, and that writing tests in code is preferred. What are the eventual disadvantages or advantages of using a record and playback tool for regression testing?

share|improve this question
up vote 7 down vote accepted

I would not recommend record and play for regression testing for following reasons

  1. The tests would record un-necessary steps depending upon the level of recording present in tool. e.g In some applications selecting a combobox would be recorded as clicking it first and then selecting it. Sometimes it might be desirable sometimes not.
  2. The objects might get duplicated and unorganized making the test very difficult to maintain.
  3. Anyway to implement the logic and iterations you need to come down to code.
  4. You know what you are doing exactly when hand-coding the test.

I would say its like hand coding a website even though you have a WYSIWYG editor at your disposal. For learning and beginning with a tool and see its constructs you can use record and play but to make stable, maintainable and standard based tests you should hand code it taking help of record functionality if required.

The advantages would be

  1. Easy for beginners. Takes less time to get started.
  2. Faster test development (though eventually maintenance and debugging time would over-weigh this advantage)
  3. Cool to demo to your manager to persuade him to buy the licenses. :)
share|improve this answer
Another serious disadvantage is that they are very fragile. Just the simplest change to the application often breaks a dozen tests, even though the application still works as intended. – Pete Jan 4 '12 at 9:52

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.