Recorder
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 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. Some driver’s (like Sahi) provide an option where you can abstract out locators before generating the 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.
We encourage users to record small units of functionality. These could then be reused in other scenarios by reusing the class that contains the generated scripts.
This is why you do not see a recorder button anywhere in Twist other than in the quick-fix option for a business workflow step.