First, we need to record the script by going through the instrument manually. Each object in the instrument has an object name with unique properties. The object name is displayed in the script when the tool generates the code. The script generating options we use record the tester’s actions such as keystrokes and mouse clicks as they are applied to the objects on the screen. These options make the script more understandable when read and allow us to more easily maintain it. Once the script is recorded the first time, we can play it back. After the script runs, the results will be displayed in the results window. If the script runs through correctly, the results show as passed. If the instrument has any changes or does not run, the script fails and the results are displayed as failed.
Record and Playback buttons are the red dot and the blue arrow:
If a script stops during playback, we know that there is an issue. When it is determined to be a defect, we enter the issue in our standard bug tracker. If it is not a defect, for example an intentional change to the instrument, we have to modify the script to make it run. This requires maintenance of the scripts as the versions of the instrument keep changing. It is not very difficult, but scripts have to be updated on an ongoing basis. One can edit the code manually to comply with the screen or re-record portions of scripts to incorporate the new information and allow the script to continue running.
First, it is important to note that automation tools have a variety of checks that can be used for more test coverage. Without checks, you’re only testing navigation. Adding checks lets you confirm that the
Application is validating input, performing calculations correctly, saving data reliably, and reporting
accurately, by comparing actual responses to expected responses and reporting any discrepancies.
Here are some of the checks that can be used in TestPartner.
Bitmap Checks: These checks compare a bitmap in the target application with one that was reviously
defined. Bitmap checks are used to verify the appearance of toolbars, the desktop, and other windows
that contain non-textual information.
Content Checks: A content check enables you to verify the contents of controls that the tool supports.Currently, tables and list controls in a Windows-based or Web-based application are supported. List controls include list boxes, drop-down lists, combo boxes, and various “tree” type controls, such as those used in Windows File Manager and Windows Explorer.
Field Checks: Field checks enable you to conduct specific types of text comparisons, including date and time, of individual fields you select in a window or area.