TestTrack Admin Training Guide 2010

TestTrack®

Seapine

Admin Training GuideVersion 2010

© 2009 Seapine Software, Inc. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form by any means without the written permission of Seapine Software, Inc.

Seapine Software, Inc.5412 Courseview Drive, Suite 200Mason, OH 45040513.754.1655

[email protected]

emailto:[email protected]

i

Contents

Course Preview: TestTrack Administrator .......................................................................1TestTrack administrative tasks................................................................................................................... 2TestTrack licenses......................................................................................................................................... 2TestTrack components ................................................................................................................................. 3

Module 1: How to Configure a New Project ...................................................................5

How to add global users in the Seapine License Server ..................................................................... 6How to add projects .................................................................................................................................13Practice: Configuring a Project ...............................................................................................................17

Module 2: How to Configure Project Options ...............................................................21

How to access project options.................................................................................................................22How to set general options .....................................................................................................................23How to set client options ..........................................................................................................................24How to set file attachments options .......................................................................................................27How to set email options..........................................................................................................................27How to set hyperlink options ...................................................................................................................28How to set defect options ........................................................................................................................28How to set import mail options ...............................................................................................................30How to set SoloBug options .....................................................................................................................30How to set SoloSubmit options................................................................................................................31How to set test case options ....................................................................................................................32How to set test run options.......................................................................................................................32How to set requirement options..............................................................................................................33How to set requirement documents options ..........................................................................................34How to set dictionary options .................................................................................................................34Practice: Project Options..........................................................................................................................36

Integrated Practice: Setting up and Configuring Projects ............................................. 41

ii

Module 3: How to Customize Fields .............................................................................47

How to decide whether to rename or create custom fields ..............................................................48How to rename fields ...............................................................................................................................49How to create a custom field..................................................................................................................51How to define field list values ................................................................................................................55How to configure field relationships......................................................................................................57How to set field relationship options .....................................................................................................59How to configure required fields and default values........................................................................61Practice: Customizing fields .....................................................................................................................66

Module 4: How to Add Users and Customers...............................................................77

Global and local users .............................................................................................................................78How to retrieve global users...................................................................................................................78How to add new users..............................................................................................................................79How to add customers ..............................................................................................................................90How to promote users and customers ....................................................................................................91Practice: Adding Users and Customers..................................................................................................93

Module 5: How to Add a Security Group......................................................................97

How to create a filter...............................................................................................................................98How to create a security group........................................................................................................... 102How to restrict viewable records for security groups ..................................................................... 103How to set command security............................................................................................................... 105How to set field security........................................................................................................................ 107Practice: Adding Security Groups....................................................................................................... 110

Integrated Practice: Adding Users and Security Groups............................................. 117

Module 6: How to Customize the Workflow ...............................................................127

How to analyze your workflow ........................................................................................................... 128How to add states.................................................................................................................................. 130How to add events................................................................................................................................. 132How to configure event fields .............................................................................................................. 143How to add transitions .......................................................................................................................... 148How to configure assignment rules...................................................................................................... 153How to evaluate and diagram the workflow ................................................................................... 157Practice: Customizing the Workflow................................................................................................... 162

iii

Module 7: How to Configure Automation Rules.........................................................167

How to configure email options........................................................................................................... 168How to configure hyperlink options .................................................................................................... 168How to configure defect send mail options....................................................................................... 168Deciding which type of automation rule to use ................................................................................ 169How to configure notification rules ..................................................................................................... 170How to customize email templates...................................................................................................... 175How to configure triggers..................................................................................................................... 178How to add trigger actions .................................................................................................................. 183How to configure escalation rules ....................................................................................................... 190Practice: Configuring Automation Rules ............................................................................................. 196

Integrated Practice: Customizing the Workflow ......................................................... 203

Module 8: How to Manage Data.................................................................................211

How to export data to an XML file .................................................................................................... 212How to import data from an XML file................................................................................................ 214How to export data to a text file....................................................................................................... 217How to import a text file ...................................................................................................................... 221How to perform bulk field changes .................................................................................................... 224How to duplicate records ..................................................................................................................... 225How to merge defects ........................................................................................................................... 229Practice: Importing and Exporting Data ............................................................................................ 232

Module 9: How to Create a Report..............................................................................237

TestTrack report types........................................................................................................................... 238How to create a detail report ............................................................................................................. 240How to create a list report ................................................................................................................... 243How to create a distribution report .................................................................................................... 247How to create a trend report .............................................................................................................. 252How to add an external report........................................................................................................... 256How to set report options ..................................................................................................................... 256Practice: Creating Reports.................................................................................................................... 259

Module 10: How to Manage the Audit Trail ...............................................................267

How to enable audit trail logging ...................................................................................................... 268How to search for and view audit trail records ............................................................................... 270How to validate records and generate audit reports .................................................................... 274

iv

Reference: Email Templates ........................................................................................277

Email acknowledgement........................................................................................................................ 277Defect assignment .................................................................................................................................. 278Defect changed ...................................................................................................................................... 279Defect added.......................................................................................................................................... 280Defects merged ...................................................................................................................................... 280Defects renumbered............................................................................................................................... 280Defect closed........................................................................................................................................... 281Test case assignment.............................................................................................................................. 281Test case changed.................................................................................................................................. 282Test case added ..................................................................................................................................... 282Test cases renumbered.......................................................................................................................... 283Test case closed ...................................................................................................................................... 283Test run assignment ................................................................................................................................ 284Test runs generated ............................................................................................................................... 284Test run changed .................................................................................................................................... 285Test run closed......................................................................................................................................... 285Requirement assignment........................................................................................................................ 286Requirement changed............................................................................................................................ 287Requirement added ............................................................................................................................... 288Requirement renumbered ..................................................................................................................... 288Requirement closed ................................................................................................................................ 289Requirement email review request...................................................................................................... 289Requirement tracked email received.................................................................................................. 290Requirement list....................................................................................................................................... 290Link changed............................................................................................................................................ 290Link made suspect................................................................................................................................... 290Requirement question or comment....................................................................................................... 291Requirement document assignment ..................................................................................................... 292Requirement document changed ......................................................................................................... 292Requirement document added............................................................................................................. 293Requirement documents renumbered.................................................................................................. 293Requirement document closed.............................................................................................................. 293Requirement document email review request ................................................................................... 294Requirement document tracked email received ............................................................................... 294Requirement document list .................................................................................................................... 294Requirement document question or comment .................................................................................... 295

Glossary......................................................................................................................297

1

Course Preview: TestTrack Administrator

This course is designed for project managers, system administrators, and advanced users who are responsible for setting up and managing the flow of defects, test cases, and test runs throughout an organization.

TestTrack Pro allows you to track defects and automate the process of resolving them, and TestTrack TCM allows you to track test cases and the associated runs. After completing this course, you will be able to create a new project with custom fields and a custom workflow. You will also be able to add users and configure security settings.

Before starting this course, you should have a working knowledge of the TestTrack interface, how to add a defect, and how to work with defects or test cases.

Note: This course focuses primarily on configuring a TestTrack Pro project to manage defects. The tasks required to configure a TestTrack TCM project are the same with some minor differences in individual steps.

TestTrack Administrator

2

TestTrack administrative tasks

The TestTrack administrative tasks can be divided into initial setup and ongoing activities.

Initial setup

Ongoing tasks

In this course, you will work with the setup activities from creating a project through defining the workflow. You will also learn how to create reports, export and import files, and work with the audit log.

TestTrack licenses

TestTrack RM tracks requirements, TestTrack TCM tracks test cases and runs, and TestTrack Pro tracks defects. Together the applications allow you to manage the testing and defect resolution process through a single interface. Each application is controlled by a separate license. If you are using more than one TestTrack application, you can control which users have access to items. For example, developers and QA analysts may need access to defects and test cases. As a result, you would assign both a TestTrack Pro and a TestTrack TCM license to those users. However, technical writers only need access to defects and only need a TestTrack Pro license.

Install the softwareConfigure the

Seapine License Server

Create a projectConfigure the TestTrack Server

Customize the fields

Define the workflow

Create security groups Add users Add customers

Configure source control

Configure automation rules

Create a report Export/import files View audit log

3


The workflow

The activities that a user can perform on an item are defined by the project workflow. For example, in the following workflow a user can assign, estimate, or fix an open defect. When a defect is fixed, it can move either to the Fixed state or to the Closed (Fixed) state.

TestTrack components

TestTrack includes the following components:

Seapine License Server — Stores all the licenses for Seapine applications including TestTrack Pro, TestTrack TCM, and Surround SCM.

Seapine License Server Admin Utility— Connects to the Seapine License Server via TCP/IP and allows you to manage licenses, global users, the server log, and server options.

TestTrack Server — Contains information about projects, the server log, server users, the mail queue, and server options.

TestTrack Server Admin Utility — Generally installed on the server computer and the server administrator’s computer. The Server Admin Utility is used to manage projects, the server log, server users, the mail queue, and server options.

TestTrack Server Admin Web Utility — Allows you to perform same functions as the TestTrack Server Admin Utility using a browser.

TestTrack Client — Allows users to access TestTrack Pro through a cross-platform client/server interface.

TestTrack Pro Web Client — Allows users to access TestTrack Pro using a browser.


4

5

Module 1: How to Configure a New Project

After completing this module, you will be able to:

Use the Seapine License Server Admin Utility

Use the TestTrack Server Admin Utility

Create users who can access multiple projects

Create a new project based on an existing project

Create a new project based on the TestTrack default settings

Activate existing TestTrack projects

The Seapine License Server Admin Utility and TestTrack Server Admin Utility are used to manage the available projects and how users interact with them.

How to Configure a New Project

6

How to add global users in the Seapine License Server

The Seapine License Server manages the licenses for all the copies of Seapine applications in your enterprise. Storing user data on the license server allows you to make a user available to multiple Seapine applications. As a result, the user can use the same username and password to access TestTrack and Surround SCM.

The Seapine License Server also supports LDAP, which allows you to define users once and share them across multiple computers and applications. If your company already uses an LDAP server, configuring the Seapine License Server to use LDAP will make user administration easier. User information, such as phone numbers and email addresses, is stored on the LDAP server and accessed by the license server. This ensures the Seapine License Server is always in sync with your company’s user directory.

Types of users

The Seapine License Server and TestTrack make a distinction between users and customers.

The Seapine License Server and TestTrack further classify users and customers by their ability to log in to a project.

Users are individuals within your organization.

Customers are individuals outside your organization or within your organization who are tracked separately in a TestTrack project.

Local users and customers are stored in a specific project and cannot log in. They are not assigned usernames or passwords.

Global users and customers are stored in the Seapine License Server and have usernames and passwords. If they are assigned a license, they can log in to one or more projects.

Stored in the license server

Stored in the project

Can log in Has a username

Global user X X X

Global customer X X X

Local user X

Local customer X

7


Use the definitions to complete the following exercise. Write local user, local customer, global user, or global customer.

Answers:

1 Global customer — John does not work for Acme. So he is a customer. He has to log in to the project. That makes him a global customer. He has to be assigned a license to log in.

2 Local user — Bill works for Acme so he is a user. SoloSubmit allows individuals to submit defects without logging in to the project. Therefore, Bill is a local user. His user profile exists in the project so the administrator can track the defects he submits.

3 Global user — June works for Acme and must log in. Just like John, she has to be assigned a license before she can log in to the project.

4 Local customer — Sally does not work for Acme so she is a customer. She does not log in so she is a local customer. Like Bill, her user profile is used solely for tracking purposes.

1 John does not work for Acme but needs to log in to the project and update defects.

2 Bill works for Acme and submits defects through the SoloSubmit Web page without logging in to the project.

3 June is a developer for Acme and regularly works with defects.

4 Sally works for one of Acme’s customers and uses SoloBug to submit defects.


8

Adding global users

Global users and customers are stored on the license server and can be added through the Seapine License Server Admin Utility or the TestTrack Client. Local users and customers are stored a specific project and are only added to that project using TestTrack.

Use the following steps to add a global user to the Seapine License Server.

1 If the license server is not running, choose Start > All Programs > Seapine Software > Seapine License Server > Seapine License Server.

2 Choose Start > All Programs > Seapine Software > Seapine License Server > Seapine License Server Admin.

3 Enter your username and password. The License Server Admin Utility opens.

4 Click Global Users. The Global Users dialog box opens.

Note: How to Add Users and Customers, page 77 in this participant guide covers adding users and customers in TestTrack.

Note: The Assign Licenses area displays buttons for all your installed Seapine products. A TestTrack Pro license gives users access to defects in a project, a TestTrack RM license gives users access to requirements and requirement documents, and a TestTrack TCM license gives users access to test cases and test runs. If you want a user to have access to all record types, assign that user all three TestTrack licenses.

9


5 Click Add. The Add User dialog box opens.

Try it

Start the License Server Admin Utility and add yourself as a user.

Make sure to enter a username.

Do NOT click OK.


10

Answer:

The following screenshot shows the completed dialog box for a user named Abby Adams.

Security options

The Security tab of the Add User dialog box controls the user’s access to the License Server Admin Utility, NOT their access to TestTrack projects. TestTrack security is defined within the project.

11


License options

The Licenses tab of the Add User dialog box allows you to assign licenses to the user. Global users and global customers must have licenses to log in to a project.

Use the following steps to add licenses to a user.

1 Click the Licenses tab on the Add User dialog box.

2 Click a product. The Assign License dialog box opens.

3 Click Use floating license to assign a floating license to the user or Use named license to assign a named license to the user.

4 Click OK.

Try it

You work in the QA department and need access to defects, test cases, and test runs.

Using your user information, configure your user profile to use floating licenses to access TestTrack Pro and TestTrack TCM.


12

Answer:

The following screenshot shows the correct settings for the Licenses tab.

Address information

The Address tab of the Add User dialog box allows you to specify the user address, company, division, and department. If you have a large number of users, setting the Company, Division, and Department fields can help you group users.

Use the following steps to add address information for a user.

1 Click the Address tab on the Add User dialog box.

2 Enter or select the user Company, Division, and Department information. If you enter a value, it is saved and can be selected for other users.

3 Enter the user Address.

13


4 Click OK.

How to add projects

After you create global users, you can begin creating projects. When you create a project, you must decide whether to use the native TestTrack database format or to use another database format. The TestTrack server can host projects from multiple physical databases.

If you want to use a database format other than the native format, you must set up an RDBMS connection prior to creating the project. For this module, you will create projects in the native database format.

Adding a project

Use the following steps to add a project.

1 Choose Start > All Programs > Seapine Software > TestTrack > TestTrack Server Admin.

2 Enter your Username and Password. The TestTrack Server Admin Utility opens.

3 Click Projects. The Projects dialog box opens.


14

Deciding which type of project to create

You can create a project based on the default TestTrack settings, create a project based on a previous project, or add an existing project.

Use the guidelines to complete the following. Specify whether you would click Create, Create from Template, or Add Existing.

Answers:

1 Add Existing — The Development project is an existing project that you want to make available on the new server.

2 Create from Template — There is no reason to create a new project from scratch if you have another project that matches the new one.

3 Create — Since you do not know the functionality you will need for the new project, it is best to create the new project based on the default TestTrack fields and workflow.

4 Create from Template — Even though you will have to make some changes, it is best to start with an existing project that has functions similar to the new one.

Guidelines:

If you want a blank project based on the default workflow, click Create.

If you want to copy filters, reports, security groups, and fields from an existing project, click Create from Template.

If you need to add an old project or add a new project moved to this server, click Add Existing.

1 You are consolidating TestTrack servers. You moved the Development project to the new centralized server and want to make it available to users.

2 You have a project named Beta that works exactly the way you want a new project to work.

3 You are creating a project to track defects for a new product. It will not use the same workflow or fields as other projects.

4 A project named Enhancements works the way you want a new project to work. However, the new project will need two additional fields and one new workflow state.

15


Defining the project

After you click Create, Create from Template, or Add Existing, the Create Project dialog box opens.

Try it

Create a new project for WysiCorp, a software company that makes office productivity software.

It is their first TestTrack project.

Name the project ‘WysiDevelopment.’

Note: The dialog box has a different title depending on the button you click. However, the options in the dialog box are the same.


16

Answer:

1 Choose Start > All Programs > Seapine Software > TestTrack > TestTrack Server Admin.

2 Enter your Username and Password.

3 Click Projects.

4 Click Create. The Create Project dialog box opens.

The following screenshot shows the proper settings.

5 Click OK.

17


Practice: Configuring a Project

Directions

In this practice, you will add new global users and create a new project.

Read the situation and use the following to complete this exercise:

Seapine License Server Admin Utility

TestTrack Server Admin Utility

When you are finished, compare your results with the Solution section.

You have five minutes to complete this practice. If you have problems during the practice, contact the instructor.

Situation

Acme Software is using TestTrack Pro to track their defects.

Add two new users to the Seapine License Server with your last name.

Assign TestTrack Pro floating licenses to the new users.

Then create a new empty project named ‘Acme Development.’

Note: Make sure the Seapine License Server and TestTrack Server are running before beginning this exercise.


18

Solution

Add global users:

1 Switch to the Seapine License Server Admin Utility.

2 Click Global Users. The Global Users dialog box opens.

3 Click Add. The Add User dialog box opens. The following screenshots show the settings for one of the new users.

4 Click OK.

19


5 Repeat Steps 3 and 4 until all the users are added.

Add project:

1 After adding the global users choose Start > All Programs > Seapine Software > TestTrack > TestTrack Server Admin. The TestTrack Server Admin Utility opens.



20

3 Click Create. The Create Project dialog box opens. The following screenshot shows the settings for the new project.

4 Click OK.

21

Module 2: How to Configure Project Options


Set general project options

Configure basic defect, test case, test run, requirement, and requirement document settings

Specify how the project imports email

Specify how the project handles SoloBug files

Specify how the project handles SoloSubmit defects

Set dictionary options and add words to the custom dictionary

Project options are used to control the overall behavior of a project and apply to all users. You can set all the options at the beginning of the project or adjust them as the project goes on. This module covers some of the project options. Other options are discussed with the program components they apply to.

How to Configure Project Options

22

How to access project options

After you create a project using the TestTrack Server Admin Utility, you can open the project in TestTrack and specify how it will function by using the project options. After opening the project, access the Project Options dialog box by choosing Tools > Administration > Project Options.

The options are grouped in categories. In this module, you will learn about the following categories:

General

Client Options

File Attachments

Email

Hyperlinks

Defects

Test Cases

Test Runs

Requirements

Requirement Documents

23


Dictionary

You will learn about the Compliance, Fields, and Reports project options in upcoming modules.

How to set general options

The general options allow you to enter project information, as well as choose login, workflow, and stamping options.

The login options allow you to choose whether or not to allow TestTrack Pro and TestTrack TCM users to log in to the project. The workflow options allow you to choose whether or not to display inactive states/events in reports, filters, or the interface and to generate automated systems comments. The stamping options allow you to choose whether or not users can insert stamps in multi-line text fields to indicate changes and to configure a stamp format.

Note: You must enter a Project name if you want to include it in notification emails and reports.


24

How to set client options

The client options allow you to control functionality when the project is accessed over the Web, define how multiple logins for floating licenses are handled, whether local users and customers appear in assignment filters, and limit the text displayed on the Overview tab.

25


TestTrack Pro Web options control how the TestTrack Pro Web client behaves (NOT SoloSubmit).

Multiple login options specify whether or not to allow users with floating licenses to login multiple times.

Miscellaneous options allow you to choose whether or not to show local users and customers in assignment filter restrictions.

Hide navigation buttons if no security access

If you select this option, Web users can only see the navigation buttons they have the security to use. Instead of the buttons simply being disabled, they will be hidden.

Replace graphics if field labels are renamed

The tabs and buttons in the Web client are graphics that contain text. If you change the name of a field that uses a graphic, the site will use a blank graphic with the new label superimposed over it in HTML text.

If this option is not selected and you change the name of a field label that uses a graphic, the default graphic will be used. For example, if you change Defects to Issues and do not select this option, the tab will still read ‘Defects.’ You will have create a custom graphic and configure the pages to use that graphic.

Disable spell checking If you select this option, Web users cannot use spell check.

Populate user and customer selection lists each time Web pages load

This option controls how Web user fields are populated. TestTrack Web performance may be slow if a project includes a large number of users and customers because all user and customer selection fields are populated each time a page loads. If you select ‘Do not populate user and customer fields’, users must click the Find button next to a field to select the users or customers to add.

Note: These can be overridden by a security group.


26

Overview tab options allow you to limit the number of characters in descriptions and tracked emails displayed on the Overview Tab.

Try it

Start TestTrack and open the WysiDevelopment project you created in the previous module.

Open the Project Options dialog box and change the following:

Answer:

The following screenshots show the correct settings.

Project name: WysiDevelopment

Description: Project tracks defects, test cases, and test runs for all WysiCorp’s products

TestTrack Web options: Hide navigation buttons in the Web client if the user does not have security access.

27


How to set file attachments options

Image file attachment options allow you to specify whether to create thumbnails for images attached to a defect and whether to display the thumbnail automatically when opening the defect.

The following screenshot shows a defect with images displayed as thumbnails.

If you do not select Automatically display thumbnails, users can right-click the attachment and choose Show Thumbnail to view it.

How to set email options

The email options allow you to enable email sending and tracking and set return address information for notifications.


28

How to set hyperlink options

The hyperlink options allow you to specify information so users can open items in TestTrack, such as defects, using hyperlinks.

The RSS Feeds options allow you to specify whether RSS feeds can be created for published filters.

How to set defect options

The defect options allow you to defer defect numbering, define next defect numbers, and select a link definition to use when creating a test case from a defect.

The defer defect numbering options control when defect numbers are assigned. If you want to review defects submitted by a specific method before TestTrack assigns a number, clear the corresponding option to defer numbering.

Note: You must have to Web client installed to use the hyperlinks.

29


The next number options control the next defect number that will be assigned and the next sequence number used.

The sequence number is stored in the defect Reference field.

You can configure the project so the Reference field is populated when defects are imported from SoloBug, SoloSubmit, or email. This sequence number can also be used in notification emails sent to the submitter and can act as a case number.

The Create Test Case from Defect option allows you to specify which link definitions are available when users create a test case from a defect.

Other defect options are grouped in subcategories. In this module, you will learn about the following defect subcategories:

Import Mail

SoloBug

SoloSubmit

You will learn about Send Mail and Reports options for defects in upcoming modules.

Note: Defect numbers can be re-used.


30

How to set import mail options

The import mail options allow you to control how the project handles defects submitted via email.

Import mail options include the settings for where defects are imported from and how often TestTrack checks for new files. In the second set of options, you can specify whether or not to send a reply to the submitter, which email template to use when replying, and whether or not the next sequence number is used.

The final set of options allow you to specify how long the client will wait for a connection response before timing out.

How to set SoloBug options

The SoloBug options allow you to specify where to look for SoloBug files and what to do after the files are imported.

See Reference: Email Templates, page 277 for the text of the different email templates.

31


How to set SoloSubmit options

The SoloSubmit options allow you to specify how the project handles defects submitted through SoloSubmit. SoloSubmit is a TestTrack add-on that allows users and customers to submit bug reports and feature requests to a TestTrack project using a Web browser.

The first three options allow you to specify the SoloSubmit page, whether to send an email notification to the submitter, and whether to include the reference number in the defect. In addition, you can set the following options.

Enforce required field validation

Select this option to make sure that all the required fields are entered.

Use default values Select this option if you want SoloSubmit to initially populate the SoloSubmit Web page with default values.

Field relationships JavaScript is used to handle field relationships on the SoloSubmit page. If you have hidden fields or have customized the SoloSubmit page select the field relationships you do NOT want to use JavaScript to manage.


32

How to set test case options

The test case options allow you to control the behavior of test cases in the project, including when to defer test case numbering, the next test case numbers, and the fields used to calculate the actual and fixed hours in reports.

The defer test case numbering options control when test case numbers are assigned. If you want to review test cases submitted by a specific method before TestTrack assigns a number, clear the corresponding option to defer numbering. The Next test case number option controls the next test case number that will be assigned when a new test case is added.

How to set test run options

The test run options allow you to specify the next test run number, control test run status reporting fields, and select a link definition to use when creating a defect from a test run.

The next test run number option controls the next test run number that will be assigned.

The create defect from test run option allows users to select a link definition to use when creating a defect from a test run.

See Module 9: Reports for more information about test run status reporting fields.

33


How to set requirement options

The requirement options allow you to defer requirement numbering, specify the next requirement number and the fields used to calculate the actual and fixed hours in reports.

The defer requirement numbering options control when requirement numbers are assigned. If you want to allow requirements submitted by a specific method to be reviewed before TestTrack assigns a number, clear the corresponding option to defer numbering. The next requirement number option controls the next requirement number that will be assigned when a new requirement is added.

The actual vs. fixed hours options are used with trend reports to calculate time tracking values and help you determine if your estimates are on target.

The create test case from requirement option allows users to select a link definition to use when creating a test case from a requirement. The prompt users before adding link option prompts users to create a link when generating a test case from a requirement. Clearing this option will assign the select link definition to all test cases.


34

How to set requirement documents options

The requirement documents options allow you to defer requirement document numbering until they have been reviewed and specify the fields used to calculate the actual and fixed hours in trend reports.

How to set dictionary options

The dictionary options control which dictionary to use and the words in the custom dictionary. TestTrack includes three dictionaries: American English, British English, and Canadian English. Additional dictionaries can be downloaded from http://www.seapine.com/ttpresources.php#spellcheck.

You can add words such as your company name or product names to the dictionary by clicking Add.

Note: Users can also add words to private dictionaries associated with their profiles.

35


Try it

Add the following words to the dictionary for the WysiCorp Development project.

WysiCorp

WysiCalc

WysiChart

Answer:

The following screenshot shows the words in the dictionary.


36

Practice: Project Options

Directions

In this practice, you will set the project options for the Acme Development project you created in the previous module.

Use the following to complete this exercise:

Acme Development project



Situation

Configure the project options using the following information.

Project name: Acme Development

Description: Project tracks requirements, test cases, test runs, and defects for all Acme products

Defer defect numbering: Only automatically number defects submitted by TestTrack users.

Defer test case numbering Do not automatically number test cases imported from a text or XML file.

Images: Create thumbnails for file attachments.

Automatically display thumbnails when opening a defect.

SoloBug: Look for SoloBug files every 30 minutes.

SoloSubmit: Enable SoloSubmit

37


Solution

1 Choose Tools > Administration > Project Options. The Project Options dialog box opens. The following screenshot shows the correct General settings.

2 Click the File Attachments category. The following screenshot shows the correct File Attachments settings.


38

3 Click the Defects category. The following screenshot shows the correct Defects settings.

4 Click the Test Cases category. The following screenshot shows the correct Test Cases settings.

5 Click the SoloBug category. The following screenshot shows the correct SoloBug settings.

39


6 Click the SoloSubmit category. The following screenshot shows the correct SoloSubmit settings.

7 Click OK.


40

41

Integrated Practice: Setting up and Configuring Projects

Directions

In this practice, you will create a project using the TestTrack Server Admin Utility and set the correct project settings based on the situation.

Read the situation and use the following to complete this exercise:

TestTrack Server Admin Utility

TestTrack Client


You have 10 minutes to complete this practice. If you have problems during the practice, contact the instructor.

Situation

WysiCorp developed a new spreadsheet application, WysiCalc. They need a project to track defects related to this product. Use the following requirements to set up the new project.

Project name: WysiCalc

Description: Project for all WysiCalc bugs (beta and production)

Images: Create thumbnails for file attachments

Defect numbering: Do not automatically number any defects

Custom dictionary entries: WysiCalc, WysiCorp

Setting up and Configuring Projects

42

Solution

1 Choose Start > All Programs > Seapine Software > TestTrack > TestTrack Server Admin. The TestTrack Server Admin Utility opens.


43


3 Click Create. The Create Project dialog box opens. The following screenshot shows the project settings.

4 Click OK.

5 Open the new project in TestTrack.

6 Choose Tools > Administration > Project Options. The Project Options dialog box opens. The following screenshot shows the General settings.


44

7 In the File Attachments category, select the Create thumbnails for image file attachments option.

8 In the Defects category, clear all the defect numbering options. The following screenshot shows the Defect settings.

45


9 Click the Dictionary category. The following screenshot shows the Dictionary settings.

10 Click OK.


46

47

Module 3: How to Customize Fields

After completing this module you will be able to:

Rename fields

Create custom fields

Specify choices for drop-down list

Configure required fields

Specify default fields values

Configure relationships between fields

Set field options for the project

This module will help you customize projects to fit your environment.

How to Customize Fields

48

How to decide whether to rename or create custom fields

Before you can decide if you need to customize fields, it is helpful to review how a defect, test case, or test run moves through the workflow. For example, the Add Defect Window contains a collection of fields that are organized on a series of tabs.

Depending on the status of the defect, users can perform different activities. These activities have corresponding dialog boxes and fields. The following screenshot shows the Estimate dialog box and its fields.

When you are customizing fields, you will notice that TestTrack groups the fields by the window or dialog box that contains them.

Use the TestTrack Fields Worksheets to review the default TestTrack fields and values to determine if you can rename an existing field or if you need to create a custom field.

49


How to rename fields

If you want to use an existing field but need to change the label to match your company’s terminology, use the following steps.

1 Choose Tools > Administration > Rename Field Labels. The Rename Field Labels dialog box opens.

2 Select the field you want to rename and click Edit. The Edit Field Label Value dialog box opens.

3 Enter the Field Label.

4 Click OK.

5 Repeat Steps 2 through 4 for each field label you want to rename.

6 Click OK in the Rename Field Labels dialog box.

Note: Field labels cannot be resized in the user interface and should not be longer than 32 characters. Field labels that do not fit in the allotted space are truncated.

The TestTrack Fields Worksheets show all the field labels with the corresponding window or dialog box.


50

Try it

TestTrack uses the Component field in the Add Defect window to specify different sets of functionality within a product.

WysiCorp does not use the term component.

They refer to components as functional areas.

Change the Component field label to ‘Functional Area.’

Answer:

1 Choose Tools > Administration > Rename Field Labels.

2 Select Component and click Edit.

3 Enter ‘Functional Area’ in the Field Label field.

4 Click OK.

51


5 Click OK in the Rename Field Labels dialog box. The following screenshot shows the renamed field in the Add Defect window.

How to create a custom field

If you determine that you need fields that do not exist in TestTrack, use the following steps to create a custom field.

1 Choose Tools > Administration > Custom Fields. The Setup Custom Fields dialog box opens.

2 Select a record Type.

3 Click Add. The Add Custom Field dialog box opens.

Field name The field name is displayed as the label in TestTrack.

Long label Long labels are displayed in drop-down lists and help users distinguish between the same fields in different events.


52

Try it

WysiCorp wants to store where the user was working when a defect occurred so they can eliminate environmental factors when troubleshooting.

In the WysiDevelopment project create a custom field using the following information.

Field code The field code automatically generates data and is used with email templates, reports, and SoloSubmit. Custom fields all begin with ‘%Z_’.

Location Location specifies whether the field appears in the main defect window or on a separate Custom Fields tab. This field only applies to defects.

Field type The field type specifies the type of data input: text field, date/time, check box, or pop-up menu. The Field Properties section changes based on the selected field type.

Single line Single line specifies the format and length of the text field entry.

Multi-line Multi-line defines how many rows of text are allowed in a text field.

Field name: Location

Long label: Location

Field code: LOCATION

Location: Main Defect Window

Field type: Pop-Up Menu

Pop-up menu options: Corporate office

Satellite office

On the road

53


Answer:

1 Choose Tools > Administration > Custom Fields.

2 Select Defects as the record Type.

3 Click Add. The following screenshot shows the settings for the Add Custom Field dialog box.

4 Click Setup Pop-up Menu Items. The Setup Custom Pop-up Menu dialog box opens.

5 Click Add. The Add Pop-up Menu Item dialog box opens.

6 Enter ‘Corporate office’ and click OK.

7 Repeat Steps 4 through 6 until all the locations are added.


54

8 Use the Top, Move Up, Move Down, and Bottom buttons to arrange the choices in ascending order.

9 Click OK in the Setup Custom Pop-up Menu dialog box.

10 Click OK in the Add Custom Field dialog box.

11 Click OK in the Setup Custom Fields dialog box.

The following screenshot shows the new field in the Add Defect window.

55


How to define field list values

TestTrack contains a variety of pop-up menus (drop-down lists). Use the following steps to change the values.

1 Choose Tools > Configure List Values.

2 Select the category you want to add the list value to. The Setup dialog box opens.

3 To add a new value click Add. To change an existing value, select the item you want to change and click Edit.

4 Enter a list value.

5 Click OK.

6 Organize the list of items in the order you want them to appear.

Note: The dialog box title changes based on the menu you are editing.


56

7 Click OK.

In the next sections, you will learn how to set the default values for pop-up menus and how to create field relationships.

Try it

Change the WysiCorp severity values to match the following.

Answer:

1 Choose Tools > Configure List Values > Severity Values.

2 Select Causes Crash and click Edit. The Edit Severity dialog box opens.

3 Enter ‘Critical.’

4 Click OK.

5 Repeat Steps 2 through 4 for No Workaround and Workaround.

The TestTrack Fields Worksheets include all the values for the standard TestTrack pop-up menus.

Default value New value

Causes Crash Critical

No Workaround Significant

Workaround Normal

Cosmetic Not needed — delete

57


6 Select Cosmetic and click Delete. The following screenshot shows the resulting severity values.

How to configure field relationships

You can set up relationships between fields. This allows you to control the choices available in one field based on the value selected in another field. For example, you can limit the choices available in the Component field based on what the user selects in the Product field. This allows you to control users’ choices and make sure the data collected is valid.

Use the following steps to configure field relationships.

1 Choose Tools > Administration > Field Relationships. The Field Relationship Selection dialog box opens.


3 Click Add. The Setup Parent-Child Relationship dialog box opens.


58

4 Select the Parent Field from the menu then select the Child Field and click OK. The Setup Field Relationships dialog box opens.

5 Select an item in the Parent list.

6 Enable or disable the available values in the Child field for the selected parent.

7 Repeat Steps 4 through 6 until all the relationships are configured.

8 Click OK when you finish setting up the field relationship.

9 Click OK in the Field Relationship Selection dialog box to save your changes.

Try it

WysiCorp wants all defects that result in loss of data to have a priority of critical or significant.

Set up a relationship between the Type and Severity fields using the following information.

Type Option Severity Options

Crash - Data Loss Critical

Significant

59


Answer:

1 Choose Tools > Administration > Field Relationships.


3 Click Add.

4 Select Type as the Parent Field

5 Enable Severity as the Child Field and click OK.

6 Select Crash - Data Loss in the Parent list.

7 Disable Normal in the Child list.

8 Click OK.

9 Click OK in the Field Relationship Selection dialog box to save your changes.

How to set field relationship options

There are also project options that control field relationships. Use these project options when you want to:

Control how invalid selected child field values are handled for defects

Control how invalid selected child field values are handled for test cases and test runs

Specify whether list values added to child fields are associated with all or none of the parent menu items

To prevent bad data from being entered into a project, these options should be set for any project that uses field relationships.


60

Use the following steps to set the field relationship options.

1 Choose Tools > Administration > Project Options. The Project Options dialog box opens.

2 Click the Relationships category.

Remove any invalid selected child field values on the Add Item page

Selecting this option removes the child field value if the user selects another parent value and the previously selected value in the child field is not valid (not in the child list) for the new parent value. These options apply to the behavior in the Add window for defects and test cases.

Remove any invalid selected child field values on the Edit Item page

Selecting this option removes the child field value if the user selects another parent value and the previously selected value in the child field is not valid (not in the child list) for the new parent value. These options apply to the behavior in the Edit window for defects, test cases, and test runs.

Associate new child fields

These options specify what happens when you add a list value to a child field. The new options can either be made available to all or none of the parent options. You can still control the relationships for the new options by using the Setup Field Relationships dialog box.

61


How to configure required fields and default values

After you add custom fields, rename fields, and specify values for pop-up menus, you can specify which fields are required and the default values for pop-up menus. Use the following steps to define the required fields and default values.

1 Choose Tools > Administration > Required Fields & Default Values. The Required Fields & Default Values dialog box opens.


3 Select a field group from the Fields list.

4 To set a required field, select the corresponding Is Required? check box.

5 To set a default value, select it from the Default Value list for the field.

6 Click OK.

Try it

WysiCorp needs to configure the following required fields and default values.

The Fields Worksheets show the dialog boxes for each of the field groups.

Field Category Required Default value

Disposition General No Open — Not Reviewed

Severity General Yes Normal

Reproduced Found by Yes <not set>


62

Answer:

1 Choose Tools > Administration > Required Fields & Default Values. The Required Fields & Default Values dialog box opens.


3 Select General Fields from the menu.

4 Select Is Required for the Severity field.

5 Select Normal from the drop-down list.

Repeat the steps for the other fields. The following screenshots show the correct settings for the fields.

6 Click OK.

Field default and required field options

There are also project options that control default and required fields behavior. Use these project options when you want to:

Specify that TestTrack use the server date for the default date fields

Control how field labels are displayed for required fields

63


Use the following steps to set the field options.


2 Click the Fields category.

The Default Date Options allow you to specify whether the date/time fields use the date/time on the local computer or the server date/time. The Version Fields options controls how the Version field behaves in the project.

Users can enter text in version fields

Select this option if you want to enter any value into the version field.

Users must select a pop-up menu value in version fields

If you select this option, users must select a version number from a drop-down list. The list of values must be created and then updated as new versions are made available. (Tools > Configure List Values > Version Values)

Use advanced logic when sorting on version fields

Select this option if you want TestTrack to look for delimiters in the Version field and sort using just the alphanumeric characters.


64

The Version field appears in several windows and dialog boxes including Add/Edit Defect, Estimate, Fix, Verify, and Release Notes.

3 Click Required.

The Required Fields Identification options allow you to specify how required fields are identified in both the TestTrack Client and TestTrack Pro Web.

Try it

Change the required fields for both TestTrack Pro Web and the TestTrack Client so the labels are bold, underlined, and blue.

Enforce required status even if field security prevents editing

Select this option to prevent users from saving records with empty required fields that they do not have permission to view or edit.

Only select this option if all required fields must be set when records are added or edited. For example, if the defect Priority field is required and can only be edited by users in the Administration security group, this option prevents users in other security groups from adding defects

65


Answer:


2 Click the Required category.

3 Select blue from the Color list for both clients.

4 Select Underline for both clients. The following screenshot shows the correct settings.

The following screenshot shows the changes in the Add Defect window.


66

Practice: Customizing fields

Directions

In this practice, you will customize the fields for the Acme Development project.





Situation

The Acme system administrator decides to make the following field changes.

1 Rename the Reference field to ‘Reference #.’

2 Create a new field on the Main Defect window that captures the department that found the defect. The following table shows the field settings.

3 The Product field should have the following values:

CheckMate Personal Finance

AcmeAccount Pro

Field name: Found by Department

Long label: Found by Department

Field code: FOUND_BY_DEPT

Location: Main Defect Window

Field type: Pop-Up Menu

Pop-up menu options: Development

QA

Documentation

Tech support

Marketing

67


4 The Component field should have the following values:

Reconcile

Account Manager

Payroll

Automated Payments

5 The Component field is a child of the Product field. The following table shows what Component options are available for the Product choices.

6 The Product field is required and has a default value of <not set>.

7 Required fields should be bold and red in the TestTrack Client.

Reconcile Account Manager

Payroll Automated Payments

<not set>

CheckMate Personal Finance X X X

AcmeAccount Pro X X X


68

Solution

Rename the field:

1 Select Tools > Administration > Rename Field Labels. The Rename Field Labels dialog box opens.

2 Select Reference and click Edit. The Edit Field Label Value dialog box opens. The following screenshot shows the required change.

3 Click OK in the Edit Field Label Value dialog box and the Rename Field Labels dialog box.

Add a new field:

1 Select Tools > Administration > Custom Fields. The Setup Custom Fields dialog box opens.


69


3 Click Add. The Add Custom field dialog box opens. The following screenshot shows the settings for the new field.

4 Click Setup Pop-up Menu Items. The Setup Custom Pop-up Menu dialog box opens.


6 Enter ‘Development’ and click OK.

7 Repeat Steps 4 through 6 until all the items are added. The following screenshot shows the correct menu items.

8 Click OK.


70

Add list values for the Product field:

1 Select Tools > Configure List Values > Product Values. The Setup Product Names dialog box opens.

2 Click Add. The Add Product dialog box opens.

3 Enter ‘CheckMate Personal Finance’ and click OK.

4 Repeat Steps 2 and 3 until all the products are added. The following screenshot shows the correct product names.

5 Click OK.

71


Add list values for the Component field:

1 Select Tools > Configure List Values > Component Values. The Setup Component Names dialog box opens.

2 Click Add. The Add Component dialog box opens.

3 Enter ‘Reconcile’ and click OK.

4 Repeat Steps 2 and 3 until all the components are added. The following screenshot shows the correct component names.

5 Click OK.


72

Configure field relationships:

1 Select Tools > Administration > Field Relationships. The Field Relationship Selection dialog box opens.


3 Select Add. The Setup Parent-Child Relationship dialog opens.

4 Select Product from the Parent Field list.

5 Select Component from the Child Field list. The following screenshot shows the correct settings.

6 Click OK in the Setup Parent-Child Relationship dialog. The Setup Field Relationships dialog box opens.

73


7 Disable all the child components when the product is not set.

8 Select Checkmate Personal Finance and enable the appropriate child components.

9 Select AcmeAccount Pro and enable the appropriate child components.

10 Click OK in the Setup Field Relationships dialog box and the Field Relationship Selection dialog box.


74

Configure the required fields and default values:

1 Select Tools > Administration > Required Fields & Default Values. The Required Fields & Default Values dialog box opens with General Fields selected.


3 Select the Is Required? check box for Product and leave the default value as <not set>.

4 Click OK.

75


Define the formatting for required fields:

1 Select Tools > Administration > Project Options. The Project Options dialog box opens.

2 Select the Required category.

3 Select red from the Color list for the TestTrack Client.

4 Click OK.


76

77

Module 4: How to Add Users and Customers


Retrieve global users and customers from the Seapine License Server

Add global users and customers using the TestTrack Client

Add local users and customers

Assign users and customers to security groups

Change local users and customers to global users and customers

TestTrack allows you to make distinctions between internal and external individuals (users and customers) and individuals who can work in the project (global) and those who are used for tracking purposes (local).

How to Add Users and Customers

78

Global and local users

You have learned that there are two types of users, global and local. Global users can log in to a project if they are assigned a license. You can add them in TestTrack or in the Seapine License Server. No matter where they are added, they are stored on the license server and are available to other Seapine projects.

Local users cannot log in to a project and are stored in the project where they were created. They are used mainly for tracking purposes. Local users, however, can be promoted to global users so they can access projects.

How to retrieve global users

Global users can be retrieved from the Seapine License Server and added to a project, which allows them to access to that project.

Use the following steps to retrieve global users.

1 Choose View > Users. The Users window opens.

2 Click Retrieve Global User. The Retrieve Global User dialog box opens.

3 Select one or more users.




Global user X X X

Local user X

79


4 Click Add. A progress indicator is displayed while the user is retrieved.

5 Select the user you just retrieved.

6 Click Edit.

7 Select a Security Group.

8 Click OK.

How to add new users

You have already learned how to add global users using the Seapine License Server Admin Utility. You can add both global and local users in TestTrack. Use the following steps to add new users.

1 Click Create > User. The Add User dialog box opens with the Info tab selected.

2 Enter the user’s first name, middle initial (optional), and last name.

3 If you want the user to be able to log in to the project, select Global. If the user will NOT log in or will only be used for tracking purposes, select Local.

4 If you selected Global, enter a Username.

5 If you selected Global, enter a password in the Password and Confirm Password fields.

Note: The user canNOT log in to the project unless you select a security group.


80

Try it

Retrieve your user information from the license server and add another global user to the Acme Development Project using the following information.

If Jean Barber already exists in the license server, retrieve her user information instead.

Answer:

1 Click Create > User.

2 Select Global.

3 Enter ‘Jean’ in the First Name field.

4 Enter ‘Barber’ in the Last Name field.

5 Enter ‘jbarber’ in the Username field.

6 Enter ‘[email protected]’ in the Email Address field.

First name Last name Username Security group Email Password

Jean Barber jbarber Customer Service [email protected] jbpassword

81


7 Enter ‘jbpassword’ in the Password and Confirm Password fields. The following screenshot shows the correct settings.

Notification rules

The Notify tab allows you to specify when the user should receive emails about defects, test cases, and test runs. For example, you can send notification emails when a record is assigned to a user or a record is added. You can use filters to further control notification rules. Click the Notify tab to configure the notification rules.


82

Use the following steps to create a notification rule.

1 Select the record Type of record the notification applies to.

2 Click Add. The Add Notification Rule dialog box opens.

3 Enter a Rule name.

4 If you want to use a filter to restrict the notification rule, select a Passes Filter.

5 Click the Trigger When tab.

6 Select the action that causes the notification to be sent.

83


7 Click the Actions tab.

8 Select a Template for the notification email.

9 If you do not want to send an email if the user made the change, select Do not send email if this user made the change.

10 If you want to send an email only when the defect is assigned to the user, select Only send email if item is assigned to this user.

11 Click OK.

Try it

Jean Barber is the product manager for the CheckMate Personal Finance product. She wants to be notified every time a new defect for the product is created.

Set up a notification rule for new defects using the CheckMate Defects filter.

See Reference:Email Templates, page 277 for the text of the different email templates.


84

Answer:

1 Click the Notify tab.

2 Select Defect from the Type list.

3 Click Add.

4 Enter ‘New CheckMate Defects’ as the Rule name.

5 Select CheckMate Defects from the Passes filter list. The following screenshot shows the correct settings.


7 Select Defect is created. The following screenshot shows the correct settings.


85


9 Select Defect Added from the Template list. The following screenshot shows the correct settings.

10 Click OK. The following screenshot shows the completed dialog box.


86

License options

If you want a global user to be able to log in to the project, you must assign the user a license. Click the License tab to access the license options.

You can select a floating license, a named license, or no license. TestTrack displays how many licenses of each type are available.

Address information

The Address tab allows you to specify the user address, company, division, and department. If you have a large number of users, setting the Company, Division, and Department fields can help you group users.

87


Notes

The Notes tab provides a place to store additional information about the user.

CPU and peripheral settings

The CPU and Peripherals tabs provide a place to store the user’s computer configuration. This allows you to capture the computer configuration without requiring users to enter it for every defect they create.

If the computer that you are using to configure the user has the same configuration as the user’s, you can click Capture Config to populate the settings.


88

Display settings options

You can specify the columns users see in the different list widows by default and whether defects, test cases, and test runs are filtered. Click the Display Settings tab to access the display options.

Statistics

The read-only Statistics tab stores data about the user’s activity in the project.

Try it

Finish adding Jean Barber by assigning a floating license, assigning her to the Administration security group, and entering the following CPU information.

Operating system: Windows XP

OS version: 5.1

CPU type: Pentium

89


Answer:

1 On the Info tab, select Administration from the Security Group list.

2 Click License.

3 Click Floating. The following screenshot shows the correct settings.

4 Click CPU.

5 Enter ‘Windows XP’ in the Operating System field.

6 Enter ‘5.1’ in the OS Version field.

7 Enter ‘Pentium’ in the CPU Type field. The following screenshot shows the correct settings.


90

How to add customers

You can configure customers as global customers so they can log in to the project or as local customers so they are only used for tracking purposes. To view customers choose View > Customers.

Notice that you can also retrieve global customers from the Seapine License Server just like you can retrieve global users.

Click Add to create a new customer.




Global customer X X X

Local customer X

Note: The user canNOT log in to the project or receive notification emails unless you select a security group.

91


The User Type option defaults to Local in the Add Customer window. The Add Customer window has the same tabs as the Add User window with the addition of the History tab. The History tab displays more detailed information about the defects found by the customer. Since customers are outside your organization, you may want to keep track of the number of defects they submit.

Try it

Add a local customer with your last name.

How to promote users and customers

Remember that local users and customers cannot log in to the project and are not shared between projects. You can promote local users or customers so they become a global users or customers. Once promoted, they will be stored on the Seapine License Server. You will be then be able to assign them a username and a license to allow them to log in to projects.

1 To promote a user choose View > Users.

2 Select the user you want to promote.

3 Click Promote. The Promote to Global User dialog box opens.

4 Enter a Username.

5 Click OK.


92

6 Edit the user and specify a license and a security group.

Try it

Promote the customer with your last name.

Note: The steps for promoting a customer are the same. Choose View > Customers instead of View > Users.

93


Practice: Adding Users and Customers

Directions

In this practice, you will add users to the Acme Development project.

You will use the Acme Development project to complete this exercise.



Situation

Acme has hired two new developers.

Add the users and assign them to the Developers security group.

Summit Accounting, one of Acme’s customers, added one new customer who will be tracked in the project but cannot log in.

Add these customers as well.

Users

Customers

First name Last name Security group Password License

Sean (your last name) Developers Floating

Emma (your last name) Developers Floating

First name Last name Company Division Department

Ann (your last name) Summit Accounting Corporate Human Resources


94

Solution

Add users:

1 Choose Create > User. The Add User dialog box opens.

2 Click the Info tab. The following screenshot shows the completed dialog box for Sean Erikson.

95


3 Click the License tab. Click the TestTrack Pro and TestTrack TCM buttons and select Floating.

4 Click Add.

5 Repeat Steps 2 through 4 until all the users are added.

Add customers:

1 Choose Create > Customer. The Add Customer dialog box opens.


96

2 Click the Info tab. The following shows the completed dialog box for Ann Brown.

3 Click the Address tab and enter the Company, Division, and Department. The following screenshot shows the completed dialog box.

4 Click Add.

97

Module 5: How to Add a Security Group


Create a filter

Create a security group

Assign a filter to a security group

Control access to commands

Define field level security

Security groups allow you to create a set of access rights and assign them to a group of users.

How to Add a Security Group

98

How to create a filter

You can use a filter to control the records that users in a security group can access. It is helpful to create the filter before you create the security group, though you can add the filter at any time. Use the following steps to create a defect filter.

1 Choose Create > Filter > Defect. The Add Defect Filter dialog box opens.

2 Enter a Name and Description.

3 Select a Share option.

Tip: Filters can be used in the Defects, Test Cases, or Test Runs list windows and in other areas of TestTrack. If you have a large number of filters, it can be helpful to use an abbreviation at the beginning of the filter names to group filters by how they are used. For example, the filter “SG Checkmate Defects” is used in a security group. The following is a list of suggested abbreviations:

SG — Security group

RP — Report

NT — Notification

TR — Trigger

ES — Escalation

99


4 Click Add to add a filter restriction. The Add Restriction dialog box opens.

5 Select the field you want to include in the filter from the Restrict by list.

6 Select Prompt for restriction information at run time to be prompted to enter restriction information when the filter is applied. If this option is selected, the Interactive Filter Wizard opens when the filter is selected on a list window, when generating a report that uses the filter, when applying a user-defined view that uses the filter, or when applying the filter to select items to add to a link.

7 Select the restriction options. The restrictions you can set change based on the Restrict by field.

8 Click OK to save the restriction.

9 Repeat Steps 4 through 8 until you have added all the required restrictions.

10 Select NOT/AND/OR operators and parentheses to build the Boolean logic for the filter if you have more than one restriction.

11 Click Validate to check the syntax of your filter.

12 Click Add.

Note: DO NOT select this option if you plan to use the filter in security groups, automation rules, or user notification rules. The filter cannot be used in these areas if this option is selected.


100

Try it

Acme has two dedicated support groups, one for CheckMate and another for AcmeAccount Pro.

They want to set up security so that tech support associates can only work with defects that affect the products they support.

They need two filters to be able to achieve this.

Create one filter named ‘SG CheckMate Defects’ that finds defects where the Product is CheckMate Personal Finance.

Name the second filter ‘SG AcmeAccount Pro’ and configure it to find defects where the Product is AcmeAccount Pro.

Both filters should be available to everyone.

Answer:

1 Choose Create > Filter > Defects.

2 Enter ‘SG CheckMate Defects’ as the Name and Description.

3 Select Shared With Everyone.

4 Click Add to add a filter restriction. The Restriction dialog box opens.

5 Select Product.

6 Select CheckMate Personal Finance. The following screenshot shows the restriction settings.

7 Click OK to save the restriction.

101


8 Click Validate. The following screenshot shows the completed CheckMate filter.

9 Click Add.

10 Repeat Steps 1 through 9 to add the AcmeAccount Pro filter. The following screenshots show the settings for the restriction and the filter.


102

How to create a security group

TestTrack allows you to control user activities at the defect, command, and field level. These settings are combined into a security group. You then assign users to the security group to apply the security settings. Before creating a security group, consider the following:

Should users in the group be limited to seeing a certain type of record?

What activities can users in the group perform and what menu options can they access?

What level of access should users in the group have to fields when adding new items?

What level of access should users in the group have to fields when editing existing items?

Use the following steps to create a new security group.

1 Choose Create > Security Group. The Add Security Group dialog box opens with the Users in Group category selected.

The Add Security Group dialog box includes Users in Group, Command Security, Field Security, and Notes categories.

In the Users in Group category, you can add users to the group. You can also specify if these users are included in pop-up menus (e.g., Closed by, Assign to, etc.).

2 Select Display users, Display inactive, Display customers, or Display local to control which users are visible in the Available Users list.

3 Select Include users in pop-up menus or Include customers in pop-up menus to display the selected users or customers in pop-up menus.

4 Click Find User to search for users and customers to add to the group. You will learn about adding users to security groups in an upcoming module.

5 Click Add.

103


How to restrict viewable records for security groups

Use the item subcategories of the Command Security category to restrict the type of records that users access.

You can select a filter and restrict users so they can only view or edit records they report.

Try it

Create a security group in the Acme Development project named ‘CheckMate Tech Support.’

Use the SG CheckMate Defects filter to restrict the defects the security group can access.

Note: You can duplicate an existing a security group by selecting it in the Security Group list window and choosing Edit > Duplicate Security Group.


104

Answer:

1 Choose Create > Security Group.

2 Select the Defects subcategory in the Command Security category.

3 Select the SG CheckMate Defects filter. The following screenshot shows the correct settings.

105


How to set command security

Use the Command Security category of the Add Security Group dialog box to control the menu options that users can access and the functions they can perform.

Commands are grouped by menu or functional area. Clear the check box to disable access to the command. All commands are selected (enabled) by default.

Try it

Using the CheckMate Tech Support security group, disable all the User and Administration commands.

In the Defects subcategory, disable access to assign defect numbers and renumber defects.


106

Answer:

1 Select the Users subcategory in the Command Security category.

2 Click Disable All.

3 Select Administration.

4 Click Disable All.

5 Select the Defects subcategory in the Command Security category.

107


6 Disable the Assign Defect Numbers and Renumber Defects options.

How to set field security

Use the Field Security category of the Add Security Group dialog box to specify the level of access that users in the security group have to defect, test case, and test run fields.

You can specify one of three levels of security for each field:

Read/Write

Read Only

Hidden


108

You can also define different behavior based on whether the users are adding a record or editing an existing one.

Try it

The Reference field is automatically generated by the system and users should not be able to change it.

Change the settings so the Reference field is read only when a defect is added or an existing defect is edited.

Note: You can create a report that shows the enabled/disabled commands for a security group.

109


Answer:

1 Select the Defects subcategory in the Field Security category.

2 Select Reference from the Add Privileges list.

3 Click Read Only.

4 Select Reference from the Edit Privileges list.

5 Click Read Only. The following screenshot shows the correct settings.

6 Click Add.


110

Practice: Adding Security Groups

Directions

In this practice, you will add a security group to the Acme Development project.

Use the Acme Development project to complete this exercise:



Situation

Acme Software needs a security group for their developers that will allow them to perform most of the same activities as an administrator but without the ability to add users, customers, or security groups.

Create a new security group named ‘Developers’ and make the following changes to the default settings.

If a category is not listed, no changes are required.

Command security

Administration: Can set up the Version field

Show logged in users

Can log out other users

Can import and export text and XML files

Can create release notes

Defects: CanNOT renumber defects

CanNOT edit other’s historical actions

Customers: CanNOT perform any customer activities

Users: CanNOT perform any user activities

Security groups: CanNOT perform any security group activities

Filters: CanNOT edit shared filters

CanNOT delete shared filters

111


Solution

1 Choose Create > Security Group. The Add Security Group dialog box opens. The following screenshot shows the basic settings.


112

2 Select Administration and clear the appropriate check boxes. The following screenshot shows the correct settings.

113


3 Select the Defects subcategory in the Command Security category and clear the appropriate check boxes. The following screenshot shows the correct settings.

4 Select Customers and click Disable All. The following screenshot shows the correct settings.


114

5 Select Users and click Disable All. The following screenshot shows the correct settings.

6 Select Security Groups and click Disable All. The following screenshot shows the correct settings.

115


7 Select Filters and clear the appropriate check boxes. The following screenshot shows the correct settings.

8 Click Add.


116

117

Integrated Practice: Adding Users and Security Groups

Directions

Add new users and security groups based on the requirements of the project.


WysiCalc project



Situation

The new WysiCalc project has several levels of security.

Developers can perform more functions than basic users. Create a security group that limits what basic users can do.

Then create user accounts for the following employees and assign the users to the security group.

Security Group

Name: Basic Users

Description: Can add, edit, and delete comments on a defect

Defect security: Users can only work with defects they reported

Command security

General: CanNOT log in via the Web, DLL, or SOAP interface

Administration: CanNOT perform any administrative functions

Defects: CanNOT assign defect numbers or renumber defects

CanNOT delete defects

CanNOT merge defects

CanNOT edit or delete anyone’s historical actions

CanNOT perform SCC actions

CanNOT perform bulk defect changes

CanNOT override the workflow

Adding Users and Security Groups

118

Users

Defect events: Can add, remove, and view attachments

Can add comments

Defect links: CanNOT perform any linking activities

Customers: CanNOT perform any customer activities

Users: CanNOT perform any user activities

Security groups: CanNOT perform any security group activities

Test configurations: CanNOT perform any test configuration activities

Filters: CanNOT delete shared filters

Reports: CanNOT perform any report activities

Workbook: Can perform ALL workbook activities

Field security Accept the default settings

First name Last name License

Jane (your last name) Floating

Bob (your last name) Floating

119


Solution

1 Choose Create > Security Group. The Add Security Group dialog box opens.

2 Select the General category and clear the Web, DLL, and SOAP interface options. The following screenshot shows the settings for the General commands.

3 Select the Administration category and click Disable All. The following screenshot shows the settings for the Administration commands.


120

4 Select the Defects category and clear the appropriate options. The following screenshot shows the settings for the Defects commands.

5 Select the Events category under Defects and clear the appropriate options. The following screenshot shows the settings for the Defect Events commands.

121


6 Select the Links category and click Disable All. The following screenshot shows the settings for the Defect Links commands.

7 Select the Customers category and click Disable All. The following screenshot shows the settings for the Customers commands.


122

8 Select the Users category and click Disable All. The following screenshot shows the settings for the Users commands.

9 Select the Security Groups category and click Disable All. The following screenshot shows the settings for the Security Groups commands.

123


10 Select the Test Configurations category and click Disable All. The following screenshot shows the settings for the Test Configurations commands.

11 Select the Filters category and clear the Delete Shared Filters option. The following screenshot shows the settings for the Filters commands.


124

12 Select the Reports category and click Disable All. The following screenshot shows the settings for the Reports commands.

13 Select the Workbook category and click Enable All. The following screenshot shows the settings for Workbook commands.

125


14 After clicking OK in the Add Security Group dialog box choose Create > User. The Add User dialog box opens. The following screenshot shows the user settings for Jane Adams.


126

127

Module 6: How to Customize the Workflow

After you complete this module, you will be able to:

Analyze your workflow

Identify states, events, and transitions

Add states and events

Configure event fields

Configure the basic assignment rules for states in the workflow.

This is the first of two modules dealing with the workflow. The workflow controls what can happen at each step of your tracking process. You can also automate activities at different points in the workflow. In this module, you will learn how to set up the workflow. In the next module, you will learn how to automate activities.

Customizing the workflow can be divided into the following tasks:

Identify states, events, and transitions

Add states

Add events

Specify events available in each state

Configure state changes for each event

How to Customize the Workflow

128

How to analyze your workflow

Before configuring the workflow in TestTrack, it is helpful to analyze your process. Diagram the process or make a list of the states that a record could move through.

Identifying states

Think of states as stops along the way in the process. When a record is in a specific state, users can perform certain activities. An activity might move the record to another state or it may just add information to the record. The state is displayed in the Status field.

For example, a defect starts in an Open state. When the defect fixed, it moves to the Fixed state and then to the Closed (Verified) state after a tester verifies the fix.

129


Identifying events and transitions

After you identify the states that records can go through, you need to decide what activities users can perform at each state and whether those activities cause a record to move to another state. It can be helpful to create a chart for your process. The following example shows state and activities used for defect tracking.

State Available activities State change

Open Assign for review -

Send to Development Development

Force Close Closed (Forced Closed)

Development Re-assign -

Send to QA QA


QA Verify Failed Development

Re-Assign -


Close Fixed Closed (Fixed)

Closed (Forced Closed) - -

Closed (Fixed) - -

<All States> Comment -


130

How to add states

After you identify the states, events, and transitions, you are ready to begin customizing the workflow. The first step is to add states or customize the existing states.

Use the following steps to add a state.

1 Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens with the States tab selected.

2 Select a record Type. The states for the selected record type are displayed.

3 Click Add. The Add State dialog box opens.

4 Enter a State Name and Description.

5 Select an Attribute. Records can either be open or closed.

6 Click OK.

Note: If the project contains any records, you can reset the workflow. When the workflow is reset all states, events, and transitions (except for the default state) are removed.

131


Try it

WysiCorp wants to track issues through the following states.

Open

Development

QA

Closed (Forced Closed)

Closed (Fixed)

Reset the workflow and add the new states.

Answer:

1 Choose Tools > Administration > Workflow.

2 Click Reset.

3 Click Yes.

4 Click Add.

5 Enter ‘Development’ in the State Name field.

6 Enter a Description.

7 Select Open from the Attribute list. The following screenshot shows the correct settings for the Add State dialog box.


132

8 Click OK.

9 Repeat the Steps 4 through 8 for the QA, Closed (Forced Closed), and Closed (Fixed) states. Be sure the Attribute for the last two states is Closed. The following screenshot shows complete list of states.

How to add events

After you create or edit states, you can add or edit the events. If you created a workflow chart, you can quickly identify all the events you need.

Use the following steps to add an event.

1 Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens with the States tab selected.

2 Select a record Type. The events for the selected record type are displayed.

133


3 Click the Events tab.

4 Click Add. The Add Event dialog box opens.

Note: If you reset the workflow, the events list will be empty.


134

5 Enter a Name and Description.

Remember that events in the Workflow dialog box translate to activities for users.

Informational events

An informational event is an activity that is available to users regardless of what state the record is in. Informational events, such as comments, do not cause the state of a record to change.

Notice that if you select the Informational Event check box the Resulting State and Assignments sections are disabled.

Tip: It can help users if event names are verbs. It also can make the workflow diagram clearer. It can also be helpful to use the same name for the event and the state.

135


Resulting state

If the event or activity causes the record to change states, use the Resulting State section to define the states the record can move to after the event. Click the drop-down list and select the resulting states.

The following screenshot shows the settings for the Fixed event. Notice that the Fixed event moves a record to either the Fixed or Closed (Fixed) state.

Note: States can be used to define distribution and trend reports. Determining how and when you want to track a defect can help you define the states you need.


136

Try it

Acme needs nine different events. They are highlighted below.

Add the events. Be sure to select the correct resulting states.

The Assign for Review and Re-assign events have a resulting state of <not set>.

The Comment event is an informational event.


Open Assign for Review -




Send to QA QA



Re-Assign -




Closed (Fixed) - -


137


Answer:

Adding the Assign for Review event:


2 Click Add.

3 Enter ‘Assign for Review’ in the Name field.

4 Enter ‘Assigns open issue to a user for review’ in the Description field.

5 Select <No State Change> from the Resulting State drop-down list. The following screenshot shows the correct settings.

6 Click OK.

Adding the Send to Development event:

1 Click Add.

2 Enter ‘Send to Development’ in the Name field.

3 Enter ‘Assigns open issue to Development’ in the Description field.

4 Select Development from the Resulting State drop-down list. The following screenshot shows the correct settings.

5 Click OK.


138

The following screenshots show the settings for the other events and the final events list.

139



140

Assignments

Assignments specify how the event affects the current assignment for the record.

Event results in a new assignment

Adds an Assign To field to the dialog box for the event.

Allow multiple user assignments

Allows more than one user to be selected in the Assign To field.

Event does not affect the current assignment

The event will not change the current assignment. The dialog for this event type will not contain an Assign To field.

Event clears the current assignment

Removes the current assignment and makes the record unassigned.

141


Try it

WysiCorp’s events have the following assignment settings.

Time tracking

If you want to capture the time spent performing an event, select the Display the time tracking field using option. Then select whether you want the total hours for all of these event types or just the hours for the last event of this type to be tracked.

Event Assignment

Assign for Review Event results in a new assignment

Allow multiple user assignments

Send to Development Event results in a new assignment

Force Close Event clears the current assignment

Re-assign Event results in a new assignment

Send to QA Event results in a new assignment

Verify Failed Event results in a new assignment

Close Fixed Event clears the current assignment

Comment -


142

Other options

The remaining options allow you to control if files can be attached to an event, if an event’s notes are included in the release notes (defects only), if electronic signatures are required to perform an event, if a dialog box displays when a user enters an event, or if the option to mark dependent items as suspect is available. Finally, you can specify if an event should be available to all existing security groups.

143


The Electronic Signature project options control whether electronic signatures are required on all actions or if they can be set on an event-by-event basis.

How to configure event fields

When you create an event, TestTrack creates a corresponding dialog box with basic fields that users complete when performing the event.

Editing fields

The fields that TestTrack creates depends on the selection on the Details tab and are listed on the Fields tab. For example, if you configured the event to result in a state change, the Resulting State field is displayed on the Fields tab and the corresponding dialog box. The following screenshots show the fields for the Fix event and the Fix dialog box.

Use the following steps to change an existing field.


144

1 Select the field and click Edit. The Edit Event Field dialog box opens.

2 Make any changes to the Name, Long Label, and Field Code.

Long labels are displayed in drop-down lists and help users distinguish between the same fields in different events. The field code automatically generates data and is used with email templates, reports, and SoloSubmit.

3 Click OK.

Adding custom fields

You can create custom fields for events.

Custom fields are displayed on the Custom Fields tab of the activity dialog boxes.

Use the following steps to create a new custom field.

1 Click the Custom tab.

Note: You can create distribution and trend reports based on custom activity fields.

145


2 Click Custom Fields. The Setup Custom Fields dialog box opens.

3 Click Add. The Add Custom Field dialog box opens.

4 Enter a Field name.

5 Enter a Field label.

6 Enter a Field code.

7 Select a Field type.

8 Enter the Field Properties.

9 Click OK.

These steps are the same as creating other custom fields for the project. See “How to Customize Fields” on page 47.

Try it

Create a custom field for the Force Close event that captures the reason for closing the record.

Use the following information to configure the field.

Field name: Force Close Reason

Long label: Force Close Reason

Field code: FORCE_CLOSE_REASON

Field type: Pop-up menu

Pop-up menu options:

Not our issue

Duplicate


146

Answer:

1 Click Custom Fields.

2 Click Add.

3 Enter ‘Close Reason’ as the Field name.

4 Enter ‘Close Reason’ as the Long label.

5 Enter ‘CLOSE_REASON’ as the Field code.

6 Select Pop-Up Menu as the Field type. The following screenshot shows the basic settings for the new field.

7 Click Setup Pop-up Menu Items. The Setup Pop-up Menu dialog box opens.


147


9 Enter ‘Not our issue’.

10 Click OK.

11 Repeat Steps 8 through 10. The following screenshot shows the correct settings in the Setup Custom Pop-up Menu dialog box.

12 Click OK.

13 Click OK in the Add Custom Field dialog box.

14 Click OK in the Setup Custom Fields dialog box.

Adding event icons

In addition to creating custom fields for the event, you can add an icon to the events toolbar. The events toolbar is displayed on the corresponding list window and the Add and Edit windows. The following example shows the events toolbar for the defect tracking workflow.

Use the following steps to add an icon.

1 On the Custom tab of the Add Event dialog box, select Add a custom icon to the TestTrack Client events toolbar to add a custom event icon to the TestTrack events toolbar.

2 Click Choose Icon to select an icon. The Open dialog box opens.

Note: Icons are stored in the following directory:

C:\Program Files\Seapine\TestTrack\workflowicons

You can use standard icons or create custom icons. If you create custom icons, they should be 32 x 32 pixels to allow for proper scaling in the application.


148

3 Locate the icon file and click Open.

How to add transitions

After you create states and events, you are ready to define which events are available in each state. Review the following example that you saw earlier in this module. When adding transitions, you are working with the State and Activities columns of the table.






Send to QA QA



Re-Assign -




Closed (Fixed) - -


149


You created the states and events (activities) for your records. You also specified the state changes for the events. Now, you will assign events to the different states using the Transitions tab. The Transitions tab is divided into three sections: Initial State, State Transitions, and Event Resulting States. The Initial State section allows you to select the beginning state of a new record from all the active states.


150

State transitions

State transitions specify the events that are available in each state. To make changes to the available events, click Edit in the State Transitions area.

The Edit State Transitions dialog box opens.

The states are listed along the side and the events are listed at the top of the columns. To make an event available for a state, select the check box that corresponds to that event.

151


Try it

Open the Configure Workflow dialog box and use the first and second column of the following table to make events available in the appropriate states.






Send to QA QA



Re-Assign -




Closed (Fixed) - -


Note: The Comment event will not appear in the Edit State Transitions dialog box.


152

Answer:


2 Click Transitions.

3 Click Edit in the State Transitions section. The following screenshot shows the correct state transition settings.

4 Click OK.

Event resulting states

Event resulting states allow you to review all the events in the workflow and specify whether a record’s state can change as the result of an event. To change the resulting states for the different events, click Edit in the Event Resulting States section.

153


The Edit Event Resulting States dialog box opens.

The events are listed along the side and the states are listed at the top of the columns. To make a state available for an event, select the check box that corresponds to that event.

If you specified the resulting state in the Add Event dialog box, you probably will not need to use the Event Resulting States dialog box.

How to configure assignment rules

In addition to creating states and events, you can also configure how a record in a specific state behaves when it is assigned to a user. By default, any user with the proper security can add an event in any of the states.

Use the following steps to configure a state so that only a user assigned to a record in that state can add an event.




154

3 Click the Assignment Rules tab.

4 Select the state you want to change and click Edit. The Edit Assignment Rules dialog box opens.

Only allow assigned users to enter an event when the record is in the selected state

Only allow users assigned to the record to add events.

Use state entered by first user to respond The resulting state of the event is determined by the first assignee to change the state.

155


Try it

WysiCorp wants to control activity on re-opened records.

In the WysiDevelopment project, configure the Open (Re-opened) state in the defect tracking workflow so that only assigned users can enter an event.

Change the options so that TestTrack waits for all the assigned users to respond.

Wait for all assigned users to respond then use the state with the highest priority

TestTrack will wait for all assigned users to enter and event AND then select the state with the highest priority.

Use the state with the highest priority and proceed as soon as an event with the highest priority is entered

TestTrack will wait until an assignee enters an event that moves the record to the state with the HIGHEST priority. It will NOT wait for other assignees to respond.

Resulting State Priorities Specify the priority of the available states.


156

Answer:


2 Click the Assignment Rules tab.

3 Select Open (Re-Opened) and click Edit.

4 Select Only allowed assigned users to enter an event when the defect is in the selected state.

5 Select Wait for all assigned users to respond then use the state with the highest priority. The following screenshot shows the correct settings.

157


How to evaluate and diagram the workflow

After you define states, events, and transitions, you can evaluate the workflow to check for orphaned states or conflicts.

Evaluating the workflow

Use the following steps to evaluate the workflow.

1 In the Configure Workflow dialog box, click Evaluate Workflow. The Potential Issues With Configured Workflow dialog box opens.

2 Review the issues.

3 Click Save As to save the details of the errors.

4 Click OK to return to the Configure Workflow dialog box and fix the errors.

Diagramming the workflow

You can also diagram the workflow to view a visual representation of it. Use the following steps to evaluate and diagram the workflow.

1 In the Configure Workflow dialog box, click Diagram Workflow. The Diagram Workflow dialog box opens.

2 Select the states you want to include.


158

3 Click OK. The diagram opens.

Arrows that point back to the same box do not cause a state change. Informational events are not displayed on the diagram. Green boxes with double borders indicate the beginning of the process. Red boxes with double borders are endpoints in the process.

Try it

Diagram the workflow for WysiCorp. Select all the available states.

159


Answer:

1 Select Diagram Workflow. The Diagram Workflow dialog box opens.

2 Click Select All. The following screenshot shows the WysiCorp workflow.

Troubleshooting the workflow

The benefit of evaluating and diagramming your workflow is that it allows you to see how the records move through the process. It can help you identify missing transitions and orphaned states. Consider the WysiCorp workflow you just created.

Notice that there is no arrow leaving the closed states. This may not seem like a problem, but what happens if a user accidentally closes a record as duplicate? There is no way to re-open the record. The user will have to recreate it. To fix this problem, users should be able to re-open a record from the closed states. Use the following guideline to determine whether to use the State Transitions or the Event Resulting States section of the Configure Workflow dialog box.

Try it

In the WysiCorp workflow, add a Re-Open event to the Close (Forced Closed) and Closed (Fix) states.

This event should clear all assignments.

This event should have a resulting state of Open.

Diagram the workflow to make sure your changes have the expected results.

Guideline:

If an arrow is MISSING from the workflow, edit the State Transitions.

If an arrow is going to the WRONG STATE, edit the Event Resulting States.


160

Answer:



3 Click Add.

4 Enter ‘Re-open’ as the Name.

5 Select Open as the Resulting State.

6 Click Event clears the current assignment. The following screenshot shows the completed Details tab.

7 Click OK.

8 Click the Transitions tab.

9 Click Edit in the State Transitions section.

161


10 For the Closed (Forced Closed) and Closed (Fixed) events, select the Re-Open check box. The following screenshot shows the correct settings.

11 Click OK.

12 Click Diagram Workflow.

13 Click Select All.

14 Click OK. The following screenshot shows the changes to the workflow.


162

Practice: Customizing the Workflow

Directions

In this practice, you will change the workflow for the Acme Development project.



Situation

Acme wants to allow users to close a defect in the Open state and postpone the fix until a future release.

The workflow changes are summarized below.

The Postpone to a Future Release event should clear the current assignment.

Acme also wants to only the assigned users to be able to enter an event when a defect is in the Open (Verify Failed) state.

State Available events State change

Open Postpone to a Future Release

Closed (Future Release)

Closed (Future Release) Estimate -

Assign -

Re-open Open (Re-Opened)

163


Solution

Add a new state:

1 Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens.

2 Select Defects in the Type field.

3 Click Add. The Add State dialog box opens. The following screenshot shows the settings for the new Closed (Future Release) state.

Add a new event:

1 After clicking OK in the Add State dialog box, click the Events tab in the Configure Workflow dialog box.

2 Click Add. The Add Event dialog box opens. The following screenshot shows the settings for the Postpone to a Future Release event.

Configure transitions:

1 After clicking OK in the Add Event dialog box, click the Transitions tab in the Configure Workflow dialog box.

2 Click Edit in the State Transitions area. The Edit State Transitions dialog box opens.


164

3 Select the appropriate options and click OK. The following screenshot shows the settings for the new state and events.

4 Click OK.

5 Click Diagram Workflow.

6 Click Select All.

7 Click OK. The workflow should resemble the following.

8 Click OK in the Configure Workflow dialog box.

165


Configure workflow assignment rules:

1 Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens.

2 Select the Assignment Rules tab.

3 Select Open (Verify Failed) and click Edit. The Edit Assignment Rules for State dialog box opens.


166

4 Select the Only allow assigned users to enter an event when the defect is in the selected state option.

5 Click OK.

167

Module 7: How to Configure Automation Rules


Configure email and hyperlink settings

Configure notification rules

Edit email templates

Configure trigger rules

Configure escalation rules

This module deals with automatic activities triggered by changes to workflow states or events, or periods of inactivity. Notifications automatically sends emails. Triggers automatically perform actions on records, such as assignments. Escalations automatically perform actions on records that pass a filter when a rule is evaluated based on a schedule.

How to Configure Automation Rules

168

How to configure email options

Notification rules and escalation rules can send emails to users and customers. Before TestTrack can send email, you must enable email for the project and configure basic options. To access the email options, choose Tools > Administration > Project Options and click the Email category.

The return address options control the return address used when TestTrack sends email. You can also specify if TestTrack should use the same return email address regardless of the circumstances or if it should use the email address of the logged in user as the return address.

How to configure hyperlink options

Emails can include a hyperlink to open the record in TestTrack. Hyperlinks can use the ttstudio protocol, which opens links in the TestTrack Client, or the http protocol, which opens links in TestTrack Web. If emails will include http hyperlinks, you need to enter the TestTrack CGI URL address so the hyperlinks point to the correct location.

You can also control whether the user has to log in to open the record using the hyperlink and how often or how long the hyperlink can be used.

How to configure defect send mail options

You can configure defect send mail options to control the notification behavior when a defect is closed. You can specify if TestTrack should send an email when a defect is closed. You can specify when and who to send it to and which email template to use when a defect is closed or changed.

169


To access the defect send email options, choose Tools > Administrator > Project Options and select Send Mail in the Defects category.

Deciding which type of automation rule to use

You can create three types of automation rules: notifications, triggers, and escalations.

Write the type of automation rule you would use based on the situation.

If you want to: Then create this type of automation rule:

Send an email to users or customers after an activity is performed on a record.

Notification

Perform an action based on an activity performed on a record.

Trigger

Perform an action based on a period of inactivity on a record.

Escalation

1 You want to automatically assign defects that enter the Fixed state to a tester for verification.

2 You want to automatically change the priority of defects that have not been modified within the past week.

3 You want to email users when defects are assigned to them.


170

Answers:

1 Trigger—Triggers can automatically enter events, such as assignments, on records based on workflow state and other activities.

2 Escalation—Escalations can automatically modify a record field based on a schedule.

3 Notification—Notifications automatically email users or customers immediately after an event is entered or another activity is performed on a record.

How to configure notification rules

You can configure notification rules to send emails to users and customers. Notifications are sent when a record enters a specific state or a specific activity is performed, such as when a record is created. Notifications are always sent after records are saved in the project database.

Use the following steps to configure notification rules.

1 Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens with the Notifications tab selected.


3 Click Add to add a notification rule. The Add Notification Rule dialog box opens with the Precondition tab selected.

171



5 Select a Passes filter.

6 If you need to create a new filter, click Create Filter.


8 Select the activity that causes the notification to be sent.



172

10 Click Add. The Add Rule Action dialog box opens.

11 Select a Recipient.

12 Select an email Template.

13 If you do not want the user who made the change to receive an email notification, select Don’t send email if current user made the change.

14 If you only want the assigned user who made the change to receive an email notification, select Only send email to currently assigned user.

15 If you want to add the sent email to the corresponding record, select Track sent emails.

16 Click OK.

17 Click OK in the Add Notification Rule dialog box.

Tip: If you select Send to the following user, you can click the button next to the field to search for users to add to the notification.

See Reference: Email Templates, page 277 for the text of the email templates.

Note: This option is only available if email tracking is enabled for the project. Tracking sent emails requires more server space and slows performance.

173


Try it

Create a notification rule to send an email to Bob Burke, the development manager, when a defect is re-opened.

Answer:

1 Choose Tools > Administration > Automation Rules.

2 Click the Notifications tab.

3 Click Add to add a rule.

4 Enter ‘Re-Opened Defects’ as the Rule name. The following screenshot shows the correct settings.


Rule name Filter Send when Email template

Defect Re-Opened Not Filtered Defect state is Open (Re-Opened)

Defect Changed


174

6 Select Defect enters the Open (Re-Opened) state. The following screenshot shows the correct settings.


8 Click Add.

9 Select Send to the following users and select Burke, Bob.

10 Select Defect Changed from the Template list. The following screenshot shows the correct settings.

11 Click OK.

175


12 Click OK in the Configure Automation Rules dialog box.

How to customize email templates

TestTrack includes several email templates. You can edit any of these templates or add new templates.

Use the following steps to edit an existing template.

1 Choose Tools > Administration > Email Templates. The Configure Email Templates dialog box opens.

2 Select a record Type. A list of the email templates for the selected record type are displayed.

3 Select an email template and click Edit. The Edit Email Template dialog box opens.

See Reference: Email Templates, page 277 for the text of the different email templates.


176

The email text is displayed on the Format tab in the Message Body field. In addition to the name and description, the dialog box includes the text of the email. Variable text is indicated by field codes, which are set off by percent signs. Use the Available field codes list to add additional fields to the template.

The Options tab controls who can view the template and if the email can have multiple recipients.

Try it

Open the Defect Assignment template

Add the Product field code on the blank line between priority (%PRIO_L%: %PRIO%) and description (%DESC_L%: %DESC%) field codes.

Note: The field label is indicated by ‘_L’ at the end of the field code. For example, %COMP_L%: %COMP% inserts the component field label followed by a colon, a space, and the component value entered for the record.

Field label codes are not included in the Available field codes list. They must be entered manually. For a complete list of field codes, see ‘Reference: Field Codes’ in the TestTrack User Guide.

177


Answer:

1 Choose Tools > Administration > Email Templates.

2 Select Defect Assignment and click Edit.

3 Select the blank line between %PRIO_L%: %PRIO% and %DESC_L%: %DESC%.

4 Select %PROD% --- Defect Product from the Available field codes list.

5 Click Insert.

6 Select %PROD% in the Message Body and copy it.

7 Paste %PROD% before the other product field code.

8 Change the first field code to ‘%PROD_L%: ’. The following screenshot shows the edited template.


178

How to configure triggers

You can create triggers that automatically perform actions on records when records change. Trigger rules are evaluated when the TestTrack Server receives a request to save a record. If the record passes a filter and matches the activity specified in the rule, the trigger action is performed.

Trigger actions can be performed before or after records are saved in the project database. For example, if a user makes changes in the Edit Defect dialog box, trigger rules are evaluated when the user clicks OK or Apply to save the changes.

Before save triggers can perform the following actions:

Enter a workflow event on a record

Modify record field values

Prevent users from saving the record

Run a server-side executable

After save triggers can only run a server-side executable.

The following diagram shows how triggers are evaluated and executed.

179


Use the following steps to configure triggers.

1 Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens.

2 Click the Triggers tab.


4 Click Add. The Add Trigger Rule dialog box opens with the Precondition tab selected.


6 If you want to run the trigger when records are imported into the project from a text or XML file, select Apply this rule to items imported from a text or XML file.



180


9 Select when you want the trigger actions to be performed.

Select Before save if you want the trigger to perform actions before the record is saved in the project database.

Select After save if you want the trigger to run an executable after the record is saved in the project database.

10 If you selected Before save and you do not want to evaluate subsequent triggers if the rule passes, select Do not process additional rules if this rule passes.

11 Select the activity that causes the trigger to run.

Try it

New CheckMate feature requests need attention from the product manager.

Add a trigger rule named ‘CheckMate Feature Request Added’ that runs when a feature request is created.

Create a new filter for the trigger named ‘TR CheckMate Feature Requests’ that is shared with everyone that runs when the product is CheckMate Personal Finance product the type is Feature Request.

Do NOT click OK or add any trigger actions.

181


Answer:




4 Enter ‘CheckMate Feature Request Added’ as the Rule name.

5 Click Create Filter. The Add Defect Filter dialog box opens.

6 Enter ‘TR CheckMate Feature Requests’ as the Name and Description.

7 Select Shared With Everyone from the Share list.

8 Click Add. The Add Restriction dialog box opens.

9 Select Product from the Restrict by list.

10 Select CheckMate Personal Finance. The following screenshot shows the correct settings.

11 Click OK.

12 Repeat Steps 8 through 11 to add the restriction on the Type field. The following screenshot shows the correct settings.


182

13 Click Add in the Add Defect Filter dialog box.

14 Select TR CheckMate Feature Requests from the Passes filter list. The following screenshot shows the correct settings.


16 Select Defect is created. The following screenshot shows the correct settings.

183


How to add trigger actions

Actions are performed on records when the criteria in a trigger rule is met. You can add the following actions to trigger rules:

Enter event

Modify

Prevent

Run executable

Adding an Enter event action

The Enter event action automatically enters a workflow event. You can use this action to automatically assign records to users when records enter a specific state or move records through the workflow without changing the current assignment. You can only add this action to triggers that run before records are saved.



Note: You can only add one action of each type to a trigger. If you want to perform multiple instances of the same action, you must create multiple triggers. For example, if you want to assign the record and enter a Comment event to a record when it is created, you need to create two triggers.

Note: To maintain the integrity of the workflow, you can only configure enter event actions that perform assignments for states that have an event with only one resulting state.


184

3 Select Enter event from the Action list.

4 Select the Event to enter.

5 Select any Assign Options if the event results in a new assignment.

6 Click OK.

Try it

Add a rule action to assign new feature requests to William Clemons, the product manager.

Do NOT click OK in the Add Trigger Rule dialog box.

Answer:

1 Click the Actions tab in the Add Trigger dialog box.



185


4 Select Assign from the Event list.

5 Select Assign to the following users and select Clemons, William. The following screenshot shows the correct settings.

6 Click OK.

Adding a Modify action

The Modify action automatically changes field values. This action can only modify general and custom field values, not event fields. You can only add this action to triggers that run before records are saved.

1 Click the Actions tab in the Add Trigger Rule dialog box.



186

3 Select Modify from the Action list.

4 Make any changes to the field values.

5 Click OK.

Try it

Add a rule action to modify the Priority field for feature requests to Future Release.

Do NOT click OK in the Add Trigger Rule dialog box.

Answer:

1 Click the Actions tab in the Add Trigger dialog box.


3 Select Modify from the Action list.

Note: Some fields have Prepend and Append options. If you select Prepend, the text is added before the existing text in the field. If you select Append, it is added after the existing text.

187


4 Select Set to value and Future Release from the Priority lists. The following screenshot shows the correct settings.

5 Click OK.

Adding a Prevent action

The Prevent action stops users from saving the record and displays a customized message. You can only add this action to triggers that run before records are saved.

If a trigger with this action runs, subsequent rules are not evaluated and the record is not saved.


188



3 Select Prevent from the Action list.

4 Enter the Message to display when users attempt to save the record.

5 Click OK.

Adding a Run executable action

The Run executable action automatically runs a script or compiled program. You can add this action to triggers that run before and after records are saved. For example, you can run a script from an after save trigger that sends information to an external reporting system.



189


3 Select Run executable from the Action list.

4 Enter the full path to the Executable location.

The executable location must be the relative or absolute path to the executable on the TestTrack Server. Multiple files and arguments are not supported.

5 Click OK.

6 Click OK in the Add Trigger Rule dialog box.

Configuring the default trigger rule

After you configure trigger rules, you may want to specify what happens if a record does not pass any of the rules. You configure the default trigger rule by clicking Add Default on the Triggers tab in the Configure Automation Rules dialog box.

The options for the default rule are the same as the options for other trigger rules.


190

How to configure escalation rules

Escalation rules automatically perform actions based on a schedule. Escalation rules are generally used to make sure that work is performed on defects within a certain period of time. Escalation rules can be evaluated on a daily, weekly, or monthly basis. You can also manually evaluate rules to perform actions on records that pass the rule immediately.

Escalation rules can perform the following actions:

Enter a workflow event on a record

Modify record field values

Send email to a user or customer

Run a server-side executable

Use the following steps to configure escalation rules.


2 Click the Escalations tab.


4 Click Add. The Add Escalation Rule dialog box opens with the Precondition tab selected.

191



6 If you want to inactivate the rule after it runs the first time so it does not run again, select Inactivate rule after it runs once.

7 If you only want to run the rule once for each record, select This rule should only be applied once per item.


9 Click the Schedule tab.

10 Select an Evaluate frequency.

11 Select any Options based on the frequency selected in the Evaluate list.



192


14 Select an Action.

15 Enter or select the action options.

16 Click OK.

17 Click OK in the Add Escalation Rule dialog box.

Try it

Create an escalation rule named ‘CheckMate Defects Need Review’ that runs every Monday at 7:00 for defects that have not been reviewed.

Create a new filter for the escalation named ‘ES CheckMate Defects to Review’ that is shared with everyone and runs when the product is CheckMate Personal Finance, the disposition is <not set> and Open - Not Reviewed, and the date found is within the past seven days.

Assign defects that pass the new filter to Bob Burke.

Answer:


2 Click the Escalations tab.


4 Enter ‘CheckMate Defects Need Review’ as the Rule name.

5 Click Create Filter. The Add Defect Filter dialog box opens.

6 Enter ‘ES CheckMate Defects to Review’ as the Name and Description.

7 Select Shared With Everyone from the Share list.

Note: You can add the same actions as you can for triggers except for the Prevent action. You can also add the Send email action, which includes the same options as notification rules.

193



9 Select Product from the Restrict by list.

10 Select CheckMate Personal Finance. The following screenshot shows the correct settings.

11 Click OK.

12 Repeat Steps 8 through 11 to add the restriction on the Disposition field. The following screenshot shows the correct settings.

13 Repeat Steps 8 through 11 to add the restriction on the Date Found field. The following screenshot shows the correct settings.

14 Click Add in the Add Defect Filter dialog box.


194

15 Select ES CheckMate Defects to Review from the Passes filter list. The following screenshot shows the correct settings.


17 Select Weekly from the Evaluate list.

18 Select 7:00 AM from the Start time field.

19 Select Monday in the Days list. The following screenshot shows the correct settings.





195


24 Select Assign to the following users and select Burke, Bob. The following screenshot shows the correct settings.

25 Click OK.



196

Practice: Configuring Automation Rules

Directions

In this practice, you will add triggers, escalations, and notification rules to the Acme Development project.



Situation

Acme wants to further customize the functionality and workflow of their project. Configure the project to perform the following.

1 When a defect is fixed, it should be automatically assigned to Abby Adams. Name the rule ‘Defect Fixed’.

2 When a CheckMate defect is closed, the user who entered the defect should receive an email. Use the NT CheckMate Defects filter and the Defect Closed template for this email. Name the rule ‘CheckMate Defect Closed’.

3 Defects that fail verification must be fixed each week in time to be included in the weekend build. A reminder email should be sent to the currently assigned users every Friday at 9:00 AM for failed defects that are not fixed. Use the Defect Assigned template for this email. Name the rule ‘Failed Defect Needs Attention’.

197


Solution

Configure trigger rule:


2 Select the Triggers tab.

3 Click Add. The Add Trigger Rule dialog box opens.

4 Enter ‘Defect Fixed’ as the Rule name. The following screenshot shows the correct settings.


6 Select Defect enters Fixed state. The following screenshot shows the correct settings.


198





11 Select Assign to the following users and select Adams, Abby. The following screenshot shows the correct settings.

12 Click OK.


Configure notification rule:

1 Click the Notifications tab in the Configure Automation Rules dialog box.

2 Click Add. The Add Notification Rule dialog box opens.

3 Enter ‘CheckMate Defect Fixed’ as the Rule name.

4 Select ‘NT CheckMate Defects’ from the Passes filter list. The following screenshot shows the correct settings.

199



6 Select Defect enters Fixed state. The following screenshot shows the correct settings.


8 Click Add. The Add Rule Action dialog box opens with the Send email action selected.

9 Select Send to the Entered by user.


200

10 Select Defect Closed from the Template list. The following screenshot shows the correct settings.

11 Click OK.

12 Click OK in the Add Notification Rule dialog box.

Configure escalation rule:

1 Click the Escalations tab in the Configure Automation Rules dialog box.

2 Click Add. The Add Escalation Rule dialog box opens.

3 Enter ‘Failed Defects Needs Attention’ as the Name. The following screenshot shows the correct settings.


5 Select Weekly from the Evaluate list.

6 Select 9:00 AM from the Start time field.

201


7 Select Friday in the Days list. The following screenshot shows the correct settings.


9 Click Add.

10 Select Send email from the Action list.

11 Select Send to the assigned users.

12 Select Defect Assignment from the Template list.

13 Select Only send email to the currently assigned user. The following screenshot shows the correct settings.


202

14 Click OK.


16 Click OK in the Configure Automation Rule dialog box.

203

Integrated Practice: Customizing the Workflow

Directions

Customize the workflow with the correct events, states, and transitions.


WysiCalc project

When you are finished, compare your results with the Solution section. You have 10 minutes to complete this practice. If you have problems during the practice, contact the instructor.

Situation

WysiCalc wants to review new defects and classify them as bugs, enhancements, or documentation issues before working on them.

Update the workflow in the WysiCalc project to reflect following changes.

Take a moment before opening the Configure Workflow dialog box to identify which of the following are states, events, and events that cause states to change.

State Activities/events State change/actions

Open Classify Bug

Enhancement

Documentation

CanNOT fix the defect from the Open state

Bug Estimate

Assign

Fix

Close

-

Enhancement Estimate

Assign

Fix

Close

-

Customizing the Workflow

204

Documentation Estimate

Assign

Fix

Close

Automatically assign to Jane Adams

State Activities/events State change/actions

205


Solution

Bug, Enhancement, and Documentation are new open states.

1 Choose Tools > Administration > Workflow to access the Configure Workflow dialog box.

2 Click Add to add the three new states. The following screenshots show the correct settings for the new states.


206


4 Click the Add button to add the Classify event. The following screenshot shows the correct settings for the Classify event.

5 Click OK.

6 In the Configure Workflow dialog box, click the Transitions tab.

207


7 Click Edit in the State Transitions area. Configure the following state transitions. Make sure the Fix check box is cleared for the Open state.

8 Click OK.

9 In the Configure Workflow dialog box, click Edit in the Event Resulting State section and confirm that the transitions for the Classify event matches the following screenshot.

10 Click OK.

11 In the Configure Workflow dialog box, click Diagram Workflow.

12 Click Select All.


208

13 Click OK. Your workflow diagram will resemble the following screenshot.

14 When a defect is classified as a documentation issue, it is automatically assigned to Jane Adams. Choose Tools > Administration > Automation Rules.


16 Click Add. The Add Trigger Rule dialog box opens.

209



18 Click the Trigger When tab and select Defect enters Documentation state.

19 Click the Actions tab and then click Add.



210

21 Select Assign from the Event list. Select Assign to the following users and Adams, Jane.

22 Click OK.


211

Module 8: How to Manage Data


Export and import XML files

Export and import text files

Make bulk field changes

Duplicate records

Merge defects

TestTrack’s export and import functionality allows you to move data between projects and manage it with other applications. In addition, TestTrack allows you to merge and duplicate defects so you can effectively manage data within the project.

How to Manage Data

212

How to export data to an XML file

XML format is the recommended export and import format for TestTrack data. Exporting to an XML file provides the following benefits:

You do not need to match project fields and data fields when importing and exporting records.

You can import and export multiple reported by records.

You can import and export multiple instances of the same defect actions.

You can import and export more than one record type.

You can import and export file attachments associated with defects.

You can import and export folder information.

You can use the XML export functionality to export defects, test cases, test runs, folders, users, customers, and test configurations. This data can then be imported into another TestTrack project.

You can export all of the records or a subset of records. If you want to export specific records, open the corresponding list window and select the records you want to export before opening the XML Export dialog box. If you are exporting defects, you can use a filter to locate the records you want to export.

Use the following steps to export data to an XML file.

1 Choose File > Export > XML Export. The XML Export dialog box opens.

2 Specify which records to export.

3 Select the type of records you want to export. To export multiple record types, Ctrl+click each record type.

213

How to Manage Data

4 Select the Export Options.

5 Click Export. The Export XML File dialog box opens.

6 Select the file location, enter a file name, and click Save. A progress indicator opens and lets you know the file is being exported.

Try it

In the Acme Development project, export all the users except the System Administrator to a file named ‘AcmeUsers.xml.’

Save the file on the desktop.

How to Manage Data

214

Answer:

1 Choose View > Users. The Users window opens.

2 Select all of the users except for the System Administrator.

3 Choose File > Export > XML Export. The following screenshot shows the correct settings for the XML Export dialog box.


5 Enter ‘AcmeUsers’ as the File name.

6 Select Desktop from the Save In list.

7 Click OK.

How to import data from an XML file

One of the benefits of importing from an XML file is that you do not have to match the fields in the file to fields in the project when you import the data into TestTrack. TestTrack will automatically match the fields.

Use the following steps to import data from an XML file.

215

How to Manage Data

1 Choose File > Import > XML Import. The XML Import dialog box opens.

2 Click Browse to select an XML or ZIP file to import. The Open XML File dialog box opens.

3 Select the file and click Open.

4 Select the Number Import Options.

You can specify whether you want TestTrack to assign numbers to imported records or if you want to use the record numbers in the file.

5 Decide what to do if a pop-up menu option in the file does not exist in the project you are importing to.

You can add the missing menu item or use the default value for the field without adding the value in the XML file.

6 Click Import to import the records. The XML Import Warnings and Errors dialog box opens.

7 If you want to save the warnings and errors, click Save As.

8 Click Close in the XML Import Warnings and Errors dialog box.

Try it

Open the AcmeProduction project and export the defects as an XML file named ‘Acme_Production_Defects.xml.’

Then open the Acme Development project and import the defects.

How to Manage Data

216

Answer:

1 Choose File > Export > XML Export.

2 Select Defects in the XML Export dialog box. The following screenshot shows the correct settings.


4 Enter ‘Acme_Production_Defects’ as the File name.

5 Click Desktop.

6 Click OK.

7 Choose File > Switch Project.

8 Select the Acme Development project and click Switch.

9 Choose File > Import > XML Import.

10 Click Browse to locate the file.

217

How to Manage Data

11 Select Import defect number field information from the XML file. The following screenshot shows the correct settings.

12 Click Import.

How to export data to a text file

While exporting to a text file is not the preferred method, it does provide access to a greater variety of information for export. Using an XML file, you can export the following:

Defects

Test cases

Test runs

Requirements

Requirement Documents

Folders

Users

Customers

Test configurations

Using a text file, you can also specify which fields to export. In addition, you can export the following:

Security groups

Filters

Reports

Tasks

How to Manage Data

218

You canNOT export folders to a text file.

Exporting data to a text file

Use the following steps to export data to a text file.

1 If you want to export a subset of records, open the corresponding list window and select the records you want to export.

2 Choose File > Export > Text File Export. The Text Export dialog box opens.

3 Select the type of fields you want to export from the Export fields list.

4 Select the fields to export.

5 Select the export options.

Note: You canNOT import security groups, filters, reports, or tasks into TestTrack.

Guideline: Use XML export if you are transferring data from one TestTrack project to another.

Use TEXT export if you want to use the data in an application other than TestTrack.

219

How to Manage Data

The Convert EOLs to spaces option converts carriage returns/line feeds to spaces in the export file.

6 Click Export. The Export File dialog box opens.

7 Select the file location and enter a file name.

8 Click Save.

Try it

Open the AcmeProduction project and export all the defects, but only export the following fields:

Number

Summary

Product

Description

Select Convert EOLs to spaces and name the file ‘AcmeDefectSummaries.’

How to Manage Data

220

Answer:

1 Choose File > Export > Text File Export.

2 Select Defects from the Export list.

3 Click Select None.

4 Click Number, Summary, Product, and Description. The following screenshot shows the correct settings.

5 Click Export.

6 Select the file location and enter ‘AcmeDefectSummaries’ as the File name.

7 Click Save.

221

How to Manage Data

How to import a text file

Exporting to a text file gives you access to different data than an XML export and provides the flexibility to control what fields are exported. When you import from a text file, you must match the fields in the file with the fields in the project to ensure that the data is saved in the correct project fields.

Use the following steps to import data from a text file.

1 Choose File > Import > Text File Import. The Text Import dialog box opens.

2 Select the type of fields you want to import.

3 Click Browse to select a file to import. The Open dialog box opens.

4 Select the file you want to import.

How to Manage Data

222

5 Click Open. The Select Code Page dialog box opens. Use the code page to specify the character encoding (language) used by the text file. TestTrack uses Unicode. If the file does not use Unicode encoding, you must specify the encoding so TestTrack can map the characters correctly.

6 Select a Code Page and click OK. The Import dialog box is populated with the text file information.

7 Select the Import Options.

8 If the file contains column headings, select Ignore first record.

9 If the file contains quotes around comma- and tab-delimited records, select Handle quoted text.

10 If the file has vertical tab characters that represent carriage returns, select Map vertical tab to return.

11 Select the Delimiter used to separate fields.

12 Match the TestTrack fields in the right column to the fields in the left column. The column on the left displays the fields as they appear in the file.

13 Click and drag the fields in the right column up or down to the proper position.

14 Select the fields to import by selecting the check box next to the field in the right column.

15 Click Import. The Importing Defects dialog box opens.

16 When the import is complete, click Close.

223

How to Manage Data

Try it

Open the WysiDevelopment project and import the ‘AcmeDefectSummaries’ file.

Make sure to match the fields in the file to the fields in the project.

Answer:

1 Choose File > Import > Text File Import.

2 Select Defects in the Import fields list.

3 Click Browse and select AcmeDefectSummaries.

4 Select Ignore first record.

5 Click Select None.

6 Select the Number, Summary, Product, and Description in the TestTrack fields.

7 Drag the Description field so it lines up with the Description field in the text file. The following screenshot shows the proper settings.

8 Click Import.

How to Manage Data

224

How to perform bulk field changes

TestTrack allows you to quickly update data by performing bulk field changes. Use the following steps to make bulk field changes.

1 Choose View > Defects.

2 Select the defects you want to change.

3 Choose Activities > Bulk Field Changes. The Bulk Field Changes dialog box opens.

The fields are grouped by the dialog box in which they appear. Certain fields have Prepend and Append options. If you select Prepend, the text will be placed before the existing text in the field. If you select Append, it will be placed after the existing text.

4 Make any changes to the field values.

5 Click OK.

Try it

In the Acme Development project, open the Defects window and select the CheckMate Defects filter.

Select the open defects and change the Entered by name to Jean Barber.

Note: The following steps use defects. You can also perform bulk field changes on test cases, test runs, requirements, and requirement documents.

Note: Perform bulk field changes with caution. You can accidentally enter bad data if you are not careful.

225

How to Manage Data

Answer:

1 Choose View > Defects.

2 Select the open defects.

3 Choose Activities > Bulk Field Changes.

4 Select Set to value and Barber, Jean from the Entered by lists.

5 Click OK.

How to duplicate records

Now that you have learned how to add records and perform basic activities, you are ready to look at more advanced operations. Occasionally, a defect may contain several defects that you or the project manager might want to track separately. For example, a defect contains several proposed features for the next release of the software. Not all of those features will be included in the next release. Having them all together in one defect can make it difficult to tell which components the different activities apply to. In this case, you can duplicate the original defect one or more times and edit the defects so it is easier to track the efforts for each feature.

Use the following steps to duplicate a defect.

Note: The following steps use defects. You can also duplicate test cases, test runs, requirements, and requirement documents.

How to Manage Data

226

1 Choose View > Defects. The Defects window opens.

2 Select the defect you want to duplicate.

3 Choose Edit > Duplicate Defect. The Duplicate Defect Options dialog box opens.

4 Select Link duplicated defect with original to link the new defect with the original defect.

Select a Link definition. The list includes all peer link definitions for defects.

Enter a Link comment. The comment is displayed on the defect Links tab and in the link diagram.

5 Select Identify original defect in system comment to add a system comment to the Workflow tab of the new defect that indicates the original defect number and summary.

6 Select Identify original defect in Description text to add a line to the Description field of the new defect that indicates the original defect number and summary.

227

How to Manage Data

7 Select the information to copy from the original defect.

Select History information to copy information from the History tab.

Select File attachments to copy attachments from the Attachments mini tab on the Detail tab.

Select SCC attachments to copy attachments from the Source Code tab.

Select Workflow to copy information from the Workflow tab.

Select Email messages to copy emails from the Email tab.

Select Folder information to copy the new defect to the same folder as the original defect. Defects can only be copied to folders you have access to.

8 Click OK.

9 Edit the duplicated defect to make any necessary changes.

Try it

The new versions of CheckMate Personal Finance and AcmeAccount Professional will contain a spell check feature in the Account Manager. Create a defect for CheckMate Personal Finance using the following information. Then duplicate the defect and edit the new defect so that it applies to AcmeAccount Professional.

Summary: Create a spell check function for CheckMate

Disposition: Open - Not Reviewed

Type: Feature Request

Priority: Future Release

Product: CheckMate Personal Finance

Component: Account Manager

Reference: (blank)

Severity: <not set>

Entered by: Adams, Abby

Found by: Adams, Abby

Date Entered: Current date

Version: 5.0

Description: Add the ability to spell check account names in the Account Manager.

How to Manage Data

228

Answer:

1 Search the project to make sure that the defect has not already been entered.

2 Select Create > Defect. The following screenshot shows the completed Add Defect window.

3 Click Add.

4 Close the Add Defect window.

5 Click the new defect you just created.

6 Choose Edit > Duplicate Defect.

7 Open the duplicate.

8 Edit the Summary so that it references AcmeAccount Professional.

9 Select AcmeAccount Professional from the Product list. The following screenshot shows the changes.

229

How to Manage Data

10 Click OK.

How to merge defects

You can link defects to indicate a relationship between them but still track them separately. However, there are occasions where the same defect is reported by different users. The summaries could be written so it is not clear they concern the same defect or they may have been added twice by mistake. If you want to preserve the different descriptions and the activities taken, you can merge the separate defects into one. The information from the individual defects is stored on the defect’s Detail tab.

Use the following steps to merge defects.

1 Select the defects you want to merge.

2 Choose Edit > Merge Defects. You are prompted to confirm the merge.

3 Click OK. The defects are merged. The resulting defect assumes the lowest defect number and the type, priority, and severity of that defect.

Try it

Create a new defect based on the following information.

Then merge it with the other CheckMate spell check defect you created.

Summary: You should be able to CheckMate data

Disposition: Open - Not Reviewed

Type: Feature Request

Priority: Future Release

Product: CheckMate Personal Finance

Component: Account Manager

Reference: (blank)

Severity: <not set>

Entered by: Burke, Bob

Found by: Burke, Bob

Date Entered: Current date

Version: 5.0

Description: Add the ability to spell check account names in the Account Manager.

How to Manage Data

230

Answer:

1 Choose Create > Defect.

2 Complete the general information and Detail tab. The following screenshot shows the completed Add Defect window.

3 Click Add.

4 Click the new defect.

5 Hold the Ctrl key and click the ‘CheckMate Spell Check’ defect.

6 Choose Edit > Merge Defects. A message box opens to confirm the merge.

231

How to Manage Data

7 Click OK in the message dialog box. The following screenshot shows the merged defect.

How to Manage Data

232

Practice: Importing and Exporting Data

Directions

In this practice, you will import data into the Acme Development project.



Beta.xml (located on the Desktop)

Users.txt (located on the Desktop)



Situation

1 Acme maintains a separate project for tracking defects during the alpha and beta stages of development. After the product is released, the defects from that project are migrated to the Acme Development project. Import the defects from the Beta.xml file.

Assign the next defect number to the imported defects. If a menu item in the imported data does not exist in the Acme Development project, use the default values in pop-up menus.

2 Acme’s QA department is adding ten people who need access to TestTrack. The QA manager has all their user information stored in a text file named ‘Users.txt.’ Import the users into the project.

The file uses a tab delimiter and has a header record.

233

How to Manage Data

Solution

Import defects:

1 Choose File > Import > Import XML. The XML Import dialog box opens.

2 Click Browse. The Open XML File dialog box opens.

3 Locate the Beta.xml file and click Open.

4 Select Assign the next available defect number to any imported defects.

5 Select Use the default value (ignoring the value in the XML file). The following screenshot shows the correct settings.

6 Click Validate XML File. The XML Import Warnings and Errors dialog box opens.

7 Click Close.

8 Click Import. The Importing Records dialog box opens.

How to Manage Data

234

9 After the records are imported, the XML Import Warnings and Errors dialog box opens.

10 Click Close.

Import users:

1 Choose File > Import > Text File Import. The Text Import dialog box opens.

2 Select User from the Import fields list.

235

How to Manage Data

3 Click Browse. The Open dialog box opens.

4 Locate the Users.txt file and click Open. The Select Code Page dialog box opens.

5 Click OK. The following screenshot shows the Text Import dialog box after the file is selected.

6 Compare the fields in the text file with the fields in the project and make sure they match.

7 Select Ignore first record.

How to Manage Data

236

8 Select Tab as the delimiter. The following screenshot shows the correct settings.

9 Click Import. The Importing Defects dialog box opens.

10 Click Close when the import is complete.

237

Module 9: How to Create a Report


Decide which type of report to use for different situations

Create a detail report

Create a list report

Create a distribution report

Create a trend report

Add an external report

Set the report options for a project

TestTrack reports can help you manage projects and analyze data.

How to Create a Report

238

TestTrack report types

TestTrack includes the following built-in report types.

Detail report

A detail report displays detailed information about defects, folders, test cases, test runs, customers, users, security groups, or test configurations. It includes ALL the available fields for the type of data you select.

List report

A list report displays information about defects, test cases, test runs, folders, customers, users, security groups, or test configurations using a SUBSET of the available fields.

Tip: You can create a quick detail or list report that uses the current filter and sort options by selecting File > Print.

239


Distribution report

A distribution report displays the total number of defects, test cases, or test runs based on different categories.

Trend report

A trend report displays the changes in defects, test cases, or test runs totals over a period of time.

Use the report descriptions to complete the following. Write the type of report you would use for each situation.

1 You want to view all the details of the records that match the CheckMate filter.

2 You want to see the total number of records created over the last month, subtotaled by the priority.

3 You want to compare the number of records by type and priority.

4 You want to view all the details of all the records but only want to include the Number, Summary, and Product fields.


240

Answers:

1 Detail report — The report will use all the available fields.

2 Trend report — You want to see totals over time.

3 Distribution report — You want to see how records are spread across two categories.

4 List report — You want to specify the fields displayed in the report.

How to create a detail report

A detail report displays all the fields for defects, test cases, test runs, folders, customers, users, security groups, or test configurations even if the fields are empty. You can create a report that displays all the defects or you can use a filter to limit the results. The following screenshot shows a section of a detail report.

Use the following steps to create a detail report.

1 Choose Create > Report > Detail. The Add Detail Report dialog box opens with the Report On tab selected.

2 Enter a Name. The report name is displayed in the Reports list window.

3 Enter a Title. The title is displayed at the top of the report when it is viewed or printed.


241


5 On the Report On tab, select the record type (defects, test cases, test runs, folders, customers, users, security groups, or test configurations) from the Report contains list.

6 If you are NOT reporting on defects, test cases, or test runs select the records to include in the report.

7 Click the Options tab.

8 Select a Stylesheet.

9 If you want the report to use an existing filter, select it from the Filter list.

10 Select Print items on separate pages to insert page breaks between each record in the report.

11 Click the Sorting tab.

12 Select a Primary or Secondary sort column and set the column sort order. The Secondary sort column is only enabled if there are at least two fields in the report.

13 Click Add.

Note: The Sorting tab is disabled for detail reports based on folders.


242

14 To view the report, choose View > Reports. The Reports list window opens.

15 Select the report in the list.

16 Click Preview. The report opens in a browser window.

Try it

In the AcmeProduction project, create a detail report named ‘CheckMate Defects.’

Include all the CheckMate defects in the report.

Share the report with all users and use the DefectDetailReport stylesheet.

Answer:

1 Choose Create > Report > Detail.

2 Enter ‘CheckMate Defects’ in the Name and Title fields.

3 Select Shared With Users as the Share option.

243


4 On the Report On tab, select Defects from the Report contains list. The following screenshot shows the general settings and the settings for the Report On tab.


6 Select DefectDetailReport.xslt from the Stylesheet list.

7 Select SG CheckMate Defects from the Filter list. The following screenshot shows the settings for the Options tab.

8 Click Add.

How to create a list report

A list report is similar to a detail report, except it allows you to specify which fields to include in the report and to customize the format. The following screenshot shows a section of a list report that includes the date found, the record number, summary, and product fields.

Use the following steps to create a list report.

1 Choose Create > Report > List. The Add List Report dialog box opens with the Report On tab selected.

2 Enter a Name

Note: You can also create list reports with drill-down charts to display data using different stylesheets.


244

3 Enter a Title.


5 On the Report On tab, select a record type from the Report contains list.

6 Select the fields from the Available Fields list and click Add.

7 Select a field from the Fields in Report list and click Top, Move Up, Move Down, or Bottom to change the field order.


9 Select a stylesheet.

10 If you want the report to use an existing filter, select it from the Filter list.

11 Enter the number of Records per printed page to add page breaks between rows in the report.


Note: The Sorting tab is disabled for detail reports based on folders.

245


13 Select a Primary and Secondary sort column and set the column sort order. The Secondary sort column is only enabled if there are at least two fields in the report.

14 Click the Formatting tab. Field and table settings are defined by the default stylesheet. This tab lets you override the stylesheet settings.

15 Select the Field Settings and the Table Settings.

16 Click Add.

Try it

Create a defects list report named ‘Defects by Product/Status.’

Include the following fields in this order:

Number

Product

Status

Summary

Found by

Use the NonDetailReport stylesheet.

Sort the report by Product and then by Status.

Answers:

1 Choose Create > Report > List.


246

2 Enter ‘Defects by Product/Status’ in the Name and Title fields.

3 Select Share With Everyone as the Share option.

4 Select Defects from the Report contains list.

5 Select the Number, Product, Status, Summary, and Found by from the Available Fields list and click Add. The following screenshot shows the general settings and the settings for the Report On tab.


7 Select NonDetailReport.xslt from the Stylesheet list.


9 Select Product from the Primary Sort Column list.

247


10 Select Status from the Secondary Sort Column list. The following screenshot shows the settings for the Sorting tab.

11 Click Add.

12 In the Reports list window, select the report and click View. The following screenshot shows a preview of the finished report.

How to create a distribution report

A distribution report allows you to categorize records using different TestTrack fields. You can also view totals and chart the results. The following screenshot shows a section of a distribution report.

Use the following steps to create a distribution report.

1 Choose Create > Report > Distribution. The Add Distribution Report dialog box opens with the Report On tab selected.

2 Enter a Name

3 Enter a Title.



248

5 On the Report On tab, select a record type from the Report contains list.

6 Specify what data you want to base the report on. The following sample reports show examples of the different defect options.

The Defects option groups defects by user. A report created using this option displays a single total for each user who performed a SPECIFIC ACTION.The following report displays the total number of defects by the user who found them.

The Defects reported by option groups defects based on different reported by criteria, such as source or type. These reports display a single total for ONE of the following:

Each value in an event pop-up list

Each state

Each test configuration

The following report displays defects grouped by the current state that they are in.

249


The Defect status by option creates a crosstab report based on Status and one of the following:

Type

Priority

Product

Component

The following report displays defects grouped by status and by the type of defect.

The Defects by option creates a crosstab report based on any TWO fields. The following report displays defects grouped by type and priority.

7 Click the Options tab and set the options.

Distribution reports offer additional options, including the ability control whether to display total and empty rows or columns.


9 Select a Primary and Secondary sort column and set the column sort order.


250

10 If you want to include a chart with the report, click the Charting tab.

11 Click New Chart and select the charting options.

12 Click Add.

Try it

Create a report named ‘Status/Severity’ that groups defects based on the Status and Severity fields.

Share the report with everyone.

Use the NonDetailReport stylesheet. Show the empty columns and rows.

Create a pie chart of number of defects in the different statuses.

Base the chart on the row totals.

Then, create a pie chart for the severity based on the column totals.

251


Answers:

1 Choose Create > Report > Distribution.

2 Enter ‘Status/Severity’ in the Name and Title fields.


4 On the Report On tab, select Defect.

5 Select Status and Severity from the Defect by list. The following screenshot shows the settings for the Report On tab.


7 Select the NonDetailReport.xslt stylesheet.

8 Clear the Hide empty columns and Hide empty rows options. The following screenshot shows the settings for the Options tab.

9 Select the Charting tab.

10 Click New Chart.

11 Select Pie from the Type list.

12 Select Row Totals from the Data to Chart list.


252

13 Enter ‘Status’ as the Title. The following screenshot shows the correct settings.

14 Repeat Steps 10 through 13 substituting Column Totals for the Data to Chart to create the Severity chart.

How to create a trend report

A trend report shows records totals over time. The following screenshot shows a trend report that displays the open defects on March 14, 2006, totaled by priority.

Use the following steps to create a trend report.

1 Choose Create > Report > Trend. The Add Trend Report dialog opens with the Report On tab selected.

2 Enter a Name

3 Enter a Title.


253


5 On the Report On tab, specify the data you want to base the report on.

The Defect status (Open, Fixed, etc.) in period option shows the totals for all the statuses over time. The following report shows the total defects in each state grouped by date.

The Defects by option lets you build a report of defects in a status grouped by another defect field. The following report shows open defects for each date grouped by the type of defect.


254

Using the Defect open age in period option, you can create a report that shows how long defects have been open.

With the Actual vs. Estimated hours option, you can create a report that shows the validity of your estimates.

With the Defect status aggregate totals of defects in each state for period option, the report shows the total number of defects in each state for each period.

The Defects Open vs. Closed option allows you to compare the number of open and closed defects over time.

6 Click the Options tab and set any options.

7 If you want to include a chart with the report, click the Charting tab.

8 Click New Chart to select the charting options.

9 Click Add.

Try it

Create a report named ‘Actual vs. Estimated’ that displays the age of open defects.

Configure the report to show defects opened on June 10, 2006 and after.

255


Use the NonDetailReport stylesheet.

Answer:

1 Choose Create > Report > Trend.

2 Enter ‘Actual vs. Estimated’ in the Name and Title fields.



5 On the Report On tab, select Actual vs. Estimated hours.


7 Select the From check box and enter ‘6/10/2006.’

8 Select NonDetailReport.xslt as the Stylesheet. The following screenshot shows the correct settings for the Options tab.

9 Click Add.


256

How to add an external report

External reporting allows you to view reports from external reporting services and gives you more control over report content and more output format options. You create an external report the same way you create a built-in report. After adding an external report to TestTrack, you can choose the output format and open the report in the associated external report viewer.

Use the following steps to add an external report.

1 Choose Create > Report and choose the name of the reporting service you want to add the report from. The Select External Report dialog box opens.

2 Select the report you want to add.

3 Click Add.

How to set report options

You can specify some of the default report settings, such as the fonts and time zone, using the project options.

Use the following steps to set the report options.


2 Click Reports in the Defects category.

3 Select the Actual Hours Fields you want to use in the reports to calculate the number of hours it took to complete a task.

Note: You can only edit the Name, Output Type, and Share fields of external reports in TestTrack.

257


4 Select the Estimated Hours Fields you want to use in the reports to calculate the estimated number of hours to complete a task.

5 Click the Reports category.

6 Select a Look for new server stylesheets time interval.

7 Select a time zone option.

8 Select the Diagram Font to use for text in workflow diagrams.

9 Select the diagram Output Type to specify the file format used when saving workflow diagrams.

10 Select a Chart Font to use for text in report charts.

Try it

Change the project’s report options so TestTrack looks for new stylesheets every hour and uses GMT for displaying times in reports.

Answer:

1 Choose Tools > Administration > Project Options.

2 Select the Reports category.


258

3 Select 1 hour from the Look for new server stylesheets list.

4 Select Use GMT time zone. The following screenshot shows the correct settings.

5 Click OK.

259


Practice: Creating Reports

Directions

In this practice, you will create reports for the Acme Development project.





Situation

Acme has been using TestTrack for several weeks, and now they need reports to effectively manage the project. Create the following reports.

Detail report

The project manager needs a report that shows the details of all defects. The report should use the DefectDetailReport stylesheet.

The defects should be sorted by the status and then by defect number. Name this report ‘Management Report (by Status).’ All users should have access to this report.

Distribution report

The development manager needs a summary report of how many defects are in the different statuses grouped by product. Name the report ‘Defect Status’ and configure it so all users can view it.

Use the NonDetailReport stylesheet. The report should show values for all the statuses and products even if the values are zero. The data in the report should not be sorted or charted.

List report

The project manager also needs a report that lists just the open and fixed defects. (Hint: You must create a filter first.) She wants to select the defect statuses to include when she runs the report.

The report should list the date the defect was reported, the defect number, and the summary information (in that order). The report should be sorted by the report date and then by the defect number.

Name the report ‘Open Defects (by Date)’ and configure it so all users can view it. Use the NonDetailReport stylesheet.

Preview the report when you are finished. Exclude fixed defects to see only those with an open status.


260

Solution

Create a detail report:

1 Choose Create > Report > Detail. The Add Detail Report dialog box opens.

2 Enter ‘Management Report (by Status)’ in both the Name and Title fields.

3 Select Share With Users from the Share list.

4 Select Defects from the Report contains list. The following screenshot shows the general report settings.


6 Select DefectDetailReport.xslt from the Stylesheet list. The following screenshot shows the settings for the Options tab.


8 Select Status as the Primary Sort Column.

261


9 Select Number as the Secondary Sort Column. The following screenshot shows the settings for Sorting tab.

10 Click Add.

Create a distribution report:

1 Choose Create > Report > Distribution. The Add Distribution Report dialog box opens.

2 Enter ‘Defect Status’ in both the Name and Title fields.



5 Select Defects status by and select Product from the list. The following screenshot shows the settings for the Report On tab.


262


7 Select NonDetailReport.xslt option from the Stylesheet list.

8 Clear the Hide empty columns option.

9 Clear the Hide empty rows option. The following screenshot shows the settings for the Options tab.

10 Click Add.

Create a filter and a list report:

1 Choose Create > Filter > Defect. The Add Defect Filter dialog box opens.

2 Enter ‘RP Open Defects’ in both the Name and Description fields.

263




5 Select Status from the Restrict by list.

6 Select Prompt for restriction information at run time.

7 Select the following statuses from the list: Open, Open (Verify Failed), Open (Re-Opened), and Fixed. The following screenshot shows the completed dialog box.


264

8 Click OK. The following screenshot shows the Add Defect Filter dialog box after the restriction is added.

9 Click Add.

10 Choose Create > Report > List. The Add List Report dialog box opens.

11 Enter ‘Open Defects (by Date)’ in both the Name and Title fields.



14 Select Date found and click Add.

15 Select Number and click Add.

265


16 Select Summary and click Add. The following screenshot show the settings for the Report On tab.


18 Select NonDetailReport.xslt from the Stylesheet list.

19 Select RP Open Defects from the Filter list.


21 Select Date Found as the Primary Sort Column.


266

22 Select Number as the Secondary Sort Column. The following screenshot shows the settings for the Sorting tab.

23 Click Add.

24 Select the report in the Reports list window and click Preview. The Interactive Filter Wizard opens.

25 Clear the Fixed status. The following screenshot shows the completed dialog box.

26 Click Finish. The report opens.

267

Module 10: How to Manage the Audit Trail


Configure the project to maintain an audit trail

Search for audit trail records

Validate audit trail records

Create a report of the audit trail

Export audit trail records

By default TestTrack tracks the activities performed on a defect, test case, or test run. The audit trail provides a more granular look at individual changes made to field values and data.

How to Manage the Audit Trail

268

How to enable audit trail logging

Audit trail logging records track every change to a record so that you can trace the activities performed by users. This can be helpful for regulated industries or companies with compliance mandates.

Audit trail logging is not enabled by default because saving data on every change made to a record requires extra storage space. Audit trail records are not affected when items are deleted because they are maintained separately from the history log. The audit trail does not affect performance.

Use the following steps to configure the project to perform audit trail logging.


2 Select a record type in the Compliance category.

3 Select Enable detailed audit trail logging. Audit trail logging records the information that is modified when a record is added, edited, or deleted. This information is logged in an audit log change record and cannot be deleted. You can trace back to view a complete trail of when and how the data was modified.

4 Specify the data to log. Logging the changes only saves the fields or data that changed. Logging all the record data stores a complete copy of the data any time there is a change.

269


5 Click the Compliance category.

6 If the project is stored in a TestTrack native database select the number of audit trail rows that will be saved before the table is automatically archived.

7 Click OK.

Try it

Enable historical information logging and detailed audit trail logging for defects in the Acme Development project.

Answer:


2 Select Defects in the Compliance category.

3 Select Enable historical defect information logging.


270

4 Select Enable detailed audit trail logging for defect changes. The following screenshot shows the correct settings.

5 Click OK.

How to search for and view audit trail records

After you enable audit trail logging and users make changes to defects, test cases, or and test runs, you can search and review audit trail records.

Use the following steps to search for audit trail records.

1 Choose Tools > Administration > View Audit Trail. The Search Audit Trail dialog box opens.

2 Select the date range of records to view.

The date defaults to today’s date. You can enter another date or use the calendar to select one.

271


3 Select a Users option.

4 Select a Defects, Test Cases, Test Runs, Requirements, and Requirement Documents option.


272

5 Specify the sources used to modify the record.

6 Specify the type of modification.

273


7 Click Search. The View Audit Trail dialog box opens.

8 Select a record to view the details.

Try it

In the Acme Production project, make some changes and search for all the records from the beginning of the project.


274

Answer:

1 Choose Tools > Administration > View Audit Trail. The Search Audit Trail dialog box opens.

2 Clear the From option. The following screenshot shows the correct search criteria.

3 Click Search.

How to validate records and generate audit reports

You can validate audit trail data to make sure that it was not changed outside of TestTrack. You can also create a report of the data. Use the following steps to validate the records and create a report.

1 If you want to verify that audit trail records were not changed outside of TestTrack select the records you want to check and click Validate Records.

2 Click OK in the message box.

275


3 If you want to see more details on the audit trail records using a formatted report, select the records you want to include and click View Report.

4 If you want to export the records and work with them in another application, select the records you want to export and click Export Records. The Export Audit Trail dialog box opens.

5 Select a file location, enter a name, and click Save. A progress indicator opens and lets you know the file is being exported.

6 Click OK in the message dialog box.

7 Click Close in View Audit Trail dialog box.

Try it

Using the results from the last exercise, export the first two records to a file named ‘Renumber_Audit.’


276

Answer:

1 Select the first two records.

2 Click Export Records. The Export Audit Trail dialog box opens.

3 Enter ‘Renumber_Audit’ as the File name.

4 Select a location.

5 Click Save.

277

Reference: Email Templates

Email templates provide a way to control the text of notifications. In the following templates, text enclosed in square brackets indicates variable text pulled from the field in the brackets.

Email acknowledgement

Subject: Re: [Defect Summary]

Message body:

Welcome to the TestTrack technical support system.

This is an automated acknowledgement that we received your message on [Current Date].

Your link has been given Reference No. [Sequence/Reference Number]

Should you wish to check on the status of your issue, please refer to the Reference No.

If you don't receive an answer to your issue in the next few days, please realize we save all issues that we are unable to process in a timely manner, and plan to answer them as soon as time permits.

Thank you for your input.

-- Technical Support Group

[email protected]

Your original message...

[Original message]

--------------------------------------------------------------

Sent to you by TestTrack

Your Total Bug Tracking Solution

http://www.seapine.com

--------------------------------------------------------------

Email Templates

278

Defect assignment

Subject: [Defect Label] [Defect Number] has been assigned to you

Message body:

[Defect Label] [Defect Number] was assigned to you on [Current Date].

[Summary Label]: [Defect Summary]

[Type Label]: [Defect Type]

[Severity Label]: [Defect Severity]

[Priority Label]: [Defect Priority]

[Description Label]: [Defect Description]

-----------------------------------------------------------------------

This message was sent to you by TestTrack

-----------------------------------------------------------------------

279

Email Templates

Defect changed

Subject: [Defect Label] [Defect Number] has changed

Message body:

[Defect Label] [Defect Number] changed on [Current Date].






Change: [Changes to the defect]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

Email Templates

280

Defect added

Subject: [Defect Label] [Defect Number] was added to project

Message body:

[Defect Label] [Defect Number] was added to the project file on [Current Date].






-----------------------------------------------------------------------


-----------------------------------------------------------------------

Defects merged

Subject: [Defect Label] merged into #[Defect Number]

Message body:

[Changes to the defect]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

Defects renumbered

Subject: [Defects Label] were renumbered

Message body:

[Changes to the defect]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

281

Email Templates

Defect closed

Subject: [Defect Label] [Defect Number] has been closed

Message body:

[Defect Label] [Defect Number] was closed on [Current Date].


-----------------------------------------------------------------------


-----------------------------------------------------------------------

Test case assignment

Subject: [Test Case Label] [Test Case Number] has been assigned to you

Message body:

[Test Case Label] [Test Case Number] was assigned to you on [Current Date].

[Summary Label]: [Test Case Summary]

[Type Label]: [Test Case Type]

Automated Test: [Test Case is an Automated Test]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

Email Templates

282

Test case changed

Subject: [Test Case Label] [Test Case Number] has changed

Message body:

[Test Case Label] [Test Case Number] changed on [Current Date].




Change: [Changes to the test case]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

Test case added

Subject: [Test Case Label] [Test Case Number] was added to project

Message body:

[Test Case Label] [Test Case Number] was added to the project file on [Current Date].




----------------------------------------------------------------------


-----------------------------------------------------------------------

283

Email Templates

Test cases renumbered

Subject: [Test Cases Label] were renumbered

Message body:

[Changes to the test case]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

Test case closed

Subject: [Test Case Label] [Test Case Number] has been closed

Message body:

[Test Case Label] [Test Case Number] was closed on [Current Date].


-----------------------------------------------------------------------


-----------------------------------------------------------------------

Email Templates

284

Test run assignment

Subject: [Test Run Label] [Test Run Number] has been assigned to you

Message body:

[Test Run Label] [Test Run Number] was assigned to you on [Current Date].

[Summary Label]: [Test Run Summary]

[Type Label]: [Test Run Type]

Automated Test: [Test Run is an Automated Test]

[Test Run Label] Set: [Test Run Set]

[Test Variant Label]: [Test Variants]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

Test runs generated

Subject: [Test Runs Label] were added to the project

Message body:

[Test Runs Label] were generated on [Current Date].

[Changes to the test runs]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

285

Email Templates

Test run changed

Subject: [Test Run Label] [Test Run Number] has changed

Message body:

[Test Run Label] [Test Run Number] changed on [Current Date].


[Type Label]: [Test Run Type]

Automated Test: [Test Run is an Automated Test]

Change: [Changes to the test runs]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

Test run closed

Subject: [Test Run Label] [Test Run Number] has been closed

Message body:

[Test Run Label] [Test Run Number] was closed on [Current Date].


-----------------------------------------------------------------------


-----------------------------------------------------------------------

Email Templates

286

Requirement assignment

Subject: [Requirement Label] [Requirement Number] has been assigned to you

Message body:

[Requirement Label] [Requirement Number] was assigned to you on [Current Date].

[Type Label]: [Requirement Type]

[Importance Label]: [Requirement Importance]

[Requirement Document Label]: [Requirement Document List]

[Summary Label]: [Requirement Summary]

[Description Label]: [Description]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

287

Email Templates

Requirement changed

Subject: [Requirement Label] [Requirement Number] has changed

Message body:

[Requirement Label] [Requirement Number] was changed on [Current Date].






[Changes to the requirement]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

Email Templates

288

Requirement added

Subject: [Requirement Label] [Requirement Number] was added to project

Message body:

[Requirement Label] [Requirement Number] was added to project [Project Name] on [Current Date].






-----------------------------------------------------------------------


-----------------------------------------------------------------------

Requirement renumbered

Subject: [Requirements Label] were renumbered

Message body:

[Changes]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

289

Email Templates

Requirement closed

Subject: [Requirement Label] [Requirement Number] has been closed

Message body:

[Requirement Label] [Requirement Number] was closed on [Current Date].


-----------------------------------------------------------------------


-----------------------------------------------------------------------

Requirement email review request

Subject: [Requirement Label] review requested

Message body:

You have been requested to review [Requirement Label] [Requirement Number].






-----------------------------------------------------------------------


-----------------------------------------------------------------------

Email Templates

290

Requirement tracked email received

Subject: [Requirement Label] [Requirement Number] received an email

Message body:


-----------------------------------------------------------------------


-----------------------------------------------------------------------

Requirement list

Subject: [Requirement Number]

Message body:

[Tag Number] [Requirement Summary], [Requirement Status]

Link changed

Subject: Link has changed

Message body:


-----------------------------------------------------------------------


-----------------------------------------------------------------------

Link made suspect

Subject: Link made [Suspect Label]

Message body:


-----------------------------------------------------------------------


-----------------------------------------------------------------------

291

Email Templates

Requirement question or comment

Subject: Regarding [Requirement Label] [Requirement Number] in [Project Name]

Message body:

-----------------------------------------------------------------------

[Requirement Label] [Requirement Number] in project [Project Name]






-----------------------------------------------------------------------


-----------------------------------------------------------------------

Email Templates

292

Requirement document assignment

Subject: [Requirement Document Label] [Requirement Document Number] has been assigned to you

Message body:

[Requirement Document Label] [Requirement Document Number] was assigned to you on [Current Date].

[Name Label]: [Requirement Document Name]


-----------------------------------------------------------------------


-----------------------------------------------------------------------

Requirement document changed

Subject: [Requirement Document Label] [Requirement Document Number] has changed

Message body:

[Requirement Label] [Requirement Number] was changed [Current Date].



[Changes]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

293

Email Templates

Requirement document added

Subject: [Requirement Document Label] [Requirement Document Number] was added to project

Message body:

[Requirement Document Label] [Requirement Document Number] was added to project [Project Name] on [Current Date].



-----------------------------------------------------------------------


-----------------------------------------------------------------------

Requirement documents renumbered

Subject: [Requirement Documents Label] were renumbered

Message body:

[Changes]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

Requirement document closed

Subject: [Requirement Document Label] [Requirement Document Number] has been closed

Message body:

[Requirement Document Label] [Requirement Document Number] was closed on [Current Date].


[Status Label]: [Requirement Document Status]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

Email Templates

294

Requirement document email review request

Subject: [Requirement Document Label] review requested

Message body:

You have been requested to review [Requirement Document Label] [Requirement Document Number].



[Changes]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

Requirement document tracked email received

Subject: [Requirement Document Label] [Requirement Document Number] received an email

Message body:

[Changes]

-----------------------------------------------------------------------


-----------------------------------------------------------------------

Requirement document list

Subject: [Requirement Document Number]

Message body:

[Requirement Document Number] [Requirement Document Name], [Requirement Document Status]

295

Email Templates

Requirement document question or comment

Subject: Regarding [Requirement Document Label] [Requirement Document Number] in [Project Name]

Message body:

-----------------------------------------------------------------------

[Requirement Document Label] [Requirement Document Number] in project [Project Name]



-----------------------------------------------------------------------


-----------------------------------------------------------------------

Email Templates

296

297

Glossary

Active Directory: Microsoft’s directory service that automates network management of user data, security, and distributed resources.

Assignment: Associating a user or customer with a record and designating that person as the one responsible for taking action on it.

Audit trail: Audit trail logging records the information that is modified when a defect, test case, or test run is added, edited, or deleted. This information is logged in an audit log change record and cannot be deleted. Audit trail records are not affected when defects, test cases, and test runs are deleted because they are maintained separately from the history log.

Customer: Use customers to make a tracking distinction within a project. A customer can be a person outside your organization or an individual within your organization who is tracked separately in a TestTrack project. For example, in a software development company, customers are individuals outside the organization who use the product. However, if you are using TestTrack to administer an internal help desk, users are the help desk employees, and customers are the other employees in your company who might submit help desk tickets.

Crosstab report: Crosstab reports summarize data and display the results in a two-dimensional grid.

EOL: End-of-line mark, a special character or sequence of characters that marks the end of a line.

Escalation: An action performed on a record as the result of a period of inactivity.

Events: Actions that users can perform for each state in a workflow such as Assign or Fix. Actions are listed in the Activities menu.

Glossary

298

Floating license: A license that can be shared by more than one user.

Global user or customer: A user or customer who has a username and password stored in the Seapine License Server. A global user can log in to TestTrack.

Historical information logging: A record of history stored with the defects, test cases, and test runs.

LDAP: Lightweight Directory Access Protocol. Protocol that allows you to define users once and share them across multiple computers and applications.

List values: The options in a pop-up menu

Local user or customer: A user or customer who is defined within a single project. A local user/customer canNOT log in to TestTrack or work with projects. They are used strictly for tracking purposes.

Named license: A license assigned to a specific username that cannot be used by anyone else.

Notification: An email sent to a user as the result of a change to a record.

Pop-up menu: A drop-down list in TestTrack.

SOAP (Simple Object Access Protocol): A protocol that uses Hypertext Transfer Protocol (HTTP) and Extensible Markup Language (XML) to allow applications to interact and exchange information. TestTrack includes a SOAP-based SDK that can be used to customize TestTrack or integrate it with other applications.

SoloBug: A standalone bug reporting application that allows users and customers to submit defects via email.

SoloSubmit: A TestTrack add-on that allows users and customers to submit bug reports and feature requests to a TestTrack project using a Web browser.

State: A step or decision point in the workflow.

Transitions: The relationship between states and events. Transitions enforce the workflow by enabling event menu items and toolbar buttons based on the current state of the record.

Trigger: An action performed on a record as the result of a change.

TestTrack Pro Web client: A browser-based version of TestTrack Pro.

User: A person within your organization who is tracked in a TestTrack project.

XML: Extensible Markup Language is a flexible way to create common information formats and share both the format and the data on the Web, intranets, and between applications.

Date post:	04-Mar-2015
Category:	Documents
Upload:	stefanrott
View:	396 times
Download:	0 times