Test cases

A test case is your documentation for performing the tests on your product, feature etc.

Allure TestOps supports working with both – manual and automated test cases.

In Allure TestOps Test case consists of the following set of actions and metadata.

1. Name is the text label of the test case briefly describing its purpose.
2. System ID – Allure ID is a unique identifier of a test case in Allure TestOps.
3. Description is an extension for test case's name. You can provide more information about the test's purpose and what is actually does.
4. Steps of a test case are described in the scenario.
   • steps can have attachments providing additional information about the test's flow. These could be images, tables, text attachments.
   • You can have one main step and several sub-steps.
   • Sub-step is created by pressing Tab on your keyboard. To transform sub-step back to a main step press Shift+Tab.
5. Test case's lifecycle status. Defines on which stage of the workflow is your test case. This is adjustable parameter, simplest examples of the status are Draft (you are still creating a test case), Review (done but is not approved), Active (can be used in test runs).
6. Meta information about a test case. Meta information will allow you smart grouping, filtering, searching the test cases and test results.

Test cases meta information

At the moment there are following types of meta information supported by Allure TestOps.

1. Custom fields.
2. Members – Roles.
3. Test layers.
4. Tags.
5. Information about issues in issue trackers.
6. Links towards external Test management systems.

Managing this information is described in next sections.

Managing your test cases

Generally, the management of test cases implies the creation, editing (scenario, meta information), and maintaining the lifecycle of a test case.

The management of manual and automated test cases generally differ but intersect sometimes, in the next sections you will.

Manual test cases

• Creating manual test cases
• Adding Tags
• Adding Issues
• Adding Members, e.g. an owner or an author etc.
• Adding Custom Fields
• Bulk actions
• Creating and editing of Scenario
• Muted tests
• Relations
• Filtering the test cases

Automated test cases

• Creating automated test cases
• Adding Tags
• Adding Issues
• Adding Members, e.g. an owner or an author etc.
• Adding Custom Fields
• Bulk actions
• Creating and editing of Scenario
• Muted tests
• Relations
• Filtering the test cases