- 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
Last updated Aug 31, 2021
Glossary
Below you will find a brief explanation of the terms we use in TestFLO.
| Term | Description |
|---|---|
| Test Case Template (TCT) | This is a non-executable test specification that can be multiplied across Test Plans. TCT is represented as a Jira issue, which means it has workflow and attributes. Test Case Template can be organized in the test repository folder tree. Read more here. |
| Test Case (TC) | This is an executable instance created from a Test Case Template. TC can be created from TCT or directly on the Test Plan. Test Case is represented as a Jira sub-task. Read more here. |
| Test Plan (TP) | This issue aggregates Test Cases to be executed. On TP you can plan execution, set order of Test Cases, or put them into groups. Test Plan is represented as a Jira issue. Read more here. |
| Master Test Plan | This issue is an optional issue type that groups Test Plans. MTP can get you a better view of Test Plans execution. Test Plan is represented as a Jira issue. Read more here. |
| Defect | It can be simply defined as a difference between expected and actual. In TestFLO, a defect can be represented by any issue from Jira and you can report it in a Test Case or for a given step in the Steps field. |
| Requirement | A document that describes the needs that a particular product or service should have. It can be covered by Test Case Templates. Requirements can be either a Jira issue or a sub-task. You can freely configure which type will be treated as a requirement in TestFLO. Read more here. |
| Steps field / Steps panel | This custom field allows defining a list of instructions that are necessary to perform the test. Steps field appears on Test Case Template and Test Case. Read more here. |
| Preconditions | A custom field that can help you determine the list of conditions that have to be done before a test is run. Preconditions field appears on Test Case Template and Test Case. Read more here. |
| Preconditions repository | A place where you can store previously written preconditions for use later in Test Case Templates or Test Cases. The repository is available in every project and their content can be shared with other projects. Read more here. |
| Test Repository | A place in a project where you can organize created Test Case Templates in a folder tree structure. Read more here. |
| Test repository folders field/panel | A custom field that is available on Test Case Template. With this field, you can assign a given TCT to an existing folder without going to the Test Repository folder view. Read more here. |
| Test executions / Test Case execution | The first or next execution of a Test Case in a given Iteration. We treat the execution as marking the Test Case and/or Steps with the appropriate status, which is set as final. Read more here. |
| Test Plan Iteration / Iteration | Test Plan Iterations is a process in which you can create and perform once again all or selected Test Cases included in a given Test Plan. Read more here. |
| Panel Filter Result (PFR) | A panel showing a list of related issues with the issue a user is viewing. For example, panels can display coverage (TCTs), test progress (TC), and defects for a given requirement. Read more here. |
| Automated test runs | A place in a project where you can view a list of all active and finished automated test runs that users requested from a given Test Plan using the Run automated tests operation. Read more here. |
| Test Reports | A place where you can view all reports from TestFLO. Read more here. |
