- Introduction
- About
- Onboarding
- Getting Started
- Demo backup
- User's guide
- Projects' organization
- Test design
- Organizing tests
- Test planning
- Test execution
- Requirements
- Operations
- Reporting and tracking
- Import/Export TCT
- Export test issues
- Issue search dialog
- TestFLO menu
- Admin's guide
- Project configuration
- TestFLO settings
- Test Automation configuration
- TestFLO Permissions
- Custom fields
- Advanced workflow configuration
- Panel Filter Result
- Upgrade reports
- Upgrade guide
- Integrations
- REST API
- Configuration Manager for Jira
Test Case Template operations
This page provide information about Test Case Template operations.
Each Test Case Template has dedicated operations:
Add to existing Test Plan
This operation allows adding given Test Case Template (create Test Case) to selected Test Plan. Test Case is an issue type which is an executable copy of the Test Case Template. The Test Case Template becomes Test Case when you add it to the existing Test Plan. 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.
Due to the fact that Test Cases are creating by using Test Case Templates a table below lists the fields copied by default and those that can be created using the Create TCs with fields from filter config setting from TestFLO settings.
| Field type | Default configuration | Field configuration from filter |
|---|---|---|
| Summary | yes | yes (always) |
| Description | yes | yes |
| Priority | yes | yes (always) |
| Component/s | yes | yes (compared by name) |
| Labels | yes | yes |
| Remaining Estimate | yes | yes |
| Original Estimate | yes | yes |
| Attachments | yes | yes (every time, no attachment column in filter) |
| Assignee | default assignee from project or component | yes |
| Affects Version/s | no | yes (compared by name) |
| Environment | no | yes |
| Fix Version/s | no | yes (compared by name) |
| Issue links | separate configuration Copy links from TCT | yes |
| Issue security | no (inherited from Test Plan) | no (inherited from Test Plan) |
| Reporter | logged user | logged user |
| Custom fields | yes (all in TCT and TC context) | yes |
Steps
To add the Test Case Template to existing Test Plan:
- Click the Add to existing Test Plan operation from Test information panel or select from menu More.
- On the Select issue(s) dialog select the Test Plans to which you want to add this particular Test Case Template. After selection, click Select.
Note
The list shows Test Plans for which the user has permissions.
Result
The Test Cases Template have been added to the selected Test Plans. The created Test Cases from the given Test Case Template are visible in the Test Progress panel.
Link with Requirement
The Link with Requirement operation allows to link given Test Case Template with requirements. This operation is connected with Requirement field on issue and Requirements tab in project configuration.
To read more about Test Case Templates and its connection to requirements, see Link with tests.
Steps
To link with requirement:
- Click the Link with Requirement operation from Test information panel or select from menu More.
- On the Select issue(s) dialog select requirements that you want to link with given Test Case Template. After selection, click Select.
Note
The list shows:
- only these issues from projects which were selected in the Requirements tab in project configuration (restrictions for requirement),
- all issues when no restrictions were selected in the Requirements tab in project configuration.
Result
The requirements have been linked with the Test Case Template in Requirement field.
Update Test Cases
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 Test Case Template and you want to change the content in the created Test Cases from given Test Case Template.
Due to the fact that Test Cases are updated by using Test Case Templates a table below lists the fields copied by default and those that can be updated using the Update TCs with fields from filter config setting from TestFLO settings.
| Field type | Default configuration | Field configuration from filter |
|---|---|---|
| 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 (every time, no attachment column in filter, 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 | no (inherited from Test Plan) |
| Reporter | no | yes |
| Custom fields | yes (all in TCT and TC context) | yes |
During the Test Cases update, you can decide whether 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 is about deleting or adding a step to the Steps panel, the statuses will be reset because this is a big interference in the content.
Steps
To use Update Test Cases operation:
-
Click the Update Test Cases operation from Test information panel or select from menu More.
-
On the Update Test Cases dialog, check the option if you do not want to reset the step statuses to default or leave this option unchecked to reset these statuses. When the number of steps has changed then the status is always reset regardless of this option.
-
Select Test Cases which you want to update from given Test Case Template.
The list will show only those Test Cases that were not executed (their statuses are not set in the Closed statuses setting from TestFLO settings).
Result
The selected Test Cases have been updated from the given Test Case Template.
