A Recorder allows you to record your interactions with the application you are testing and generates the underlying test script which can then be played back.
Twist supports recording of user interactions on a graphical user interface using capabilities provided by the underlying Driver that you have chosen for implementation. Sahi, Selenium RC 0.9.2 and Selenium 2(Webdriver) provide recording capabilities on web based applications. Frankenstien supports recording on Swing based applications. The SWTBot driver does not currently provide recording capabilities.
Using the Recorder does help in getting started with your test suite quickly however it is not a recommended approach to building out your test suite.
Potential fallouts are :
- Test data and object locators are by default hard coded in a recorder generated script.
- There is limited opportunity for reuse resulting in greater duplication of code
How is the Twist Recorder different?
You can start using the Twist Recorder at any point in your scenario. The recorder plays back all the previous steps and it will bring the application to the state where you want to start recording your actions. If you have preconditions as contexts in scenario, Twist ensures that all such contexts are executed before it starts recording, and also to cleanup post recording. For more information please see Recording in Twist.
We encourage users to record small units of functionality, which can be expressed as an intent of a step in a typical Business Workflow. Having such intent steps, allows it to be reused in other scenarios by reusing the method and class that contains the generated scripts.