As you interact with your application, the Test Recorder records the interactions and displays them in the test case table from which you started the Test Recorder.
The process works as follows for the sample zip code application. This sample is available in the samples that ship with General Interface. To open the sample project, choose Project > User Projects > samples > WSDL_Mapping_1.
- Enter a zip code, and a change event is recorded with the target object #zip. The change event is added as a row in the test case table tab from which you launched the Test Recorder. The event action is jsxchange, and the target is #zip. The Test Recorder also records event metadata, shown in the Value column, which allows the Test Recorder to play back the event.
 Click here to expand screenshot...
- Click Find City and State, and a new event is added to the test case table. The event action is jsxexecute, and the target is #lookupButton.
Click here to expand screenshot...
- Another event is added when you dismiss the pop-up success message.
Click here to expand screenshot...
- To verify that the application is working, click the Wait button. This puts the recorder in "wait" mode. The next click on the application will generate a wait test case instead of recording a model event. The recorder automatically picks what it determines to be the most appropriate command. You can change the command later, if needed, in the test case table. As shown in the next figure, clicking on a text box generates a jsxwait_value event.
Click here to expand screenshot...
In the sample zip code application, the target it #city and the value is "San Francisco." This means that when the action is replayed by GIPP or GITAK, it will wait until the value of #city equals "San Francisco."
When constructing test cases, it is best to interact with the application and then do a single wait or assert operation. For a list of wait actions, see Working with the Test Case Table.
When the recording is complete, you can go to the test case table and make modifications. In general, the recorder makes a best guess as to your intentions; however, because many interactions have multiple interpretations, you may need to manually edit some entries.
For example, the next figure shows the result when the Wait button was clicked twice during recording. By returning to the test case table, you can delete the second instance of the wait event.
Click here to expand screenshot...
- To keep the generated test cases, save the test case table. GIPP test cases require a .js extension and GITAK test cases require an .html extension.
- After saving the recorded file, you can run the test case by launching it in GIPP or GITAK. Before doing so, make sure that GIPP and GITAK are configured. To do so, choose Tools > IDE Settings. Click GIPP & GITAK and specify the appropriate installation directory.
- Click the Launch GIPP or Launch GITAK button in the builder window.
 | Clicking the Launch in GIPP button launches only the current file. To run GIPP with all of the available test cases, choose Project > Run Project in GIPP. |
|
|
