Testing Elements

A Testing Project is the test project in Appsvio Test Management (ATM). It sits above Jira spaces (projects) and connects them. In a Testing Project, you map each testing object to a Jira space and a work type, which Jira also calls a work type.

Independent teams in your company should have their own Testing Project.

What a Testing Project defines

A Testing Project maps these testing objects: requirements, Test Cases, Test Plans, Test Executions, defects, and Test Campaigns. Each object can be in a separate Jira space, or all objects can be in one space. ATM gives you full freedom here.

For example, requirements can be Epics and Stories, and defects can be Bugs. ATM Test Type is currently set to Manual for all Test Cases. For details on each field, see ATM in Jira.

Without requirements, you can’t use the Coverage and Traceability reports. See About Requirement.

Each Testing Project has one Test Repository with its own folder tree. See Test Repository.

See all Testing Projects

Go to Apps › Test Management › Testing Projects. The page shows each Testing Project as a tile. Every user can see this list and star Testing Projects.

• To find a Testing Project, use the filters above the list: Search by name, Starred, and Jira Spaces.
• Click the star on a tile to add the Testing Project to your favorites. The Starred filter then shows only your favorites.
• A tile can show the error or disabled label. A disabled Testing Project is grayed out.
• The menu on a tile has these options: Disable or Enable, Delete, and Configuration of the Testing Project. To open the dashboard of a Testing Project, click its tile.

If there’s no Testing Project yet, the page shows “No testing project found”. It has the Create testing project and Create sample project buttons, and a Learn how link. Only Jira administrators can create the sample project. To try ATM on sample data, see Quick Start.

Create a Testing Project

Only Jira administrators can create, edit, disable, enable, or delete a Testing Project. See Permissions.

Click Create new in the top right corner of the Testing Projects page. The wizard has seven steps:

1. Requirements: choose one or more spaces and work types. You can mark one pair as the default, which the Create screen then suggests automatically. Also choose the Jira link type between a requirement and a Test Case.
2. Test Cases: choose exactly one space and work type.
3. Test Plans: choose exactly one space and work type.
4. Test Executions: choose exactly one space and work type.
5. Defects: choose one or more spaces and work types.
6. Test Campaigns: choose exactly one space and work type.
7. Summary: save the configuration.

The Requirements, Defects, and Test Campaigns steps show “This configuration is optional”, and you can skip them. If the space has no suitable work type, the step shows the Add work type button.

Each step shows which ATM fields will be added. ATM adds them to the view of each object only when you save the configuration.

Link type for requirements

The link type connects a requirement with its Test Cases. If you map requirements, you must choose a link type. If you choose a link type, you must map requirements.

We recommend the link type that shows “is tested by” on the requirement and “tests” on the Test Case. The sample project uses it. The wizard has no default link type. Each Testing Project can use a different link type. See Coverage with Test Case.

Mapping rules

• You can’t choose the same space and work type twice in one Testing Project.
• A space and work type mapped as Test Cases, Test Plans, Test Executions, or Test Campaigns can be used in only one Testing Project. It can also be mapped as only one type of object.
• Requirements and defects can be shared between Testing Projects. In that case, each Testing Project maps the same space and work type as the same object. You can’t map that pair as another type of object.

See the configuration of a Testing Project

Click a tile to open the page of that Testing Project. The page shows its name, and the × button closes it.

The Testing Project configuration section has six tiles: Requirements, Test Cases, Test Plans, Test Campaigns, Test Executions, and Defects. Each tile shows the Jira space and the work type. The Requirements tile also shows the Link type.

You can collapse this section. Below it, counters and charts show the state of testing. See Testing Project Dashboard.

Disable or delete a Testing Project

To disable a Testing Project, select Disable in the menu on its tile. To turn it back on, select Enable.

To delete a Testing Project, select Delete in the menu on its tile. To confirm, type the name of the Testing Project. You can’t undo this.

Deleting removes the configuration of the Testing Project and the folder tree of its Test Repository. Work items and the values in their fields stay in Jira, including Test Cases, Test Plans, Test Executions, and results. You can’t open them in ATM until you map them to another Testing Project.

Global configuration

Only Jira administrators see the Configuration button in the top right corner of the Testing Projects page. It opens the Configuration page with global settings in two sections:

• Environments: the environments you choose on Test Executions in the ATM Environments field. See Global Environments.
• Test steps: the fields of a test step. See Test Case Columns.

One space or separate spaces

You can keep all testing objects in one Jira space, or put each object in a separate space.

The sample project keeps all testing objects in one space to make onboarding easier.

Testing objects in separate spaces can have separate Project Permissions in Jira. For example, a dedicated space for Test Cases lets you set their permissions apart from Test Executions and Test Plans.

For more on this choice, see Jira Space.