1.9		MS Project Connector	appnav Project
2		Getting Started with Gemini 5	usage projects templates
2.5.1		The Grid	usage Excel
2.5.2		The Planner	usage
2.5.3		Activity Page	usage time
2.5.4		Timeline Page	usage time
2.5.5		Roadmaps and Changelogs	usage time
2.5.8		The Calendar	usage projects add-ons time plugins ms-outlook
2.5.9		Burndown and Burnup Charts	usage time reporting
2.5.11		The Data Import Wizard	admin database templates Excel migration
3		Creating and Managing Tasks	usage
3.1		Creating Tasks	projects templates
3.2		Rapid Planning (Creating Multiple Tasks)	usage projects templates
3.3		The View Item Page	usage projects sentry
6.1		Introduction to Sentry	usage testing sentry
6.2		Test Cases	usage testing sentry
6.3		Test Plans	usage testing sentry
6.4		Test Runner (Executing Tests)	usage testing sentry
6.5		Test Run History	usage testing sentry
10.5		Item Management
10.5.1		Overview
10.5.2		Creating
10.5.3		Editing
10.5.4		Viewing
10.5.5		Visibility
10.5.6		Custom Fields	custom-fields
10.5.7		Comments
10.5.8		Hierarchy
10.5.9		Links
10.5.10		Recurrence
10.5.11		Estimates & Time Logs	time
10.5.12		Source Control Links
10.5.13		Audit Trails
10.5.14		Workflow
10.5.15		Filter Items	find-filter
10.5.15.1		Using the Filter	find-filter
10.5.15.2		Saving and Reusing Filters	find-filter
10.5.15.3		Cross Project Roll-ups	find-filter
10.5.16		Patterns	usage projects
10.7		Time Management	time
10.7.1		Time Reports	time
10.7.2		Recording Time	usage
10.10.1.5		Item Management	admin
10.12.9		Custom Fields API	custom-fields api
10.12.11		Items API	api

45 documents found.

Test Cases, the basic unit of testing in Gemini, are delivered as a Process in a Project Template.

Out-of-the-box, a Test Case consists of at least 3 Custom Fields:

• Test Type – a drop-down list of numerous types of tests
• Pre-conditions - a description of the anticipated state before the test begins
• Expected results – a description of what the outcome of the test should be

In addition, Test Cases, since they are derived from Gemini’s unique Project Templates, can contain multiple, user-defined fields such as Status, Severity, Priority,Resource(s), Component(s) and such complex data as attachments. It is entirely up to you what data your Test Cases capture, you can select from the multitude of fields in Gemini’s baseline or if there are additional fields you require you can add them as Custom Fields.

The standard Test Case model is contained in the Project Template called “SENTRY”. It is recommended that if you wish to modify your Test Cases (or Test Plans), you duplicate this Template, creating a new one so that you always have the baseline as a point of reference.

Test Case Apps

Test Cases contain 3 Sentry Apps: Items Tested, Test Steps and Test Plans. Of these, only Test Steps are mandatory.

Items Tested

This app allows you to select items (bugs/issues/stories etc) from any project in Gemini that are to be tested in the Test Case. You do not have to do this as your Test Case can stand entirely on its own and not relate to any item being tracked.

Fig 1.0 Search box for “Items Tested” enter any part of the key or title and Gemini will search the database

Test Steps

This app allows you to define one or more steps to be contained within your Test Case. Each Step consists of an action that the tester is to take and the expected outcome. Since it is not possible to execute a Test Case that has no Steps this app is mandatory for Sentry to work as a testing platform. Steps can be edited using Gemini’s inline editing (just click in the field and change the value), deleted by clicking on the Delete icon , or reordered by drag-dropping using the grab handles on the left hand side of the step.

Fig 2.0 Test Steps – Step (action for tester) and Expected Results.

Test Plans

The Test Plans app allows you to see which cases the Test Case is in. It will also show you the creator of the Plan, and a breakdown of the success/failure of executing the test with a count of the number of test runs.