Run Under ANT Options

Introduction

This page describes the various parameters available when using Run Under ANT.

Refer to Generating a Build File for step-by-step instructions on generating and testing a Build File.

The contents of Run Under ANT are as follows:

  • Detail Tab: Contains the primary settings for running under ANT, e.g. test cases, test environment.
  • Test Cycle Tab: Contains information on the test cycle which should be used and the number of times it should be run. Refer to Test Cycles for more information on this feature.
  • Metadata and Logging Tab: Contains settings for metadata caching and output logs.
  • Email Tab: Gives options for sending an email with an execution report after execution is completed.

Detail Tab

When the ‘Run Under ANT’ option is selected via the Navigator view, the following dialog window appears:

The parameters of this tab are as follows:

  • Build File Name: By default, Provar will create a new build.xml in Project under ANT installation directory. The user can also select an existing build.xml file from another location using the ‘browse’ option.
  • Result Location: By default, Provar will store results in Project under ANT/Results folder. The user can select any other folder under project to save the result to, using the ‘browse’ option.
  • Executing tests usingThere are two options to execute test cases using library:
    • Provar library: Test cases will execute using the Provar library. Use this option if you intend to run your test cases under ANT on your current machine.
    • ANT library: This option is useful when you want to run the tests on a different machine/server which does not have Provar installed. Using this method, a build.xml file can be created using ‘Run under ANT’ and copied over to another machine.
  • Select test cases: By default, Provar will show test cases that are mentioned in the existing build.xml. If no xml file previously existed, Provar will show the ‘tests’ folder for the user to select the test cases manually. To select test cases, click the ‘Select’ button. The following dialog will open for selections to be made:

  • Test EnvironmentSelect the test environment where the selected test cases will run. This must be a test environment which you have defined in Provar. If no environment is selected, the default environment will used.
  • Web Browser: Select the display resolution and browser you want to execute the tests on. This is the same setting as in Provar Desktop.
  • Exclude callable test case(s)Select this checkbox if you want to exclude callable test cases. Note that this setting overrides the test case selection setting above, so if you have included a callable test in ‘Select test cases’ and also check ‘Exclude callable test cases’, it will not be executed.
  • Start ANT Execution: Select this checkbox if you want to initiate test case execution through ANT when you hit the Run button. If not checked, clicking the ‘Run’ button will simply create the Build.xml file in the chosen location. Use this option if you want to create the ANT build file to be run on a different machine.

Test Cycle Tab

This tab contains information on the test cycle which should be used and the number of times it should be run. Refer to Test Cycles for more information on this feature.

The parameters of this tab are as follows:

  • Test Cycle: Select the test cycle you want to use (if applicable).
  • Run Type: Select which test cases should be run after the initial run: ‘Run all Test Cases’ or ‘Run failed Test Cases’.
  • Rerun: If a Test Cycle is specified, select the umber of times you want it to run.

Metadata and Logging Tab

This tab contains settings for metadata caching and output logs.

The parameters of this tab are as follows:

  • Metadata Folder:Select the folder where the metadata of your org will be cached.
  • Metadata Cache:Select the type of refreshing operation you want on your metadata cache when the ANT execution takes place:
    • Reuse reuses the existing metadata.
    • Refresh just downloads metadata changes.
    • Reload deletes old metadata files and downloads fresh metadata.
  • Test output log: Select the type of detailing in your test run log/report.
  • Plugin output logSelect type of detailing you want in the plugin log.

Email Tab

This tab gives options for sending an email with an execution report after execution is completed.

The parameters of this tab are as follows:

  • Don’t send an Email / Email the Test Run Report / Email the Test Cycle report:These radio buttons define if an email should be sent and, if so, what report it should contain. Test Cycle will be greyed out if the Test Cycle tab has been left blank.
  • Email Subject: The subject of the email to be sent
  • Primary Recipients:Email addresses to receive the email (separated by a comma, if there are multiple recipients)
  • Cc Recipients:Email addresses to be cc’d on the email (separated by a comma, if there are multiple recipients)
  • Bcc Recipients:Email addresses to be bcc’d on the email (separated by a comma, if there are multiple recipients)
  • Attach PDF execution report / Attach zipped HTML report: Indicates whether a PDF and/or HTML report should be included in the email

Note that, in order to send the report email, some email account details must be provided. This has to be done only once.

To provide email account details, click the ‘Email Configuration’ button.

The following dialog box will appear:

Provide email account details, then use the ‘Test Connection’ button to verify the details are correct. Then click ‘OK’.

2017-10-10T17:05:19+00:00

Leave A Comment