You can run either a Scenario or a Test Suite in ACCELQ. Recall that a Scenario in ACCELQ comprises 1 or more test cases (data-driven) and that a Test Suite is a collection of Scenarios.
You can kick off a test execution from either
- the top-header Run action button or
- by clicking the Run button available in the Scenario or Test Suite page
Selecting what to Run
- In the Run modal, describe the purpose of Run in the Purpose field.
- Select either a suite or scenario to run.
- To further fine-tune what gets executed, you can click on the Test Case count link and individually select the test cases to run.
Note: You can run tests in trouble-shooting mode (debug mode) by selecting the checkbox for the same. Learn more.
Configuring execution parameters
While running a test, you can configure the following parameters in the Run modal
You can select a schedule to run the test. The following options are available when you click the When to Run field.
- Run Now: The test run will kick off immediately. In case the agent is busy at the max threshold for concurrent jobs, then the job is queued up.
- Schedule for a future time: Select a time when the test should execute. Note that the time selection is based on the timezone from where the ACCELQ test is being initiated. It is not the ACCELQ server timezone.
- Setup recurring run: Set up a recurring run schedule if the test should be repeatedly executed on a set schedule. Exhaustive options are available.
- Create a CI Job: This option will just create a CI job with the actual execution happening asynchronously from a CI platform. An example is Jenkins Integration as described here.
Select Application Environment
Click on the App Environment field to select the application environment against which the test should execute. Learn more about application environments here.
Select Agent to run on
An Agent is a machine on which the test should run. All the active registered agents are listed. More about local agents.
Note that the agent could be pointing to a sauce labs or browser stack instance as well.
Select OS/Browser to run against
Choose the operating system and the browser to use for test execution. When you select the operating system, the supported browser list is automatically updated.
Note: You can choose to run the test in headless mode, which causes the browser to open in the background. More info here.
When a test is executed, ACCELQ collects screenshots to embed as part of test report. You can configure the screenshot options as follows:
- Comprehensive: The screenshot is captured for every interaction with the application. This mode may have a slight execution performance impact due to the number of screenshots.
- Optimal: ACCELQ determines the transition points in the application and takes screenshots as needed. This is the recommended option.
- On Error: Screenshots are captured only when a failure occurs.
Timeouts are utilized when the scripts are executing. When you are running a test, web page and UI elements may take some time to fully load on your application. If your test logic requires interaction with a page or UI element, timeouts define how long to wait for this loading to complete.
You want to choose timeout values appropriately to make sure you are waiting long enough for the screen to load, but not too long to waste execution time when the screen is really not rendering because of application errors. There are two values you can configure:
- Page timeout: This is the maximum amount of time ACCELQ will wait for the page to fully load before starting to interact with it. This timeout is used during the automatic synchronization which is inserted before every action. The default value is 60 seconds.
- Element timeout: This is the maximum amount of time ACCELQ will wait at runtime, for an element to appear. When you are interacting with the UI element and if the element is not displayed, the script moves on with an error after waiting for this timeout (in seconds). The default value is 30 seconds.
If your local agent supports more than 1 concurrent job (thru configuration), you can enable this feature for the current run by turning this field ON. Here are the complete steps to achieve parallel execution.
Email configuration allows configuring the recipients of emails and the events on which email is delivered. Click on Notify To field for configuring. Emails can be sent at the following events:
- Test kick-off
- Test completion
Note that you can send execution emails to non-subscribers as well. Just type in the email address.
Provide Run Properties values
Run Properties allow user input during test runs. You could design your scenario and override parameters with Run Properties, in case there is dynamic information required to be passed every time the test is running. More information here.
If there are any run properties required for the selected Scenario or Test Suite, an additional screen will show up after you click on the Run button in the main Run modal.
Once the test is kicked off, you can view the progress in realtime, from the Results grid.