Running a test

Before a test can be run, the test's Java source code must be generated and compiled as explained in Generating an executable test.

Before the test's Java code can be generated, a location for storing the code must exist. If no source folder named src exists in any existing Java project, you must create one as explained in Creating a new source folder.

Before a test can be run, it must be deployed. If no deployment exists, you must create one as explained in Creating a deployment. When you run your test, you choose an existing deployment.

To run a test:
  1. In the Test Navigator, right-click an executable test that you want to run and select Run. The Run wizard opens.
  2. In the list of Java projects, click the one in which to store the test code: its name appears in the Enter or select the parent folder field.
  3. Expand the selected project and click the folder in which to store the test code.
  4. Inspect the Name field, containing the name of the executable test. Accept or change the name.
  5. Do one of the following:
    1. Click Finish (1) if only one deployment is defined or (2) to run the test using the same deployment that was used the last time the test was run. This button is grayed out if more than one deployment is defined and the test has never been run.
    2. Click Next to select a deployment. The deployment page of the Run wizard opens.
    3. From the list of deployments, expand the one to use and click the location.
    4. Optionally, add or modify Environment Settings that may be required to run the test that you have manually expanded or modified. You can add, edit, rearrange, or remove settings.
  6. Do one of the following:
    1. Click Finish to run the test (1) with one user emulation or (2) with the same number of users emulations as the last time the test was run.
    2. Click Next to specify the number of users to emulate. The user emulation page of the Run wizard opens.
    3. Enter the Number of users to emulate in this test execution.
    4. Click Finish.

Parent topic: Testing browser-based applications - quick start
Previous topic: Generating an executable test
Next topic: Analyzing test results