1		Installing Gemini 5
1.1		Pre-requisite Checks
1.2		Installing Gemini 5 Using Automated Installer
1.3		Installing Gemini 5 Using Zip File
1.4		Upgrading 5.0 to 5.1
1.5		Upgrading 4.2 to 5.1
1.6		Using Windows Authentication
1.7		Setting up with Geckoboard
1.8		Setting up with Lucidchart
1.9		MS Project Connector
2		Getting Started with Gemini 5
2.1		Signing in to Gemini
2.2		Navigation in Gemini
2.3		AppNav Cards
2.4		Gemini Terminology
2.5		Features and Functions
2.5.1		The Grid
2.5.2		The Planner
2.5.3		Activity Page
2.5.4		Timeline Page
2.5.5		Roadmaps and Changelogs
2.5.6		Documents
2.5.7		Standard Reports
2.5.8		The Calendar
2.5.9		Burndown and Burnup Charts
2.5.10		Ad Hoc Reporting with Excel
2.5.11		The Data Import Wizard
3		Creating and Managing Tasks
3.1		Creating Tasks
3.2		Rapid Planning (Creating Multiple Tasks)
3.3		The View Item Page
4		Structuring Projects
4.1		Creating Projects
4.2		Components in Gemini
4.3		Versions in Gemini
4.4		Setting Project Defaults
5		Breeze - Email-to-ticketing
5.1		Introduction to Breeze
5.2		Breeze: Queues
5.3		Breeze: SMTP Servers
5.4		Breeze: Mailboxes
5.5		Breeze: Response Templates
6		Sentry - Testing in Gemini
6.1		Introduction to Sentry
6.2		Test Cases
6.3		Test Plans
6.4		Test Runner (Executing Tests)
6.5		Test Run History
7		Project Templates
7.1		Project Templates: Introduction
7.2		Project Templates: Process
7.3		Project Templates: Screens and Visibility
7.4		Project Templates: Process Workflow
7.5		Project Templates: Custom Fields
7.6		Project Templates: Menus
7.7		Project Templates: Status, Priority and Severity
7.8		Project Templates: Resolution
7.9		Project Templates: Links
7.10		Project Templates: Time
8		People and Permissions
8.1		Users
8.2		Groups
8.3		Permissions
8.4		Active Directory Integration and Windows Authentication
9		Code Review & Source Control Connectors
9.1		SVN Server Installation
9.2		Client Side Gemini Tortoise SVN Integration
9.3		Git Source Control Connector
9.4		Mercurial Source Control Connector
9.5		TFS Source Control Connector
9.6		Using Saucery for Code Review
10		Gemini 4
10.1		Getting Started
10.2		Installing
10.2.1		Requirements
10.2.2		Automated Installer
10.2.3		Microsoft Web Platform
10.2.4		Zip File
10.2.5		Scheduler Service
10.3		Upgrading
10.3.1		Upgrading Existing Installations
10.3.2		Upgrading 4.1.x to 4.2
10.3.3		Upgrading 4.0.x to 4.2
10.3.4		Upgrading 3.7.x to 4.2
10.3.5		Upgrading 3.6.x to 4.2
10.3.6		Upgrading 3.5.x to 4.2
10.3.7		Upgrading 3.1.x to 4.2
10.3.8		Upgrading 3.0.x to 4.2
10.3.9		Upgrading 3.0.0 to 4.2
10.3.10		Upgrading 2.2 to 4.2
10.3.11		Upgrading 2.1.x to 4.2
10.3.12		Upgrading 2.0.x to 4.2
10.3.13		Upgrading 1.9.1 to 4.2
10.3.14		Upgrading 1.9/1.9a/1.9b to 4.2
10.3.15		Upgrading 1.8.x to 4.2
10.3.16		Upgrading 1.7 to 4.2
10.3.17		Upgrading 1.6.3 to 4.2
10.4		Projects
10.4.1		Project Concepts
10.4.1.1		Grouping Projects
10.4.1.2		Components
10.4.1.3		Versions
10.4.1.4		Roadmap
10.4.1.5		Change Log
10.4.1.6		Dashboard
10.4.2		Project Customization
10.4.2.1		Project Settings
10.4.2.2		Single, Multiple Item Options
10.4.2.3		Item Type, Priority, Severity Options
10.4.2.4		Default Values
10.4.2.5		Components
10.4.2.6		Versions
10.4.2.7		Project Attributes
10.4.2.8		Which Fields Are Displayed?
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
10.5.7		Comments
10.5.8		Hierarchy
10.5.9		Links
10.5.10		Recurrence
10.5.11		Estimates & Time Logs
10.5.12		Source Control Links
10.5.13		Audit Trails
10.5.14		Workflow
10.5.15		Filter Items
10.5.15.1		Using the Filter
10.5.15.2		Saving and Reusing Filters
10.5.15.3		Cross Project Roll-ups
10.5.16		Patterns
10.6		Planning Board
10.7		Time Management
10.7.1		Time Reports
10.7.2		Recording Time
10.8		Notifications
10.8.1		Project Alerts
10.8.2		Item Watchers
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		Management
10.10.1		Administration
10.10.1.1		General Configuration
10.10.1.2		SMTP and Notifications
10.10.1.3		Projects
10.10.1.4		Custom Fields
10.10.1.5		Item Management
10.10.1.6		Test Management
10.10.1.7		Licensing
10.10.2		Users & Security
10.10.2.1		User Management
10.10.2.2		Global and Project Groups
10.10.2.3		Working with Global Groups
10.10.2.4		Working with Project Groups
10.10.2.5		Available Permissions
10.10.2.6		Project Resources
10.10.2.7		Assigning Permissions to Projects
10.10.2.8		Windows Authentication
10.10.2.9		Active Directory Integration
10.11		Using Add-on Products
10.11.1		Visual Studio 2008/2010
10.11.2		Gemini Desktop
10.11.3		Microsoft Outlook
10.11.4		Converse
10.11.4.1		Installation
10.11.4.2		Core Mailbox Setup
10.11.4.3		Selecting Emails to Process
10.11.4.4		Manipulating Email Content
10.11.4.5		Outbound Notifications
10.11.4.6		Project Mapping
10.12		API
10.12.1		Introduction
10.12.2		Enabling API support
10.12.3		Authentication
10.12.4		Response Formats
10.12.5		.NET Quick-start
10.12.6		Schema Reference
10.12.7		Administration API
10.12.8		Alerts API
10.12.9		Custom Fields API
10.12.10		Groups API
10.12.11		Items API
10.12.12		Projects API
10.12.13		Users API
10.12.14		Testing API
10.13		User Profile

194 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.