- About TestFLO
- Overview
- For whom
- Key benefits
- Roadmap
- Onboarding
- Basic concepts
- Glossary
- Quick guide for Jira Administrator
- Quick guide for QA manager
- Quick guide for testers
- Demo environment
- Requirements
- Requirements
- Requirement operations
- Designing tests
- Test Case Template
- Organizing tests
- Reporting & tracking
- Reporting and tracking overview
- Requirement Test Coverage Report
- Requirement Traceability Report
- Requirement Test Execution Report
- Test Plan Execution Report
- Test Plan Iterations Report
- Test Execution Report
- Test information panel
- Issue panels
- Export test issues
- Dashboard Gadgets
- Miscellaneous
- TestFLO menu
- Issue Search Dialog
- JQL functions
- Administration & Configuration
- Projects' organization
- Create project
- Project configuration
- TestFLO settings
- TestFLO Permissions
- Custom fields
- Advanced workflow configuration
- Panel Filter Result
- Import/Export TCT
- Test Automation configuration
- Upgrade reports
- Upgrade guide
- Integrations
- Confluence
- REST API
- Configuration Manager for Jira
Test Plan operations
This page provides information about Test Plans operations.
Each Test Plan has dedicated operations:
Assign Test Cases
This operation allows changing Assignee of all not executed Test Cases under a Test Plan. Its overrides standard Assign permissions. It is highly useful if your company has sophisticated security regulations and/or for example tester should not be able to change Assignee within the project except Test Cases. Another advantage is the bulk change of the Assignee of all Test Cases under a Test Plan.
Steps
To use Assign Test Cases operation:
- Go to the Administration > Add-ons > TestFLO Settings > Test Case.
- Select the Assign Roles option and click pencil.
- Select appropriate roles and click outside the option. The configuration has been saved.
- Go to the Test Plan.
- Select the Test Cases that you want to assign.
- Click the Assign Test Cases operation.
- Select the user to whom you want to assign Test Cases.
- Click Assign to confirm.
Result
Selected Test Cases have been assigned to the chosen user.
Next iteration
The Next iteration operation allows creating another iteration of the Test Plan with Test Cases based on four strategies. Together with the new iteration, all Test Cases execution statuses, linked defects, and step comments will be reset. This will allow you to test again chosen Test Cases in the new iteration. All previous Test Case executions are available in the Test Executions tab on Test Case and all previous Test Plan iterations are available in the Test Plan Iterations tab on Test Plan.
You can restrict users’ permissions to use this operation with the Next Test Plan Iteration permission. To learn more see TestFLO permissions. Along with the restriction of this operation, a restriction on changing the Iteration name is imposed.
If your team happens to create iterations by accident, you need to know that they cannot be deleted. Therefore it is best to lower your chances to accidentally create an iteration by restricting the ability to create a new iteration to a small number of people. This can be done by granting the Next Test Plan Iteration permission. You can grant it in a given project in the Permissions tab or globally on the Permissions page.
Depending on the results of a given iteration and what Test Cases you want to execute in the next iteration, you can use strategies:
All Test Cases
This strategy creates a new iteration with all existing Test Cases on Test Plan.
Steps
To use the All Test Cases strategy:
- Click the Next iteration operation from the Test information panel or select from the menu More.
- Leave the default Iteration name or rename it to one that will help you better identify the iteration.
- Select the All Test Cases strategy and click Next.
- The Next iteration dialog displays a list with all Test Cases from Test Plan. Click Create to create the next iteration.
Result
The next iteration has been created. Historical data from the previous iteration has been saved in the Test Plan Iterations tab.
Not passed Test Cases
This strategy creates a new iteration with Test Cases whose statuses are not configured as Passed statuses in the Test Case section in TestFLO Settings. This means that if the status in the “Passed statuses” category has been set as Pass, then Test Cases which have different statuses than the Pass status will be selected for the next iteration.
Steps
To use the Not passed Test Cases strategy:
- Click the Next iteration operation from the Test information panel or select from the menu More.
- Leave the default Iteration name or rename it to one that will help you better identify the iteration.
- Select the Not passed Test Cases strategy and click Next.
- The Next iteration dialog displays the Test Cases list with not passed statuses from the current Test Plan iteration. Click Create to create the next iteration.
Result
The next iteration has been created. Historical data from the previous iteration has been saved in the Test Plan Iterations tab.
Only failed Test Cases
This strategy creates a new iteration with Test Cases whose statuses are configured as Failed statuses in the Test Case section in TestFLO Settings.
Steps
To use the Only failed Test Cases strategy:
- Click the Next iteration operation from the Test information panel or select from the menu More.
- Leave the default Iteration name or rename it to one that will help you better identify the iteration.
- Select the Only failed Test Cases strategy and click Next.
- The Next iteration dialog displays the Test Cases list with failed statuses from the current Test Plan iteration. Click Create to create the next iteration.
Result
The next iteration has been created. Historical data from the previous iteration has been saved in the Test Plan Iterations tab.
Custom Test Cases
This strategy allows creating a new Test Plan iteration with selected by user Test Cases.
Steps
To use the Custom Test Cases strategy:
- Click the Next iteration operation from the Test information panel or select from the menu More.
- Leave the default Iteration name or rename it to one that will help you better identify the iteration.
- Select the Custom Test Cases strategy and click Next.
- The Next iteration dialog displays a list with all Test Cases from Test Plan. Select the Test Cases you want to test in the next iteration and click Next.
Tip
Use Quick filters to filter relevant Test Case statuses or Test Cases that are in the current iteration.
- The Next iteration dialog displays all selected Test Cases. Click Create to create the next iteration.
Result
The next iteration has been created. Historical data from the previous iteration has been saved in the Test Plan Iterations tab.
Reset current iteration
The Reset current iteration operation reset all Test Cases execution in current iteration to initial state. All Test Case statuses, Steps statuses, linked defects, Steps comments, Resolution and Resolution date Test Cases wiil be reset.
You can restrict users permissions to use this operation. To learn more see TestFLO permissions.
Steps
To use Reset current iteration:
- Click the Reset current iteration operation from Test information panel.
- Click Confirm to reset current iteration.
Result
The current iteration have been reset to initial state.
Copy Test Plan
The Copy Test Plan operation is a dedicated operation for multiplying plans. It is one of the solutions when you need to make for example regression test. The Copy Test Plan operation allows you to select tests that you want to copy to the new Test Plan using two mechanisms.
Steps
To use Copy Test Plan:
-
Click the Copy Test Plan operation from Test information panel or select from menu More.
-
Select target projects from list. By default, the project from which the Test Plan was created is set.
WarningAvailable projects are those in which:
- Test Execution module has been activated.
- Current user has Create Issue and Browse Project permissions.
-
Select from two copy mechanisms:
3a. current Test Cases creates Test Cases on the copied Test Plan as copy of Test Cases in current Test Plan (one-to-one).
NoteIf Test Plan have multiple Test Cases originated from the same Test Case Templates, the target Test Plan will contain all Test Cases for each Test Case Template.
-
Select Test Cases or Test Case Templates (depending on the chosen mechanism) to copy from list.
-
Click Copy to copy Test Plan.
Result
The Test Plan was created.
Create Test Cases
This operation allows you to create Test Cases on a Test Plan. Test Case is an issue type that is an executable copy of the Test Case Template. The Test Case Template becomes Test Case when you use the Create Test Cases operation.
In the table below you can check the list of fields that are created/copied from the Test Case Template to the Test Case. There are two ways to create fields. You can use the Default configuration or select specific fields using the Create TCs with fields from TCTs option in TestFLO settings.
Field type | Default configuration | Fields configuration |
---|---|---|
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 (compared by name and file size) | yes (compared by name and file size) |
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 create Test Cases:
-
You have three ways to use the Create Test Cases operation:
1a. from the menu More,
1b. from Test Cases panel,
1c. from the Test information panel. -
The Select issue(s) dialog shows a list of Test Case Templates with Active statuses from projects in which the user has browse permissions. To create Test Cases select Test Case Templates you want to add to the Test Plan from the list. After selection, click Select.
NoteTest cases are created in an order that reflects the order of the Test Case Templates selected in the Select issue(s) dialog (from the beginning to the end of the list).
NoteThe Test Case Template used at least once when creating a Test Case is highlighted in yellow on the list.
-
When the Test Cases are created a progress bar is displayed in the Test Plan view. If it is necessary to interrupt operation, you can Abort Create Test Cases using the button below the progress bar.
NoteIf you use the Abort Create Test Cases option, then creating Test Cases will end when the button is pressed.
Result
You have created Test Cases from selected Test Case Templates in the Test Plan.
Delete Test Cases
This operation allows to deleting Test Cases from Test Plan. You can select which Test Cases have to removed if you made a mistake, for example during creating Test Cases.
Delete Test Cases operation is based on Jira Delete Issues permissions. Only users who have been granted this permission will be able to use the Delete Test Cases operation.
Steps
To delete Test Cases:
- Select Test Cases you want to delete.
- Click the Delete Test Cases operation from the Test information panel.
- Confirm your choice by clicking on the Delete button.
Result
Selected Test Cases and their execution have been removed from the Test Plan.
Link with Requirement
The Link with Requirement operation allows to link given Test Plan with requirements. This operation is connected with Requirement field on issue and Requirements tab in project configuration.
To read more about Test Plans and its connection to requirements, see Link with Test Plans.
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 Plan. After selection, click Select.
Note
The list can show:
- 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 Plan in Requirement field.
Update Test Cases
This operation allows you to update Test Cases based on two sources:
- Test Case Template
- Test Plan
Depending on the selected source for updating the Test Cases, the operation is based on different configurations.
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.
Update Test Cases based on Test Case Templates
This operation updates all not executed Test Cases based on the Test Case Templates fields. In this case, the Update Test Cases operation can be useful if you made a mistake while writing Test Case Templates and you want to change the content of created Test Cases from these Test Case Templates.
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 update Test Cases based on Test Case Templates:
- Click the Update Test Cases operation from the Test information panel or select from menu More.
- Select the Test Case Templates radio button.
- In the Fields to be updated on Test Case field, you can change the set of default fields or leave it unchanged. If you want to restore the default configuration, click Reset to default.
Note
If you do not have the Set fields on Update Test Cases operation permission, you cannot change the fields.
- 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 the Test Case Templates.
Note
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).
- After selection, click Update.
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.
Update Test Cases based on Test Plan
This operation updates all not executed Test Cases based on the Test Plan fields. In this case, the Update Test Cases operation can be useful if you want to propagate the field value from Test Plan to Test Cases at once, for example, the Fix Version/s field. This will save you time for completing the same fields on the Test Case multiple times.
The user can update fields that have the same context for Test Cases and Test Plan (fields exist on Test Case and Test Plan). Fields that are not on Test Cases and selected during the update will not be propagated.
Attachments are not updated from Test Plan to Test Cases.
The source of the default value for the Fields to be updated on Test Case field in the operation dialog is the Update TCs with fields from TPs option from the TestFLO settings. If there are no fields in the Update TCs with fields from TPs option, then the user has to select the fields to be updated in the dialog (field list is empty). You can also select specific fields in this option then the selected fields will be the default set of fields for the user.
Changing the fields in the operation dialog depends on the Set fields on Update Test Cases operation permission. If the user has this permission granted, 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 TPs configuration for other users. If the user does not have the Set fields on Update Test Cases operation permission and the set of fields is selected in the Update TCs with fields from TPs configuration, then the fields will update according to this configuration.
The user will not be able to perform the Update Test Cases operation, if the configuration Update TCs with fields from TPs is empty and they have no permission to change the fields in the dialog.
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 update Test Cases based on Test Plan:
- Click the Update Test Cases operation from the Test information panel or select from menu More.
- Select the Test Plan radio button.
- In the Fields to be updated on Test Case field, you can add fields or change the set of default fields or leave it unchanged. If you want to restore the default configuration, click Reset to default.
Note
If you do not have the Set fields on Update Test Cases operation permission, you cannot change the fields.
- 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 Test Plan.
Note
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).
- After selection, click Update.
Result
You have updated selected Test Cases from the Test Plan.
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.