- 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
Run automated tests from Test Plan
To run automated tests from Test Plan you need to use a dedicated operation called Run automated tests. This operation lets you trigger automated tests from integrated CI Servers in the Test Plan. After choosing the operation, you can select the appropriate CI server from which the tests are to be run, and after all the tests are completed, the results will be pulled to the Test Plan as a Test Cases with the appropriate statuses.
The operation will be displayed in the Test Plan when the given project will be configured in the CI Servers configuration.
To use the Run automated tests operation, the user must have Jira Create and Edit issues permissions.
The Run automated tests operation in Test Plan can be restricted to certain users/groups/roles in the TestFLO Permissions.
Steps
To use the Run automated tests operation:
-
Click the Run automated tests operation from Test information panel or select from menu More.
-
Select appropriate CI Server from the list.
-
Select the automated tests you want to run. Depending on the CI server selected in the previous point, an option will be displayed:
- Build plan for the Bamboo CI server build plans
- Job for Jenkins CI server jobs
-
Select TC Creation Strategy:
- Update and create new - Updates existing Test Cases and creates new Test Cases based on the results of the automated tests. If Test Plan doesn’t contain any Test Cases the strategy will only create new Test Cases.
- Update existing - Updates existing Test Cases based on the results of the automated tests.
-
Select Import results to:
- Current iteration - Creates Test Cases in the current iteration in Test Plan.
- New iteration - Creates Test Cases in the new iteration in Test Plan. If in the Test Plan no Test Cases exist then new iteration will be not created.
-
Click Run.
-
You have started the process of creating Test Cases. In the Test Cases panel you will see the progress of Running CI Automated Tests. The status of running tests you can track on the Automated test runs page.
NoteYou can execute the same test run twice or more within a given Test Plan without having to wait until the first test run is completed. All pending test runs are queued in the Activity tab on the Automated test runs page.
NoteWhile automated tests are running other operations in the Test Plan are blocked to avoid affecting the import of test results.
Result
After Run automated tests operation is complete the Test Cases will be created on the Test Plan with the appropriate test names and statuses. The connection between the created Test Cases and the automated tests is stored in the Automation Test Key. If the creation of Test Case Templates is enabled then for each Test Case a Test Case Template will be created as well. In the Test Case, the key of the Test Case Template will be visible in the TC Template field.
By default, the Automation Test Key custom field is not present in the Test Case and Test Case Template view. For more information, see Automation Test Key.
If the creation of Test Case Templates is enabled then you can reuse tests once again. You can only add selected Test Case Templates to the Test Plan to limit which test results are to be imported. You can also link the Test Case Templates and their executions in Test Cases with Requirements to track their connection in TestFLO Reports.
You can also create a Test Case Template first and then add it to the Plan Test and use Run automated tests. This approach will require knowledge of the special key for the test from CI Server, which is stored in the field Automation Test Key in the Test Case Template and Test Case.
Automation Test Key sample value:
[package name].[class name].[method name]
com.deviniti.jira.plugins.steps.StepsServiceTest.shouldSetStepsComment