Testing
Do you need to validate and verify your product? Or maybe you need to create a report that shows the connection between regulations, requirements, and tests?
Then look no further: use Jama Connect test capabilities to guide your teams through the testing process, so you can validate and verify your products and systems.
Let's define our terms
Test case | Test cases live within a project. They can be organized into a separate test suite project or into a project alongside corresponding requirements. They contain the steps a tester or script uses to validate and verify associated requirements. Test cases can be associated with one or multiple test plans. |
Test plan | Test plans live within a project. They contain a description of the strategy and objective for testing a system or subsystem. Test plans can include test cases from the same project or from different projects. |
Test group | Test groups live within a plan. They function as an optional method to organize test cases into collections within the plan. |
Test cycle | Test cycles live within a plan. They function as a container to organize a specific set of cases that are executed together. When a case is associated with a cycle, a corresponding test run is created in that cycle. |
Test run | Test runs live within a cycle. They are the record of results for an executed test case. |
Defect | Defects live within a project. They are a record of an error or defect that was discovered while executing a test run. When a defect is logged during test execution, it is traced to the originating test run to upstream test cases and requirements through the relationship configuration. |
What's involved in testing?
Here's a typical workflow:
1 | Create coverage | Create specific or generic test cases to validate upstream requirements. Create one or more relationships between test cases and requirements. Use the Trace View to check for gaps in test coverage between your requirements and test cases. |
2 | Devise a plan | Create a test plan and describe which requirements need to be tested and the strategy for testing. Associate all test cases with the plan to verify and validate the intended requirements. Optionally, organize the test cases into groups within the plan. |
3 | Execute plan | Create one or multiple test cycles in the test plan. Associate all or a subset of test cases from the test plan with each test cycle. A test run is created in the test cycle for each associated test case. Execute the test runs in each test cycle. |
4 | Monitor progress | Set up filters, dashboards, and trace views to monitor requirement coverage, track testing progress for each cycle, and keep an eye on high-priority defects. |
5 | Review and report results | Send the entire test plan or just a single test cycle to review. Generate a report showing results, such as the Test Details Grouped by Test Cycle or the Test Details Grouped by Test Case. |