Home Home
  login

Gemini Community Support Site

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.




Index Runs
Previous  |  Next

 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
View  |  Print  |  PDF

15 documents found.


Runs

testing

Test Runs can be started from either inside Test Plans or Test Cases.

By default, only two fields are required:

  • Run Name – give a short yet succulent title for the Test Run
  • Run Description – provide a more detailed description detailed the Test Run

image

NOTE: you must provide a Run Name before starting the Test Run.

Define Your Own Test Run

Use Custom Fields in order for you to totally customize the Test Run screen.

When defining a Custom Field for use within Testing, ensure you select the following option on the Custom Field definition.

image17

Gemini Administrators can then define screens for use on Test Runs as follows:

image

Once you have a screen for use on Test Plans, Gemini Administrators can reference it as follows:

image

Running Tests

A Test Run may consist of one or more Test Cases. Every Test Case is represented as below.

image

 

1 – Expandable Test Case Summary

Click on the “>” symbol to see more details about the Test Case being run.

image

 

This provides a handy summary of what you need to do as well calling out the expected result.

2 – Run Test Step

Every Step can be run individually and in sequence. Just click “play” to start. Once you have performed the Step, just click “stop”.

image

 

You can then record either a PASS or FAIL. When marking as PASSED the recording of the Actual Result is optional. However, when marking as FAILED the recording of the Actual Result is required. You can also raise a new Bug report as a result of the FAILED test.

image

Eventually you will see the outcome of each Step, with expected result recorded and options to re-run the Step or add Attachments.

image

2 – Quick Pass All / Fail All Options

As a convenience you can either mark all Steps in a Test Case as PASSED or FAILED.

image


Previous  |  Next