Running manual tests in accelQ

Availability: Version 4.0

In accelQ, you can either run an individual Scenario (with one or more test cases) or a Suite that comprises of one or more Scenarios.

You can start a run either by clicking on the Run button in the top toolbar or by clicking on Run button when you open a Scenario or a Suite.

 

 

Test Run Dialog

Type a purpose for the test run and select the Scenario or Suite that you want to run. Select the application environment where the test is going to run and provide a free form list of tags to annotate the run. Optionally, you can also setup notifications to send automated emails on the kick-off and/or completion of test run.

 

 

 

 

Test Runner

Once you start a run, accelQ Test Runner opens in a new browser window allowing you to mark test status and annotations while you are testing the AUT.

Note: Be sure to check if popup windows are blocked by Chrome, from accelQ site. If so, go to Chrome settings and allow popups from accelQ site.

 

 

Test Runner also provides a left-nav panel which displays list of test cases in the current job. You can search or navigate to arbitrary test case from this list and edit status.

 

 

 

Marking status at step level

To mark status at a step level, you can click the dropdown on the side of a step and choose one of the appropriate status values:

• Pass
• Fail
• Blocked
• Skipped
• Not Run

In addition, you can annotate a step with observations and screenshots by clicking on the step to expand it.

 

 

Marking Status at Test Case Level

At the test case level, you can set a status for the entire test case (as against step-level), associate with a bug or add annotation with screenshots. These actions are all available in the top header area of Test Runner window.

• To add annotation and attach screenshots, click on the pencil icon.
• To add a bug, click the bug icon.
• Status can be set by clicking on the status icon dropdown.

 

 

 

Once you set the status of a test case, you can navigate to the next/previous test cases by clicking on the icons in the top toolbar.

 

 

 

Note: As you update status at individual step level, system automatically updates the test case level status to reflect on the overall impact of that step on the test case. Of course, you can also manually change this test case status to something more appropriate if needed.

Create Defect for a Test Case

In accelQ, you can directly create a defect in a target Defect tracking tool, during the test run. Make sure the Defect Integration is setup for the project.

• Click on the Bug icon to open a defect modal.
• Select an option to either create a new defect or associate an existing defect from Jira or TFS.
• Select Jira or TFS project name.

 

• Click on the Next button.
• If you are associating to an existing defect, search the existing defect with its ID and complete the association.

• If you are creating a new defect, review/edit the Summary and Description of the bug.
• Select if you would like to attach a screenshot with the bug.
• In case the bug should be linked with other related items on Jira or TFS, click the link under the LINKED JIRA ISSUES section. Search for required stories and link.

 

 

• If your Jira or TFS Bug configuration requires any other mandatory information to be filled, accelQ presents a form with all the mandatory fields. Provide appropriate values and save the defect.
• Note: Make sure the values you provide in this screen are exactly (including upper/lower case and spaces) as per the form in the defect creation on Jira or TFS.

 

 

Display of Runs for a Scenario or Test Suite

When you are in the Scenario or Test Suite detail page, you can click on Runs tab to get a listing of all the test runs corresponding to the respective entity. Various user actions are possible depending on the state of the run (see below).

 

 

Open / Complete state of Test Run

When you initiate a test run, it is in Open state. You can resume the run any number of times and keep updating the test steps and test case status as required. When you are done with the particular run, you mark the test as Complete. Once marked as Complete, you cannot make any changes to test case status.

 

 

Marking the test job as Complete

When you are done running all the tests or if you are closing the Run session, you simply click on the Submit button. The test job will be in Open status until it is explicitly marked as Complete.

You can mark a job as Complete, in two different ways:

When you are submitting a job in the Test Runner, you can select Submit as Completed

 

 

Alternatively, you can click on the row corresponding to the Run in the Runs table and select Mark as Complete.

 

 

A test job that has not yet been marked as Complete, can be resumed for further updates to test status. Once marked as Complete, you cannot change the status of test steps or test cases.