Testing objects & Relations
Appsvio Test Management (ATM) works with seven types of testing objects. The testing process in ATM uses five dedicated types: Test Case, Test Plan, Test Campaign, Test Execution, and Test Case Execution. ATM creates them automatically when you create the sample project. Requirements and Defects usually already exist in Jira, for example as Epics, Stories, and Bugs.
Six of the seven objects are Jira work items. The seventh, the Test Case Execution, is ATM’s own object.
To build a testing process, you need at least three objects: Test Case, Test Execution, and Test Case Execution. Test Plans and Test Campaigns are optional, but in larger implementations you practically need them.
The seven testing objects
| Object | Short name | Jira work item | What it’s for |
|---|---|---|---|
| Requirement | REQ | Yes | What needs to be tested. Any work item can be a requirement. Most often it’s an Epic or a Story. |
| Test Case | TC | Yes | Describes how to test something, with test steps and preconditions. You reuse it in many Test Plans and Test Executions. |
| Test Plan | TP | Yes | Optional. The scope of testing: a set of Test Cases. You can run it many times, and each run is a separate Test Execution. |
| Test Campaign | TCA | Yes | Optional. Groups Test Plans so business stakeholders can track test progress. |
| Test Execution | TE | Yes | Groups the Test Cases you run together, for example in one test cycle or on one environment. It has its own status and shows the test progress. |
| Test Case Execution | TCE | No, ATM’s own object | Created when you run a single Test Case in a Test Execution. Testers record its result here, per step and as a whole: ATM sets its status from the step statuses, and you can change it manually. |
| Defect | - | Yes | A bug found during testing, for example a Bug work item. While you run a test, you create a new Defect or link an existing one. |
Relations between the objects
- A Requirement is linked to Test Cases with a Jira link. One Requirement can have no Test Cases, one, or many.
- A Test Plan contains Test Cases. One Test Case can be in more than one Test Plan.
- A Test Campaign contains one or more Test Plans. One Test Plan can be in several Test Campaigns.
- Each run of a Test Plan is a separate Test Execution. For example, you run one Test Plan on the test, staging, and production environments, and get three Test Executions.
- A Test Execution has a Test Case Execution for each Test Case you select. You can assign each Test Case Execution to a tester.
- You add Defects to a Test Case Execution: you create a new Defect or link an existing one. A new Defect created from a step or from the whole Test Case Execution is linked to that Test Case Execution. A Defect created from a step is also linked to that step.
How the testing objects get into Jira
ATM adds the testing objects to Jira when you create the sample project. If work types with these names don’t exist yet, ATM creates Test Case, Test Plan, Test Campaign, and Test Execution as work types. It also creates the Test Case Execution as its own object.
That’s why we recommend creating the sample project first, at the start of testing your product. See Quick Start. If you configure a project manually, you need to confirm all these settings yourself. See ATM in Jira.
Which spaces and work types ATM uses
A Testing Project defines what a requirement is and which space and work type each testing object uses. In a Testing Project, you must map Test Cases, Test Plans, and Test Executions. Mapping Requirements, Defects, and Test Campaigns is optional.
When you save the Testing Project configuration, ATM adds its fields to the testing objects in Jira. See Testing Elements.