Test scripts can be built easily with web2test. The tester activates the “record mode”, and from now on all of his actions within the context of the current component of the web application will be recorded. Afterwards these recorded event sequences can be played back in the web application
On this level of tests (replaying event sequences) only the detection of errors is possible witch results from the lack of a precondition (e. g. button or edit field missing or page/following page is not loadable). These tests are quite powerful, but for “true” functional testing are not sufficient enough.
At this point the “Checkmode” will come into play. In this mode, recording events is suspended. Instead, the mouse cursor is tracked and the component under it is highlighted.
When you click on the component, a check for the component is recorded using the value that is currently displayed.
There are different kinds of checks that can be performed. Which kinds of checks are applicable depends on the selected component. Some components can be enabled/disabled, so a check about “enabled state” only makes sense for button, input and select elements.
Clicking on a component with the right mouse button while in check mode brings up a menu of applicable checks for this component. Select one of the items to create the respective check.
The following list will give you an overview about all applicable checks for components:
- Text
- Href attribute
- Value attribute
- Name attribute
- Id attribute
- Class attribute
- Title attribute
- Src attribute
- Alt attribute
- Lang attribute
- Style attribute
- Width attribute
- Height attribute
- Selection
- All items
- All items with selection
- Geometry
- Enabled state
- Image
An overview about each valid HTML tag an all reasonable checks can be found in the manual, chapter 4.6 Checks for HTML tags.
Additional possibilities for enhanced checks can be found in the blog article: Browser Interface web2test - continuation
