Technical Documentation for Goldfinger TestRay Plugin

Goldfinger TestRay displays requirements based on projects and releases, providing a comprehensive view into your entire development environment. Goldfinger TestRay provides a dashboard within Jira to track requirements against specific releases. In addition, TestRay displays charts related to specific requirements and due dates across projects.

Goldfinger TestRay for Jira - Technical Documentation

Overview

Goldfinger TestRay displays requirements based on projects and releases, providing a comprehensive view into your entire development environment. Goldfinger TestRay provides a dashboard within Jira to track requirements against specific releases. In addition, TestRay displays charts related to specific requirements and due dates across projects.

By simply clicking on the Goldfinger TestRay link in the Jira menu bar, the Goldfinger TestRay dashboard appears. From the dashboard, selecting a project and release from the dropdown menus and clicking the Query button displays the requirements data in a dashboard.

Additional functionality include drilling down on specific requirements / issues by clicking a requirement in the matrix. The information from that requirement / issue can be displayed by clicking on the defect link.

Architecture

Goldfinger TestRay leverages Jira 6's architecture, including Google Gadgets and custom issue types, allowing all test management activity to be captured within Jira.

Use Case

The Test and Development phases of the software development life cycle process are seen as key indicators to the success and efficiency of a product being available to the general public on time. Here's a usage scenario of how Goldfinger TestRay can add value to your workflow.

Questions Being Answered

What test case is associated with a requirement?
What defect is associated with a test case?
What is the requirement burndown chart?
How many defects are related to the requirement?
What's the relational matrix between requirements and test cases?

Use Case Example

Project manager defines a new version for project release.
Project manager/Quality Assurance (QA) creates requirements associated to the version and estimates the effort in time.
Project manager/QA creates test suites and test cases for each requirement.
QA team creates issues when the tests fail.
Project manager monitors the project in TestRay dashboard using the traceability and planning tabs.

For more information, please review the Usage Guide.

Requirements

What's Needed

To successfully install and configure Goldfinger TestRay for Jira 6, you will need to verify that you have satisfactory versions of several programs, and the appropriate permissions for installation and configuration.

Atlassian Jira

The plugin is compatible with Jira 6.0
- Version 2.3 of the plugin is not compatible with Jira version 3.x
- Version 4.0 of the plugin is not compatible with Jira version 4.x
- For more information on Atlassian Jira, please visit the Atlassian Jira website at: www.atlassian.com

Java 6

Java is available from the Oracle website at: www.oracle.com

Administrative permissions

You will need access to the Jira server
You will need administrative access to Jira

In addition, before you read this guide, you should be familiar with the following Jira concepts:

Where to Get Help

Go2Group provides support for its entire line of products by telephone, email, and a product-specific customer support ticket system:

By telephone	877 442 4669
By email	support@goldfingerholdings.com
By ticket	Jira.go2group.com

The support site above is self-administered - feel free to create and manage your account. For additional support information, please review the TestRay for Jira 6 support page.

For support with Jira, please contact your Atlassian representative.

What's New in This Version

Go2Group is excited to announce the availability of version 6.x of Goldfinger TestRay for the latest version of Jira! For a updates on versions, visit Recent Updates.

Installation

Installation Overview

This installation guide explains how to install the plugin using the provided installer. For details on manual installation, please contact us.

Installation Assumptions

Before you begin, please make sure that you have obtained:

Internet access during installation in order to download plugin installer within Jira from Atlassian plugin Exchange.
A license key for Goldfinger TestRay. This can be generated using the plugin manager in Jira.
Appropriate privileges for Jira.
Privileges to install software on the Jira server and restart the application.

Installation Steps for plugin Installation with Atlassian Plugin Exchange.

Login to Jira as a system administrator. Click on the "COG" icon on the top right corner of the page and select Add-ons.
UNKNOWN ATTACHMENT
In the "Find new add-ons" page, search for TestRay.
UNKNOWN ATTACHMENT
If you would like to try the plugin before your purchase, click on the "Free Trial" option to generate a 30 day trial license. If you would like to purchase the plugin, click on "Buy Now".
Once you have installed the plugin, you are required to perform a re-index of your Jira instance. Click on the COG icon on the top right and select "System".
UNKNOWN ATTACHMENT
Look for the "Indexing" option under the Advanced options on the left menu bar.
UNKNOWN ATTACHMENT
Click on Re-index.
UNKNOWN ATTACHMENT
Your installation is complete. Go to the Add-ons menu in the administration page and you will see additional configuration options for TestRay in the left menu bar.
UNKNOWN ATTACHMENT
UNKNOWN ATTACHMENT

Configuration

Overview

The configuration of Goldfinger TestRay is straight-forward:

Add license key
Create custom fields
Create custom issue types
Create links

The following steps provide details for configuration Goldfinger TestRay.

Before continuing, please ensure you have administrator rights to Jira!

Base configuration

The Goldfinger TestRay plugin configuration is automated. It automatically creates and enables required Jira functions if they are inactive.

The TestRay Configuration page will have the configuration created for you. But you have the option to edit the custom fields and issue types assigned to TestRay.

Configure custom fields used by TestRay
UNKNOWN ATTACHMENT
UNKNOWN ATTACHMENT

Creating a test project

The TestRay Configuration page also provides you with an option to create a test project. Simply click on the "Create Test Project" button. You can delete this project by using the "Delete Test Project" button on the same screen (only available if test project is already created).

UNKNOWN ATTACHMENT

Configuring issue types

TestRay basically uses 6 types of issues. The below table helps us understand the different types and how they are used.

Requirements, SubRequirements and bugs	Requirements and bugs are issues reported. SubRequirements are subtasks to Requirements.
Test cases and Sub-Tests	A test case represents a single test case and is tied to requirement and/or test suite. A Sub-Test is a SubTask of a test case. A test suite is a group of test cases.
Test Plans	A test plan is a parent issue holding a group of test cases. It summarizes the result of each test case that belongs to the test plan.

TestRay comes with a default configuration for all the above issue types. But you can also configure the plugin to use issue types of your preference.

Issue type context

If you choose to use other issue types, please make sure the issue type is available in the project's issue type scheme. More information about issue type schemes can be found here.

UNKNOWN ATTACHMENT

Configuring custom fields

TestRay plugin requires 7 custom fields to maintain the mapping between requirements, test cases, test plans and test suites. These custom fields are automatically created when you install the plugin.

Parent Custom Field and Parent Link	Parent custom field is used by requirements and test cases to link to a parent requirement or test case. This allows us to create a hierarchy of requirements and test cases. When a requirement or test case is linked to it's parent, a Jira issue link is also created. The type of link is determined by the Parent Link.
Requirement Custom Field	Used by Test Cases, SubTests and Bugs to link to one or more requirement.
Test Case Custom Field	Used by Requirements, Bugs and Test Plans to link to one or more test cases.
Test Case Result Custom Field	A Text Area field used by Test Cases where test results are added to a cumulative log.
Test Case State Custom Field	A select field used by Test Cases to indicate if the test is "In-Progress", "Passed", "Failed" or "Cant Test".
Test Plan State Custom Field	A read-only field used by Test Plans. This field is set automatically when a Test Plan is closed and displays the minimum Test Case State of all the Test Cases for the Test Plan.
Test Suite Custom Field	Used to group Test Cases into one or more Test Suites.

TestRay automatically creates the custom fields for you upon installation. But you can configure the plugin to use custom fields of your choice.

UNKNOWN ATTACHMENT

Workflow and Statuses

TestRay plugin automatically creates workflows and statuses upon installation. Three statuses named "Can't Test", "Failed" and "Passed" are created. Take a look at the workflows that have been created by TestRay.

Click on the COG icon on the top right corner of the page and choose "Issues". Select "Workflows" from the left menu bar.
UNKNOWN ATTACHMENT

Please review the Usage Guide to better understand how to manage test cases, requirements, and test suites within Jira using Goldfinger TestRay.

Test Suites Management

Open the TestRay Test Suites Management link in Administration->Add-ons to access the Test Suites Management panel.

UNKNOWN ATTACHMENT

Test Suites Management panel allows you to operate with Test Suites and to see the lists of issues which are linked to the Test Suites. A TestRay test suite can belong to one of three container types or scope.

Global	Available to be linked to an issue in all Jira Projects. This is the default option.
Project	It allows you to make a test suite available only in the selected project.
Category	Available in those Jira projects which are assigned to the project category.

Adding a new test suite

To add a new test suite, select the container, enter a name and click "Add".
UNKNOWN ATTACHMENT

Edit/Delete a test suite

To edit/delete a test suite, click on "Edit" on the operations column of the test suite. The edit option allows you to rename the test suite.

UNKNOWN ATTACHMENT

Merge/Split/Copy a test suite

Clicking on "More actions" in the Operations column of a test suite, allows you to Merge, Split or Copy a test suite.

Merge to	Allows to merge the Test Suite to more inclusive Jira Container.
Split to	Allows to split the Test Suite to less inclusive Jira Container.
Copy to	Allows to copy the Test Suite to another Project.

You can find more information about Test Suites in our Usage Guide in /wiki/spaces/SRT4/pages/24084530 .

Dashboard

The Goldfinger TestRay dasboard is available for project administrators by default. You can also configure other Jira groups to have access to the TestRay dashboard. Take a look at the TestRay Dashboard screenshot below.

Configuration options available

Screenshots

Number of Requirements shown on the Traceability Dashboard
Number of Test Cases shown on the Traceability Dashboard
Number of Requirements shown on the Release Planning Dashboard
Number of Test Cases shown on the Release Planning Dashboard
Number of Related Issues On Issue Edit Screen
Number of Related Issues on Issue View Tab
Number of Related Issues on Test Plan Project tab
Use FishEye
Show information on linked Test Cases in the TestSuites Project tab
Expand linked Test Plans section of the Test Case State field on Test Case edit screen
Remove Status for the test cases on TestRay tabs and panels
Use Subtests instead of Test Cases in the Test Plans
Hide Test Cases on Test Cases Coverage tab of Requirements when Subtests enabled
Delete Subtests if removed from a Test plan
Use custom design
Issue Type colors
Jira groups to access TestRay Dashboard

UNKNOWN ATTACHMENT

On this configuration screen we can configure plugin interface settings.

1. This parameter defines the maximal number of requirements for requirement tree level in Traceability matrix.

2. In this field you can specify which number of test cases will be displayed in the Traceability table.

3. and 4. define the number of issues which will be displayed in the Release Planning Dashboard.

5. This parameter represent the number of issues which will be available on the minipages of custom fields. Image below show Requirement custom field for parameter value 1.

UNKNOWN ATTACHMENT

6. Here you can configure the number of issues on a tree level for requirement tree and the number of test cases that will be shown in issue tabs.

7.This field controls the number Test Plans to display on Test Plan project tab.

8. Check this option to enable TestRay Fisheye integration. You can find more information about the configuration of Fisheye integration in /wiki/spaces/SRT4/pages/24084524 .

9. Mark this option if you want to enable extended mode for Test Case inrofmation blocks in the Test Suites Project tab (see corresponding Usage Guide for more information).

10. This option holds the list of Test Plans linked to a Test Case on Test Case State field so that the list will be always expanded (see corresponding Usage Guide section for more information).

11. If this option is checked then TestRay will remove the test case Status information from all panels and tabs.

12. Enable this option to use Subtests in place of Test Cases in Test Plan management. This option also affects to the visibility of Create Bug option in More actions menu: the enabled feature hides the option from the menu of Test Cases.

13. This option enables the simple design of issue items on TestRay tabs, panels and custom fields, see images below:

UNKNOWN ATTACHMENT

The users from the groups in the right list box have access to TestRay dashboard. You can select groups in the left list box and grant them permission to access TestRay dashboard by pressing the button at the bottom of the list box. To revoke granted permission select groups at the right list box and press the button at the bottom of the list box.

Test Case State Automation

TestRay plugin comes bundled with a post-function and a screen to help you setup a post-function to change the state of a test case. Click here for information on setting up post-functions in your workflow. Click here for information on how to setup a screen for a transition in your workflow.

Post Function: Change TestRay Test Case State field from custom list

UNKNOWN ATTACHMENT

Screen: Synapse Test Case Results Automatic Screen

UNKNOWN ATTACHMENT

The below screenshots show three screenshots. Screenshot (1) displays a new user transition that has been added to the workflow. Screenshot (2) displays the screen that has been added to the transition. Screenshot (3) displays the change in test case state and results.

Screenshot (1)
UNKNOWN ATTACHMENT
Screenshot (2)
UNKNOWN ATTACHMENT
Screenshot (3)
UNKNOWN ATTACHMENT

Test plan workflow

This section belongs to the Test Plan section of the Usage manual. If you upgrade TestRay from previous version, TestRay will create Test Plan workflow and you have to assign this workflow to your workflow schemes.

Follow the steps below to update the workflow scheme.

Open Jira Administration section and follow the Workflows link. You will see that TestRay Test Plan Workflow was created but now is inactive. Then open the Workflow Schemes link.
UNKNOWN ATTACHMENT
You will see existing workflow schemes. If the scheme which you want to change is active then you should disassociate projects from the scheme. In this example SYNAPSETEST Project associated to TestRay Automatic Workflow Scheme. In this example we make the copy of active Workflow scheme, then associate Test Plan Workflow to new Scheme. Then we will associate the project from old scheme to new scheme. So copy Workflow Scheme.
UNKNOWN ATTACHMENT
Open the Workflows link.
UNKNOWN ATTACHMENT
Open the Assign a workflow link.
UNKNOWN ATTACHMENT
Assign Test Plan workflow to the scheme.
UNKNOWN ATTACHMENT
Now workflow assigned to the scheme. Come back to workflow schemes.
UNKNOWN ATTACHMENT
We will edit our scheme name to new. Then we will open associated project.
UNKNOWN ATTACHMENT
UNKNOWN ATTACHMENT
On the Project page open the More link in the Workflows section.
UNKNOWN ATTACHMENT
Open the Actions menu and choose the Use a different scheme option.
UNKNOWN ATTACHMENT
Choose new workflow scheme and press the Associate button.
UNKNOWN ATTACHMENT
Associate statuses from the old scheme to the new one.
UNKNOWN ATTACHMENT
UNKNOWN ATTACHMENT
After process is complete your workflow scheme with TestRay Test Plan is active.
UNKNOWN ATTACHMENT

FishEye integration

From Goldfinger TestRay v4.1 integration with Fisheye is available. You can map your Jira projects to Fisheye repositories during TestRay configuration.

What's Needed

To successfully configure Goldfinger TestRay integration with Fisheye, you will need to verify that your Jira instance and FishEye + Crucible installation is configured and connected together according to the Atlassian Guide .

Configuration

Enable Fisheye Integration in the TestRay Dashboard configuration page, select "Advanced Settings". Check the "Use Fisheye" option and click "Set".
UNKNOWN ATTACHMENT
Enter your fisheye connection parameters and click "Set".
Map Fisheye repositories to Jira projects. See /wiki/spaces/SRT4/pages/24084530 of /wiki/spaces/SRT4/pages/24084530 for more information.

Uninstallating TestRay Plugin

Click on the COG icon on the top right corner of the page and select Add-ons. Click on the "Manage add-ons" option on the left menu bar.
Locate the Goldfinger TestRay plugin in the list of installed plugins and click "Uninstall".
UNKNOWN ATTACHMENT

Tips and Troubleshooting

General Suggestions

Go2Group provides technical support for its entire line of products. If you run into any issues when installing or configuring the Go2Group Perforce Plugin for Jira, please contact us.

Updates and Upgrades

Go2Group provides regular updates to its products. These updates include performance enhancements and minor bug fixes.

To review previous, current, and upcoming updates and upgrades, please visit the Go2Group support site.

Frequently Asked Questions

Go2Group provides an updated list of frequently asked questions.

Additional Information

Technical Support

Go2Group provides technical support for its entire line of products.

Go2Group technical support is available by telephone, email, and a specific customer support ticket system for the Perforce Plugin for Jira:

By telephone: +1 877 442 4669
By email: support@Go2Group.com
By ticket: Jira.go2group.com
- The support site above is self-administered - feel free to create and manage your account. For additional support information, please review our Perforce Plugin for Jira support page.

Sales Support

Go2Group provides sales support for its entire line of products, including the Go2Group Perforce Plugin for Jira.

Go2Group sales support is available by telephone and email:

By telephone: +1 877 442 4669
By email: sales@Go2Group.com

Learn More

For more information on Go2Group, its products, and its services, please visit our website at www.Go2Group.com.

For more information on Jira, please visit the Atlassian website at www.Atlassian.com.