2		Getting Started with Gemini 5	projects templates
2.5.1		The Grid	Excel
2.5.2		The Planner
2.5.3		Activity Page	time
2.5.4		Timeline Page	time
2.5.5		Roadmaps and Changelogs	time
2.5.8		The Calendar	projects add-ons time plugins ms-outlook
2.5.9		Burndown and Burnup Charts	time reporting
3		Creating and Managing Tasks
3.2		Rapid Planning (Creating Multiple Tasks)	projects templates
3.3		The View Item Page	projects sentry
6.1		Introduction to Sentry	testing sentry
6.2		Test Cases	testing sentry
6.3		Test Plans	testing sentry
6.4		Test Runner (Executing Tests)	testing sentry
6.5		Test Run History	testing sentry
10.5.16		Patterns	projects
10.7.2		Recording Time

18 documents found.

The Test Runner

The Test Runner is a Sentry app that exists in Test Plans.

To initiate or resume a test:

Select the Test Plan that you wish to execute and open the Test Runner section. You will see the following:

Fig 1.0 Test Runner as it would appear if incomplete tests existed in the system

If there are no incomplete tests in the system then the drop down list that points to a “New Run” will not appear. If there are incomplete tests in the system and you click on this drop-down then the incomplete runs will be shown and you can select one from the list and resume testing at the next case from the last one tested.

Testing Cases

To create a new Test Plan instance, simply enter the name that you would like to give to this instance. You should consider a naming convention for your instances that might for example identify who executed the test and capture the date/time of the test e.g. “MK-AUG21-01” for test number 1 carried out by Mark King on August 21st.

Whether you are starting a new test or resuming one that is in progress, click on the “Start” button and you will be shown the Test Case screen as illustrated below:

Fig 2.0 Test Runner with 7 step Test Case where Steps 1&2 passed and Step 3 failed

As the screen above shows, the Test Runner shows you all of the Cases and all of the Steps in the case. You may also add attachments to help expand upon your test step, perhaps a screenshot of a failure or a file showing a system log entry or debug trace.

There are 5 options available to the tester:

• Reset – select a step and click on reset and that particular Test Case will be reset to that step. This action will not affect any other Test Cases in the Test Plan, either preceding or following the step that the Test Case was reset to, nor will it unwind the creation of any items (issues/bugs) that were raised before the Reset. This option is not available on the first step of a Test Case.
• Pass – the step will be passed and the step indicator as well as the step description will be moved onto the next step. If the passed step was the last in the Test Case then the Test Runner will automatically move onto the first step in the next Test Case.
• Fail – a description must be entered in the Actual Results box for a step to be marked as failed. If a step is failed then the “Fail Run” button will appear and the user can fail the entire run from that point. The step can be failed but the Test Case allowed to proceed to the next step. Unless the run was failed, if the failed step was the last in the Test Case then the Test Runner will automatically move onto the first step in the next Test Case.
• Fail & Log – after you have entered the description of the failure you will be shown the Create Item screen from where you can select the project and the type of item that Gemini should create as a result of the test failing (task, issue, bug etc.). You can create this item in any project to which you have access.
• Fail Run – will only appear after you mark a step as failed. If you fail the run then the Test Plan instance will be marked as complete and will no longer appear in the drop-down list of incomplete tests.

If you pass through all of the steps in all of the cases then regardless of whether on not certain steps failed, the Test Plan instance will be marked as completed.