About
The CubicTest "Recorder" plugin provides the possibility to record from a real browser directly into the CubicTest graphical test editor.
It is based on Selenium RC and is actively supported and maintained by the CubicTest team.
Features
- Supports both URL start points and Extension start points (in the latter case, the test browser is "forwarded" by using the Selenium RC Runner plugin to run the test to the start point and start recording from there).
- Starts up a Firefox/Opera browser with a custom profile (no setup necessary except for requiring Firefox/Opera to be installed).
- Injects a context menu in the HTML of the page to record from.
- Populates the graphical test editor in Eclipse directly.
- Records both page element assertions and user interactions.
- Captures as many identifiers as possible on the recorded elements.
System requirements
- Requires that Firefox or Opera is installed.
How to use
- To start recording: Right click in the CubicTest graphical test editor -> choose "Record" (or right click on a Page/State and select "Record from selected Page/State).
This starts up a web browser instance and forwards it to the selected point to start recording. - To assert elements present: In Firefox: Right click on web page elements (e.g. links) and select assert present from the context menu that appears. In Opera: Hold the ctrl key and left click on page elements to get the context menu.
- To assert text present, first select the text in the browser, then right click to assert text present.
- To record user interactions: Do the user interactions as normal (fill in a form, click buttons or links etc.).
- To stop recording: Same as above (toggle the "Record" menu item)
The active page that elements will be put into (the "cursor" of the recorder) is highlighted as "selected" in the CubicTest graphical test editor.
Recommended use
- Use for writing tests for an existing web application.
Limitations
- Has limited support for contexts. Workaround: Record first, then edit the test, creating contexts manually, and drag and drop page elements into their belonging contexts. Another possibility is to not use contexts (e.g. when the recorded identifiers suffice).
- The recorder runs in an iframe to keep track of the recording session. Any pages that A) modifies the top frame or B) changes the window top location will stop / disable the recorder.
- There currently no support for custom firefox profiles or going through a proxy server.
If you need to use a proxy server...
There is currently poor support for this in CubicTest itself.
Workaround: Configure the web browser used for recording manually using the normal web browser preferences. This must be done each time the recorder is launched.
If Firefox is installed in a location other than the default one...
Set the PATH variable of the operating system to include the folder where the firefox binary is located.