What is a test suite
Test Suite is a collection of scenarios (test cases) defining the scope of testing for a given execution requirement. You can setup Test Suites for a Release, Cycle, Sprint, Regression or other common needs and serves as a Test Plan.
Types of Test Suite
accelQ supports 3 different types of test suites depending on how you define the scope:
1. Static suite, where you would create a collection of named scenarios. This suite remains static once defined. Member Scenarios form an ordered list, so the sequence of test execution is always guaranteed. This is the only type of suite where the order of execution is guaranteed.
This type of Test Suite is helpful in situations where there is a specific need to run a selected collection of Scenarios together. Although it is not recommended to design scenarios with inter-dependency, in some situations it may be inevitable. Static Test Suite provides the capability to run multiple Scenarios in sequential order.
2. Filter based suite, where the suite is defined by a set of custom fields filter parameters. You just define a set of rules based on Custom Fields in the accelQ application while the actual list of Scenarios evolves over time. This kind of Test Suite is very appropriate for targeted testing of specific portions of Application Under Test such as Change Impact testing, Risk-Based Testing or module level testing.
3. Requirements based suite, where the suite is created based on the coverage requirement for a set of user stories from requirement tracking tools such as Jira. This is the most common type of Test Suite in an Agile environment. Right after the Sprint planning session, you would create a Test Suite appropriate for the Requirements and use it as a continuous tracker during the life of the Sprint.
As test planning makes progress during the Sprint, various Scenarios are identified for the test execution and tagged with the Requirements they cater to. As this happens, the Test Suite pulls all relevant Scenarios together and compiles the readiness and progress. When such a Test Suite is executed, it is very easy to pinpoint Stories that are particularly lagging in Quality readiness.
Creating a test suite
Click on the create entity icon on the top navigation and select Test Suite.
On the “New Test Suite” window,
- Select the Type of Test Suite you want to create.
- Give a name on the Name field. Remember, the name given should be unique in the project.
- Enter Description. This is an optional field, but we suggest you provide a description to explain the suite briefly.
- Click on "Save & Continue" to start defining the Test Suite. Or, click on "Save" to just create the blank Test Suite for now.
- Once you are in the created Test Suite view (Universe), start defining the Test Suite on the sidebar based on the type you selected:
a) Filter Based Test Suite
Start adding Scenario Filters on the basis of which you would like to have the Scenarios selected for the Test Suite. You can add filters based on Name, Tags and other custom fields for scenario.
b) Requirement Based Test Suite
Start mapping Requirement/Stories that are defined in external Requirement tracking tool (such as JIRA). Provide the story ID and accelQ pulls all the scenarios marked for those Requirements or Stories.
Go to the "Scenario" tab on the sidebar and start adding Scenarios which you want to make part of the Test Suite by clicking on the "+" icon.
For any type of suite, you can also add Test Case filters to narrow down on the specific Test Cases you would like to be part of the Test Suite. The Test Case filters can be based on these fields: Name, Tags and custom fields defined for test case.