Testing Setup

Setting up tests is a first step in creation of a testing process. Learn below how to start.

Testing Setup allows the global admins to configure multiple testing setups. The Setup itself is flexible and does not impose the way of organizing tests - users can follow an approach that fits them the best. It does not matter whether it's the single or cross-project method, or even their own personal way of organization - Testing Setup adjusts. More information regarding tests organization can be found here.

Setting-up tests

Adding a work type during Testing Setup configuration, allows the app to identify where to add our Test Management panel within the work item view. When the configuration is disabled, the panel will not be visible anymore.

1. To access Testing Hub, go to the left-side panel and select Apps> ATM.

2. Testing setup section will be visible on the left. In there, click Create Testing Setup to get started.

Testing Setup - quick access: The keyboard combination cmd+K, and later typing "T" can be used as a shortcut to access the Testing Setup.

1. The new window is a place where a whole set-up is configured, step by step.

   1. In the box above, users can add a name. By default, it will be 'New testing setup'.

   2. Users select projects and work types per a test element.

      1. Depending on the testing element, one or more projects and work types can be selected, e.g. both for Requirements and Defects the users can select more than one items.

2. Assign a project and a work type to Requirements. Define a link that will be used for connecting Requirements to Test Cases. Click Next when done.

   1. This step is optional - if the users do not collect Requirements in Jira, they can omit it.

   2. The users can also set one project and work type as default. Later on, default settings will be automatically suggested in the Create work screen.

1. Assign a project and a work type to Test Cases. When done, click Next.

   1. Here, the users will also be informed about the new custom fields introduction - ATM Test Plans and ATM Test Types.

      1. At this moment, the ATM Test Types field is set to Manual.

1. Assign a project and a work type to Test Plans. When done, click Next.

   1. Here, a new custom field has been introduced - ATM Test Cases.

1. Just like above, assign a project and work item type to Test Executions. When done, click Next.

   1. Here, multiple new custom fields have been introduced:

      1. ATM Test Plans

      2. ATM Test Cases

      3. ATM Environments

      4. ATM TE Status

      5. ATM TE Progress

1. Lastly, you can also assign a project and a work item type to Defects. Click Next when done.

   1. This step is optional and can be skipped if not necessary.

   2. The users can also set one project and work type as default. Later on, default settings will be automatically suggested in the Create work screen.

1. If you want to complete setting up, click the Finish set up button on the last screen.

If the selected projects are company-managed, then the add-on automatically adds the custom fields to necessary screens. If team-managed projects are in use, the users have to remember that in order for the app to work, it is necessary to add app custom fields to screens associated with selected work types.

In order for the app to work properly, the users need to assign project permissions to the testing team.

Adding a new work type

A new work item type can be introduced at any of configuration stages:

1. Select Add a work type, choose a project and switch to option Create a new work type.

1. Add a name, optionally a description and choose the Jira work item level: either (0) which corresponds to the level of tasks, or (-1) - a level for subtasks.

2. To complete, click Assign button.

Editing and enabling Testing Setup

The users can revisit their Testing Setup to make changes, such as switching projects or work item types selected for each test element. In order to do so, go into Testing Hub> Testing Setup, and click on the Edit button. The users can also change the name of the setup by editing it in the box above the configuration window.

It is also possible to disable/enable each testing setup, by switching the toggle on the block.