This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities. |
6 | Sentry - Testing in Gemini |
sentry
|
||
6.1 | Introduction to Sentry |
usage
items
sentry
|
||
6.2 | Test Cases |
usage
items
sentry
|
||
6.3 | Test Plans |
usage
items
sentry
|
||
6.4 | Test Runner (Executing Tests) |
usage
items
sentry
|
||
6.5 | Test Run History |
usage
items
sentry
|
||
10.9 | Test Management | |||
10.9.1 | Approach | |||
10.9.2 | Plans | |||
10.9.3 | Cases | |||
10.9.4 | Runs | |||
10.9.5 | Traceability | |||
10.9.6 | Filtering | |||
10.10.1.6 | Test Management |
admin
|
||
10.12.14 | Testing API |
api
|
15 documents found.
Gemini provides the means to trace Requirements, User Stories, Change Requests and other items right through the testing process to final test outcomes.
Traceability is available from within Test Plans and from the Cases tab.
When you test something specific in a Test Case you can optionally link it to Items within the project. For example a Test Case may well be associated with Requirements, Bugs or Change Requests – so Traceability clearly identifies this link between Items and Testing.
When inside a Test Plan you can choose to view Traceability.
Doing so will bring up the Test Plan’s Traceability report as follows. This report will show all Test Runs for the Test Plan and detail all the Test Cases and their outcomes.
You can choose to view Test Plan Traceability from either an Item or Test Case perspective. If you select Items perspective you will see all testing activity organized by Items (e.g. Bug).
Each Test Case can be analyzed to determine Test Run results (PASS OF FAIL) as well understanding whether new Bugs were logged as a result of testing activities.
Items (e.g. Requirements, Bugs or Change Requests) being tested by a Test Case can be determined as follows.
Each Test Run executed that is associated with the Test Case will show as either PASSED or FAILED.
Any new Bugs logged as a result of the Test Run are identified.