Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Execution screen may look a little daunting for the first time user due to various fields it has.

The image above details various sections of the execution screen.

  • On the left is the list of suites.

  • On selecting a suite, the table in the center get populated with the list of tests in that suite. Details of the test list are as shown in the diagram.

  • Execution details and other metadata appears on the right side as an accordion with 3 sections.

  • The circular pull out button toggles a slide out panel containing Saved Plans.

Expanding the first section Execution Details opens gives us the fields as shown in the image on the right. Most of the fields are self-explanatory but some need further explanation.

  1. Run Name (Required): Name your current Run

  2. Sprint/Release: Sprint or Release for this Run.

  3. Build Number: Build Number of the application used for this Run

  4. Browser Instances (1): Number of simultaneous browser instances to use for this run. It ranges from 1 to 4. This is normally used when you have multiple tests and you want to run them in parallel on multiple instances of the same browser.

  5. Distribute Across Machines(OFF): Do you want to distribute your tests to be run on different selected machines. This is normally

  6. Tags(Empty): Tag for data to use for this run. You can select multiple tags to run your tests for multiple sets of data.

  7. Execute Tags First(OFF): Default execution behavior is to run each test for every tag before proceeding to the next test. Switching this field to ON will make all the tests run for a single tag before proceeding to the next tag.

  8. Email To: Email Execution Summary Report to users. Multiple comma separated emails can be added.

Advanced Setting Section allows you to control the following aspects:

  1. Uninstall App (OFF): Determines if the app should be uninstalled from the device and reinstalled before execution.

  2. Clear App Data (ON): Clear Mobile application data after every run.

  3. Repeat Test without a Tag (OFF): This switch is used only if Execute Tags First is turned ON and is used to execute tests without a tag every time a named tag is executed. By default, this switch is off and tests without a tag are executed only once.

  4. Enable Request Capture (OFF): By turning this switch ON, you can capture and validate requests sent by your browser/device. Please see xxx for more details.

  • No labels