This page provides information about Test Case Template operations.
This operation allows you to add a given Test Case Template to the selected Test Plan. When you add TCT to TP it becomes a Test Case that is an executable copy of the Test Case Template. The Add to existing Test Plan operation has the same mechanism of the Test Case creation as the Create Test Cases operation on Test Plan.
To get more information about the Test Case issue type and its features, see the entire Test Case chapter.
To add a Test Case Template (create Test Case) to Test Plan you need to have a Create Issues and Edit Issues permissions.
Steps
To add a Test Case Template to an existing Test Plan:
The number of displayed TPs per page can be changed using the Page size: issue searcher dialog option. You must bear in mind that the change also affects other operations. To learn more see Global Settings.
The Basic search does not support Sprint, Team and Link type fields.
Each selected filter is reflected in the Search bar. Depending on the complexity, it will show up in the basic or advanced mode.
Part of the Quick filters are based on the Requirement, Component/s and Fix Version/s fields. If the fields on the Test Case Template have no values, the dedicated filters will not appear.
Result
You have created Test Case/s by adding Test Case Template to selected Test Plan/s. Created Test Cases are available in the Test Cases panel in the given Test Plan/s. They are also displayed in the Test Progress panel on the TCT.
You need to refresh the view of the Test Case Template to see all created Test Cases in the Test Progress panel.
When adding Test Case Templates to Test Plan, the data is taken from the fields existing in the TCT and recreated in the fields in the TC. The data in the fields is created (copied) based on the default configuration, which is presented in the table below. You can also overwrite the default configuration using the dedicated Create TCs with fields from TCTs option in TestFLO settings, where you select only those fields that interest you during creation. The rules for creating using the Create TCs with fields from TCTs option can be found in the appropriate column of the table below.
You must remember that field data will be copied if a given field is configured for both Test Case Template and Test Case.
In the table below you can check the list of fields and their behavior when you are adding Test Case Templates to the Test Plan (creating Test Cases).
| Field type | Default configuration | Fields configuration |
|---|---|---|
| Summary | Yes | Yes (always regardless of the configuration) |
| Description | Yes | Yes |
| Priority | Yes | Yes (always regardless of the configuration) |
| Component/s | Yes | Yes (compared by name) |
| Labels | Yes | Yes |
| Remaining Estimate | Yes | Yes |
| Original Estimate | Yes | Yes |
| Attachments | Yes (compared by name and file size) | Yes (compared by name and file size) |
| Assignee | Default assignee from project or component | Yes |
| Reporter | Yes (logged user) | Yes (logged user) |
| Affects Version/s | No | Yes (compared by name) |
| Environment | No | Yes |
| Fix Version/s | No | Yes (compared by name) |
| Issue links | No (separate configuration Copy links from TCT) | Yes |
| Custom fields | Yes (same custom fields in both TCT and TC contexts) | Yes (same custom fields in both TCT and TC contexts) |
| Issue security | No (inherited from Test Plan) | No (inherited from Test Plan) |
The Link with Requirement operation allows linking requirement with the given Test Case Template. From the list of available requirements, you can select any issue and after linking its key will appear in the Requirement field.
If you configure issues that will be your requirements then the list of available requirements will be narrowed down only to the issue types you choose. Also linked Test Case Templates will be displayed in the given requirement in the Coverage panel.
To learn how to configure your requirement types see the Requirements tab in the Project Settings.
To read more about Test Case Templates and their connection to requirements, see Link with tests.
Steps
To link Test Case Template with a requirement:
The number of displayed requirements per page can be changed using the Page size: issue searcher dialog option. You must bear in mind that the change also affects other operations. To learn more see Global Settings.
The Basic search does not support Sprint, Team and Link type fields.
Each selected filter is reflected in the Search bar. Depending on the complexity, it will show up in the basic or advanced mode.
Part of the Quick filters are based on the Component/s and Fix Version/s fields. If the fields on the Test Case Template have no values, the dedicated filters will not appear.
Result
You have linked requirement/s with the Test Case Template. The keys of the linked requirements are displayed in the Requirements field in the given Test Case Template.
You can change the behavior of the Requirement field, including key display type, number of values, and other options in the field settings. For more information, see TestFLO - Enhanced Issue Picker CF.
This operation updates all not executed Test Cases created from the given Test Case Template. The Update Test Cases operation can be useful if you made a mistake while writing the Test Case Template and you want to change the content in the created Test Cases from the given Test Case Template.
To use the Update Test Cases operation, the user must have the Edit issue permission. The permission must be granted in the project where the Test Cases are to be updated.
You can decide which users have access to the Update Test Cases operation by granting the Update Test Cases operation permission.
In the table below you can check the list of fields that are updated from the Test Case Template to the Test Case. There are two ways to update fields. You can use the Default configuration or select specific fields using the Update TCs with fields from TCTs option in TestFLO settings.
| Field type | Default configuration | Fields configuration |
|---|---|---|
| Summary | yes | yes |
| Description | yes | yes |
| Priority | yes | yes |
| Component/s | yes (compared by name) | yes (compared by name) |
| Labels | yes | yes |
| Remaining Estimate | yes | yes |
| Original Estimate | yes | yes |
| Attachments | yes (compared by name and file size) | yes (compared by name and file size) |
| Assignee | no | yes |
| Affects Version/s | no | yes (compared by name) |
| Environment | no | yes |
| Fix Version/s | no | yes (compared by name) |
| Issue links | no | yes |
| Issue security | no (inherited from Test Plan) | no (inherited from Test Plan) |
| Reporter | no | yes |
| Custom fields | yes (all in TCT and TC context) | yes (all in TCT and TC context) |
The selected option in the Update TCs with fields from TCTs configuration will be the default set of fields for the user. The default fields are available in the Fields to be updated on Test Case field in the Update Test Cases operation dialog. If the user has Set fields on Update Test Cases operation permission, they can edit the field list in the dialog. Changes made in the dialog only affect the results of the operation that the user performs. They do not change the defaults set in Update TCs with fields from TCTs configuration for other users. If the user does not have this permission, the fields will update according to the selected option in the configuration.
During the Test Cases update, you can decide if you want to reset the Steps statuses to default. This option will not reset step statuses if you apply content changes only to existing steps in the Steps panel. If the change concerns deleting or adding a step to the Steps panel, the statuses will be reset because this is a significant content interference.
Steps
To use Update Test Cases operation:
If you do not have the Set fields on Update Test Cases operation permission, you cannot change the fields.
The list displays only those Test Cases that have not been executed (their statuses are not set in the Closed statuses option from the TestFLO Settings).
Result
You have updated selected Test Cases from the Test Case Template.
If you have changed the default set of fields in the Fields to be updated on Test Case field when you use the operation again your change will be preserved. Changes are preserved per user.