From Seapine Labs

The best and easiest way to create a script to test an application is to record it. During recording, QA Wizard Pro captures the actions you perform as you interact with the application. After a script is recorded, you run it to test the application. During playback, QA Wizard Pro compares the application against the version you recorded against. If there are differences, the scripts fails.

Contents 1 Creating a workspace 2 Selecting the default Web browser 3 Recording scripts 4 Understanding recorded scripts 5 Running scripts

[edit] Creating a workspace

Workspaces organize scripts and the reports and datasheets related to the scripts. Your use of workspaces depends on your organization’s testing process. You may use only one workspace for each application or use multiple workspaces to manage each functional area you are testing in an application. You must create at least one workspace before you record scripts.

[edit] Selecting the default Web browser

You can record and run Web scripts using Microsoft Internet Explorer and Mozilla Firefox. You can run scripts using either browser, regardless of the browser used for recording.

If the application only supports one of the browsers, record and run scripts using the supported browser. If both browsers are supported, you can record scripts in either browser and run them in both browsers to ensure that the application performs consistently.

1. To select the browser, choose Tools > Browser and select Internet Explorer or Firefox.

[edit] Recording scripts

Recording a script creates a new script and captures actions as you interact with an application. The scripts you record provide a baseline for application testing. After recording, you can modify scripts to develop more complex testing scenarios.

Careful planning is the key to successful automated testing. Keep the following in mind when planning a recording session:

• Short, task-based scripts are easier to manage and update.
• Record the tasks a user would perform when working with an application.
• For a test to be useful, it should be repeatable and have an expected result.

[edit] Understanding recorded scripts

After you record a script, the actions you performed are interpreted by QA Wizard Pro and added as steps in the script. Some additional steps are also automatically added to help QA Wizard Pro use the correct application during playback.

The following statements are automatically added to all recorded scripts:

• The Set Context statement specifies the application version to connect to in the application repository during playback.
• The Run Application statement starts the application specified in the Set Context statement.

[edit] Running scripts

When you run a script, QA Wizard Pro compares the tested application against the information stored in the application repository. If differences are found, the script fails.

You can run individual scripts or multiple scripts using QA Wizard Pro or using a command prompt. You can also run scripts remotely. Keep the following in mind when you run scripts:

• If you move scripts to another computer to run them, the tested applications must be available in the global or local application repository. Scripts cannot run without connecting to the application in the repository.
• If the script connects to a running process, the process must be running on the test computer or the script will fail.
• You can monitor playback in real-time using the QA Wizard Pro Status Tool.