Ttuserguide

TestTrack
UserGuide
Version 2012
Copyrights
2012 Seapine Software, Inc. All rights reserved.
QA Wizard Pro, Seapine CM, SoloBug, SoloSubmit, Surround SCM, and TestTrack are trademarks or registered trademarks of Seapine Software, Inc. in the United States and other countries. Borland and StarTeam are trademarks or registered trademarks of Borland, Inc. in the United States and other countries. Delphi and JBuilder are trademarks or registered trademarks of Embarcadero Technologies, Inc. in the United States and other countries. Acrobat Reader is a registered trademark of Adobe, Inc. in the United States and other countries. Sun, JVM, Java, JavaScript, and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. Apple, Mac, Mac OS, Macintosh, Objective-C, and Safari are registered trademarks of Apple Computer, Inc. Microsoft, Windows, Windows NT, Windows Server, Windows Vista, MS Windows, Active Directory, Internet Explorer, Outlook, SQL Server, Visual SourceSafe, and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Linux is a trademark of Linus Torvalds. Red Hat, Red Hat Enterprise Linux, and Fedora are registered trademarks of Red Hat, Inc. in the United States and other countries. SUSE is a registered trademark of Novell Inc. in the United States and other countries. Debian is a registered trademark of Software in the Public Interest, Inc. Ubuntu is a registered trademark of Canonical Ltd. IBM, ClearCase, and all other IBM brand and product names are service marks, trademarks or registered trademarks of IBM Corporation or its subsidiaries in the United States and other countries. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. PVCS, Serena PVCS Professional Suite, and Serena PVCS Version Manager are registered trademarks of Serena Software, Inc. All other product names mentioned herein are the trademarks of their respective owners. All other trademarks are the property of their respective owners. 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. Your license agreement with Seapine Software, Inc., which is included with the product, specifies the permitted and prohibited uses of the product. Any unauthorized duplication or use of this software, in whole or in part, in print, or in any other storage and retrieval system is forbidden. Information in this document is subject to change without notice and does not represent a commitment on the part of Seapine Software, Inc. Unless otherwise noted, all companies, products, street addresses, and persons contained herein are purely fictitious. Mention of third-party companies and products is for informational purposes only and does not constitute an endorsement.
Seapine Software, Inc. 5412 Courseview Drive, Suite 200 Mason, OH 45040 (513) 754-1655 [email protected]
Contents
Welcome to TestTrack What's New Getting Started
Before you start Starting TestTrack Switching projects Connecting to a different server Starting the TestTrack Server Connecting to the TestTrack Server Logging out
1 3 5
5 5 6 6 7 7 9
Navigating TestTrack
About the TestTrack interface Using the Overview tab Using the Address bar Opening items using ttstudio addresses Entering ttstudio addresses Customizing toolbars Changing the user interface mode
11
11 12 13 14 14 16 16
Learning the Basics

TestTrack Items Using List Windows Creating User-Defined Views Using Filters Using interactive filters Viewing filters Adding Tabs Using the Workbook Finding Records Going directly to a record Using quick find Using advanced find Finding users and customers Viewing Workflow Event History Viewing workflow event details
19
19 21 28 29 30 31 32 33 34 36 36 38 39 41 41
Editing workflow event details Deleting workflow events from items Viewing item workflow history diagrams Viewing work items Viewing Item History Viewing change reports Creating User Notification Rules Formatting Multi-Line Text Fields Using spell check Inserting stamps Attaching Files Capturing Screenshots Organizing Data with Folders Using the Folders list window Adding folders Adding items to folders Moving items to folders Viewing folders Viewing items in folders Editing folders Editing items in folders Ranking items in folders Removing items from folders Deleting folders Generating Reports Generating built-in reports Generating external reports Viewing Live Charts Emailing from TestTrack Adding email recipients Viewing tracked email Replying to tracked email Deleting tracked email
42 42 43 44 44 45 46 49 52 53 54 55 56 58 61 66 66 67 68 68 68 69 69 70 70 70 70 71 73 74 75 76 76
Using Advanced Features

Linking Items
77
77
ii
Adding links Adding items to links Diagramming links Viewing links Editing links Deleting links Marking Items as Suspect Investigating suspect dependencies Clearing suspect items Updating Multiple Items Changing bulk fields Changing test variant values Importing and Exporting Data Exporting to XML Importing XML files Exporting to text files Creating text file export templates Importing text files Creating text file import templates Creating Filters Adding Filters Adding Restrictions Editing filters Inserting restrictions Duplicating filters Deleting restrictions Deleting filters Creating Reports Report types Creating built-in reports Charting report data Adding external reports to TestTrack Creating live charts Viewing report settings Editing reports
77 78 79 80 81 81 82 83 84 84 85 86 89 90 92 93 95 95 97 97 97 99 117 118 118 118 118 119 119 122 139 142 143 151 151
iii
Duplicating reports Deleting reports Creating text file report templates Saving list window reports as text files Creating RSS Feeds Accessing RSS feeds Managing Orphaned Email
152 152 152 152 153 154 155
Using TestTrack Pro

Adding Issues Adding additional issue reports Working with Issues About the default issue tracking workflow Viewing issue workflow history Managing Issue Links Managing Issue Folders Managing Issue Email Viewing Issues Editing Issues Editing additional issue reports Duplicating issues Merging issues Assigning issue numbers Renumbering issues Deleting additional issue reports Deleting issues Creating Test Cases From Issues Creating Requirements From Issues Managing Test Configs Adding test configs Viewing test configs Editing test configs Duplicating test configs Deleting test configs Creating Release Notes Building release notes
159
159 163 163 163 169 170 171 171 172 172 173 173 174 174 174 175 175 175 176 177 177 178 178 178 178 178 179
iv
Using TestTrack RM
About default requirement types Adding Requirement Documents Adding Requirements Using the Specification Document Window Customizing the Specification Document window About requirement and requirement document indicators Using Document View Using Review Mode View Modifying Requirement Documents Adding Requirements to Requirement Documents Editing Requirements in the Specification Document Window Moving Requirements between Requirement Documents Removing Requirements from Documents Unsharing Requirements Viewing Requirements Viewing Related Requirement Documents Editing Requirements Duplicating requirements Changing requirement types Assigning requirement numbers Renumbering requirements Deleting requirements Working with Requirements About the default requirements workflow Viewing requirement workflow history Working with Requirement Documents About the default requirement documents workflow Viewing requirement document workflow history Locking Requirements and Requirement Documents Reviewing Requirements and Requirement Documents Adding requirement document review notes Adding requirement review notes Editing review notes Viewing Requirement Documents
181
181 181 183 186 186 188 188 190 191 192 195 196 196 196 197 197 198 199 200 200 200 201 201 202 210 211 211 219 220 221 222 223 224 225
Editing Requirement Documents Duplicating requirement documents Assigning requirement document numbers Renumbering requirement documents Deleting requirement documents Managing Requirement and Requirement Document Email Managing Requirement and Requirement Document Folders Creating Requirement Document Snapshots Viewing Requirement Document Snapshots Viewing Requirement Document Differences Viewing all requirement document differences Viewing Historical Requirement Versions Rolling back requirements Viewing Requirement Differences Managing Requirement Document Links Managing Requirement Links Generating Test Cases from Requirements Creating Issues from Requirements Viewing Requirement Relationships Performing Impact Analysis About change impact analysis Using the Traceability Matrix About the traceability matrix Exporting the traceability matrix to Microsoft Excel Importing Requirement Documents from Microsoft Word Exporting Requirement Documents to Microsoft Word and Adobe PDF Format
225 226 228 228 229 229 230 230 231 233 234 236 237 238 239 240 241 243 244 244 245 246 247 248 249 253
Using TestTrack TCM

Adding Test Cases Entering test case details Entering test case steps Managing Test Variants Managing Included Test Variants Managing Excluded Test Variants Working with Test Cases About the default test cases workflow
255
255 256 257 266 267 269 271 271
vi
Viewing test case workflow history Creating Test Run Sets Generating Test Runs Regenerating Test Runs Viewing Test Runs Running Tests Managing run-time test variants Working with Test Runs About the default test runs workflow Viewing test run workflow history Entering Overall Test Run Results Creating Issues From Test Runs Viewing Test Run Status Managing Automated Tests Creating scripts from test cases Attaching automated tests to test cases Running automated tests from test runs Checking automated test status Viewing automated test results Attaching automated test results to test runs Managing Test Run Links Editing Test Runs Duplicating test runs Deleting test runs Managing Test Case and Test Run Folders Managing Test Case and Test Run Email Managing Test Case Links Viewing Test Cases Editing Test Cases Duplicating test cases Assigning test case numbers Renumbering test cases Deleting test cases
278 279 280 282 284 284 290 292 292 296 297 299 300 302 303 305 308 311 312 313 313 314 315 316 317 317 318 319 319 320 321 321 322
Managing Security
Managing Security Groups
323
323
vii
Adding security groups Viewing security groups Editing security groups Creating security group comparison reports Hiding fields Duplicating security groups Deleting security groups Managing Users and Customers Adding users Adding customers Retrieving global users Retrieving global customers Promoting users Promoting customers Viewing users Viewing customers Editing users Editing customers Duplicating users Duplicating customers Inactivating users Inactivating customers Making a user a customer Making a customer a user Deleting users Deleting customers
324 326 326 327 329 330 330 330 330 333 336 337 337 338 339 339 339 339 340 340 340 341 341 341 341 342
Configuring TestTrack
Setting Local Options Setting general local options Setting stylesheet options Setting local help and browser paths Setting view file options Setting formatting options Setting live chart options Setting TestTrack TCM options
343
343 343 344 344 345 346 346 347
viii
Setting User Options Setting general user options Setting display options Setting list window view options Setting dictionary options Setting spell check options Changing your password Locking Projects Viewing logged in users Logging out users Configuring Projects Setting general project options Setting client options Setting file attachment options Setting email options Setting hyperlink options Setting issue options Setting test case options Setting test run options Setting requirement options Setting requirement document options Setting compliance options Setting field options Setting time tracking options Setting report options Setting dictionary options Customizing Fields Modifying Value Lists Configuring Requirement Types Configuring Custom Fields Configuring Calculated Custom Fields Defining Required Fields and Default Values Configuring Field Relationships Renaming Field Labels Configuring Folder Types
347 347 348 351 351 353 353 354 354 354 355 355 356 358 359 360 361 366 366 367 368 368 373 375 377 378 379 379 381 384 390 406 407 409 411
ix
Adding folder types Editing folder types Inactivating folder types Deleting folder types Customizing Workflows Configuring Workflow States Configuring Workflow Events Configuring Workflow Transitions Configuring Workflow Assignment Rules Evaluating the Workflow Diagramming the Workflow Overriding the Workflow Resetting the Workflow Configuring Time Tracking Default time tracking fields Configuring Automation Rules Running Executables from Automation Rules Configuring System Notification Rules Configuring Triggers About triggers Configuring Escalation Rules Configuring Automation Rule Actions Viewing the Automation Rules Log Configuring Item Mapping Rules Default item mapping rules Adding item mapping rules Editing item mapping rules Exporting item mapping rules Importing item mapping rules Customizing Email Templates Adding email templates Using field codes in email templates Viewing email templates Editing email templates Deleting email templates
412 413 413 414 414 415 417 423 424 426 427 428 428 429 433 436 437 438 441 442 448 453 458 460 462 464 465 465 466 466 467 469 470 470 470
Configuring Link Definitions Configuring Notification Hyperlinks Managing Controlled Email Notification Hyperlinks Managing Auditable Processes Entering Electronic Signatures Managing Audit Trails Deleting Historical Log Information
470 475 476 477 477 477 482
Configuring SoloBug
Distributing SoloBug Customizing SoloBug Automatically importing SoloBug files Manually importing SoloBug files
483
483 483 485 485
Configuring SoloSubmit
Installing SoloSubmit Enabling SoloSubmit Customizing SoloSubmit Turning Off SoloSubmit Cookies SoloSubmit Field Codes SoloSubmit User Field Codes
487
487 487 489 491 492 493
Integrating with Source Control Tools

Configuring SCC Integration Working with Source Code Files Disabling SCC Integration
495
495 499 512
Using the Outlook Add-in

Configuring the Outlook add-in settings Accessing TestTrack projects from Outlook Creating items from Outlook emails Attaching Outlook emails to items
513
513 513 514 514
Appendix A: Third-Party Development Tool Integrations Appendix B: Environment Variables

Issue environment variables Requirement environment variables Requirement document environment variables Test case environment variables Test run environment variables
515 517
517 519 521 522 524
xi
Custom field environment variables Workflow event environment variables File attachment environment variables Source file attachment environment variables
526 526 526 527
Appendix C: Field Codes

Issue field codes Requirement document field codes Requirement field codes Test case field codes Test run field codes Label field codes Custom field codes
529
529 532 533 535 537 540 550
Appendix D: Report Stylesheets

Customizing stylesheets Refreshing stylesheet menus Detail report stylesheets Distribution report stylesheets List report stylesheets Release planning report stylesheets Release status report stylesheets Time tracking report stylesheets Traceability report stylesheets Trend report stylesheets List window report stylesheets
551
551 551 552 556 557 557 558 560 561 562 562
Appendix E: Security Commands

General Administration Issues Issue events Requirements Requirement events Requirement Documents Requirement document events Test Cases Test case events
565
565 566 571 575 576 583 584 592 593 600
xii
Test Runs Test run events Folders Links Customers Users Security Groups Test Configurations Filters Reports Workbook
600 606 607 609 609 610 612 613 613 615 616
Appendix F: Calculated Custom Field Functions

Date functions DateTime functions Item functions Item.Events functions Item.ReportedBy functions Math functions String functions Global functions
619
619 619 620 620 621 622 624 624
Appendix G: Fields Affected by Administrative Changes Index
627 629
xiii
Welcome to TestTrack
This guide provides information for using and administering TestTrack, including TestTrack Pro, TestTrack RM, and TestTrack TCM.
Users
Getting Started - learn how to start TestTrack and connect to a TestTrack Server. Navigating TestTrack - learn about the interface and different ways to navigate TestTrack. Learning the Basics - learn more about basic features, including how to use list windows, organize and find data, and generate reports. Using Advanced Features - learn more about advanced features, including how to import and export data, create filters and reports, link items, and create RSS feeds. Using TestTrack Pro - learn how to manage and work with issues and other issues. Using TestTrack RM - learn how to manage and work with requirements and requirement documents. Using TestTrack TCM - learn how to manage and work with test cases and test runs. Integrating with Source Control Tools - learn how to integrate with supported version control tools. Third-Party Development Tool Integrations - learn how to install the TestTrack add-in and integrate with IDEs.
Administrators
Managing Security - learn how to create security groups and manage users. Configuring TestTrack - learn how to set local and user options and configure project options. Configuring SoloBug - learn how to customize and distribute SoloBug to your customers. Configuring SoloSubmit - learn how to enable and customize SoloSubmit.
What's New
TestTrack 2012 includes the following key features. For a complete list of features, enhancements, and bug fixes, go to www.seapine.com/ttreleasenotes.html. Create draft custom fields Administrators can now create draft custom fields to add new fields without locking the TestTrack database. You can copy existing custom fields and configure them as drafts without affecting current items. When you finish customizing draft fields, you can make them active or replace an existing field in the project. See Creating draft custom fields, page 387. Configure custom fields that calculate values You can now configure custom fields to automatically calculate numeric, text, date/time, list item, and time span values based on other field values. For example, you can create a field that calculates the difference between the created date and the current date to see how long an item is open or a field that calculates the risk score based on severity and likelihood of an issue occurring. See Configuring Calculated Custom Fields, page 390. Set default field values Administrators can now enter formatted multi-line text and choose more date/time options when setting default values for text, numeric, and date fields. For example, you may want to set default field values to provide a template to guide QA team members when entering issue descriptions or specify a default due date that is a specific number of days from the current date. See Defining Required Fields and Default Values, page 406. Other enhancements TestTrack 2012 also includes the following enhancements:
n
SQLite native backend databaseTestTrack now uses SQLite for the native backend database. ExistingTestTracknative databases are automatically upgraded to the new native format. Refer to the TestTrack Upgrade Guide (http://downloads.seapine.com/pub/docs/ttupgradeguide.pdf) for information. IMAP supportYou can now use the IMAP protocol for tracked email and importing issues from email. Electronic signature reportingElectronic signatures entered when making changes in TestTrack 2012 are now displayed in history change reports, audit trail detail reports, audit trail record exports, and when viewing the audit trail log. Parent/child linking of duplicated itemsYou can now use a parent/child link definition to link duplicated and original items. Additional Surround SCM integration optionsTestTrack now includes more options for getting, checking out, and checking in Surround SCM files, such as using changelists and setting Surround SCM workflow options.
TestTrack Pro
Defect terminology change
Wh at 's N e w
'Defect' is now named 'issue' by default in new TestTrack Pro projects to provide flexibility for managing multiple item types. Administrators who want to continue using 'defect' in new projects can change the field labels. See Renaming Field Labels, page 409.
TestTrack RM
Export the traceability matrix to Microsoft Excel You can export the traceability matrix to an Excel file to share data with users outside of TestTrack or manage the data in Excel. See Exporting the traceability matrix to Microsoft Excel, page 248. Export additional requirement document data to Microsoft Word The default Microsoft Word templates for exporting requirement documents now include the requirement document description, snapshot version, requirement document workflow state, and snapshot history. See Exporting Requirement Documents to Microsoft Word and Adobe PDF Format, page 253.
TestTrack TCM
QA Wizard Pro integration enhancements When TestTrack TCM is integrated with QA Wizard Pro, you can save time and create more thorough test cases by recording steps instead of manually entering them. You can also use existing manual test cases to create QA Wizard Pro scripts, which ensures your automated tests have the same steps as the manual tests. See Recording test case steps with QA Wizard Pro, page 262 and Creating scripts from test cases, page 303.
Getting Started
In just a few minutes, you will learn about starting TestTrack, connecting to the TestTrack Server, and selecting projects.
Before you start

If you are just getting started with TestTrack, your TestTrack administrator or another high-level user should provide you with the following information:
n
TestTrack username and password Your username and password may be the same as your network credentials if your organization uses single sign-on.
TestTrack Server connection information You need to add a server connection to access each server that TestTrack projects are stored on. See Adding a server connection, page 8.
Note: If you need to install, refer to the TestTrack Installation Guide for more information.
Starting TestTrack
1. WindowsChoose Programs > Seapine Software > TestTrack > TestTrack Client. MacDouble-click the TestTrack Client icon in the Applications/TestTrack folder. LinuxEnter /usr/bin/ttclient The TestTrack Login dialog box opens. 2. Select the Server you want to connect to. See Connecting to the TestTrack Server, page 7 if you need to add a server. 3. Enter your Username and Password or select Use single sign-on to log in with your network credentials. Note: Single sign-on is only available for Windows and Mac. 4. Optionally expand the Licenses area to select the products you want to log in to. All TestTrack products you have access to are selected by default. If you use floating licenses, you may want to only log in to the products you will use for the current session. 5. Select Always login with this username and password to automatically log in with the username and password you entered when TestTrack starts. 6. Click Connect. The TestTrack Project Selection dialog box opens. 7. Select a Project. Some projects take a longer time to load. Click Refresh if the project you want to use is not listed.
S wit ch in g p r oje ct s
8. Select Always login to this project to automatically log in to the selected project when TestTrack starts. This option is only available if Always login with this username and password is selected in the TestTrack Login dialog box. 9. Click OK. You are logged in and ready to start using TestTrack. Note: If there is a problem connecting to the TestTrack Server, ask your administrator to make sure the server is started. See Starting the TestTrack Server, page 7.
Switching projects
If you are logged into TestTrack, you can quickly switch to another project on the same server. 1. Choose File > Switch Project. The Switch Project dialog box opens.
2. Select a project. Some projects take a longer time to load. Click Refresh if the project you want to use is not listed. 3. Optionally expand the Licenses area to select the products you want to log in to. All TestTrack products you have access to are selected by default. If you use floating licenses, you may want to only log in to the products you will use for the current session. 4. Click Switch. The selected project opens.
Connecting to a different server

If you need to switch to a project on a different server, you can connect to another server without quitting and restarting TestTrack. 1. Choose File > Connect to Server. You are prompted to close the open project.
S t ar t in g t h e Te st Tr ack S e r ve r
2. Click Yes. The TestTrack Studio Login dialog box opens. 3. Enter the login information and click Connect. You are now logged in to the project.
Starting the TestTrack Server

If there is a problem connecting to the server, check the following and try reconnecting:
n n n n
Make sure the server computer is running Make sure the Seapine License Server is running Check the IP address and port number Make sure you are connected to the network, intranet, or Internet
Windows
1. If the TestTrack Server is installed as an application, choose Programs > Seapine Software > TestTrack > TestTrack Server on the Start menu. If the server is installed as a Windows service, it starts automatically. If it does not start, refer to the Windows documentation for information about starting services. Note: When the TestTrack Server is running, an icon is displayed in the status area on the server computer taskbar. If the icon is yellow or red, the TestTrack Server is not running properly. When the TestTrack Server compacts a project, it can take several minutes for the TestTrack Server icon to turn green.
Linux
1. Enter /usr/bin/ttstudio start to start the TestTrack Server.
Mac
1. Start the System Preferences and click TestTrack. 2. Click the lock to make changes. Make sure the TestTrack Server is started. Select Start TestTrack Server when this computer starts up to automatically start the server. 3. Click Save.
Connecting to the TestTrack Server

TestTrack projects are located on servers, which you need to set up access to. A list of all the servers you added is displayed in the Setup Server Connections dialog box. 1. Choose File > Connect to Server. 2. Click Setup.
Con n e ct in g t o t h e Te st Tr ack S e r ve r
The Setup Server Connections dialog box opens.
3. Select a server and click Top, Move Up, Move Down, or Bottom to reorder the list. When you log in, TestTrack Servers are displayed in the same order. You may want to move the servers you access most frequently to the top of the list. 4. Click Add to create a server connection. See Adding a server connection, page 8. 5. Select a server and click Edit to change the server address or port number. See Editing a server connection, page 9. 6. Select a server and click Delete to delete the connection. See Deleting a server connection, page 9.
Adding a server connection

You need to add a server connection to access each server that TestTrack projects are stored on. Tip: Your TestTrack administrator can provide the TestTrack Server address and port number. 1. Choose File > Connect to Server. 2. Click Setup. The Setup Server Connections dialog box opens. 3. Click Add. The Add TestTrack Server dialog box opens.
4. Enter a Server Name and Server Address. Use a descriptive name to help identify the server. 5. Enter the Port number.
Loggin g ou t
TestTrack clients connect to the server on this port via TCP/IP. Valid values are 1-65535. 6. Click OK. The server connection is added and you return to the Setup Server Connections dialog box. 7. To change the order of the servers, select a server and click Top, Move Up, Move Down, or Bottom. Servers are listed in the specified order in the TestTrack Login dialog box. 8. Click Close to close the Setup Server Connections dialog box.
Editing a server connection

You can edit a server connection to change the address or port number. If you want to change the server name, create a new server connection. 1. Choose File > Connect to Server. 2. Click Setup. The Setup Server Connections dialog box opens. 3. Select the server and click Edit. 4. Make any changes and click OK.
Deleting a server connection

1. Choose File > Connect to Server. 2. Click Setup. The Setup Server Connections dialog box opens. 3. Select the server and click Delete. You are prompted to confirm the deletion. 4. Click Yes. The server is deleted.
Logging out
Log out of TestTrack when you finish working with a project. This is important if you use a floating license because the license does not become available until you log out. 1. Choose File > Logout and Disconnect. You are prompted to confirm that you want to log out. 2. Click Yes. You are logged out from the project and disconnected from the server. Note: Choose File > Exit to close the application.
Navigating TestTrack
TestTrack is easy to use but it is even easier when you understand the basics and learn a few shortcuts. Take a few minutes to learn about the interface before you start using TestTrack.
About the TestTrack interface

TestTrack includes standard interface elements, such as a title bar, menus, and toolbars. Features, such as the title bar, menus, and command buttons, are common to all list windows. Some features and options, such as active menus and commands, vary based on the list window and your security permissions. Tip: TestTrack also includes context, or right-click, menus. For example, if you right-click an item in a list window, a menu with the available commands opens.
Toolbars
TestTrack toolbars provide access to commonly used TestTrack commands and list windows. If a toolbar button is unavailable, you do not have access to that command or the command is not available for the list window. See Customizing toolbars, page 16.
Address bar
The Address bar displays an address for the open list window or item. See Using the Address bar, page 13.
11
U sin g t h e Ove r vie w t ab
Tabs
Instead of opening and switching between list windows, you can use tabs to manage multiple instances of the same list window. See Adding Tabs, page 32.
Column filters
Use column filters when you do not want to create a filter, but want to limit the records displayed in a list window by column values. See Filtering list window columns, page 24.
List windows
List windows organize information and display records. See Using List Windows, page 21.
Quick find toolbar

Use quick find to quickly find records in a list window. See Using quick find, page 36.
Workflow events toolbar

The workflow events toolbar provides one-click access to workflow events. These are the same commands that you access from the Activities menu.
Using the Overview tab

The Overview tab includes a read-only summary of an item's activities, its workflow events, and emails. This tab provides a convenient place to quickly review the history of an item. Note: If the tab is not displayed, you can enable it in the user options. See Setting display options, page 348. 1. Click the Overview tab when you are viewing or editing a record, such as an issue. The overview information is displayed.
12
U sin g t h e Ad d r e ss b ar
Note: If you are viewing an issue, click the Change overview orientation button to toggle the orientation of the panes from horizontal to vertical. 2. Click the links in the Workflow Events and Emails rows to view more detail about individual activities and events. 3. Click OK when you are finished.
Using the Address bar

The Address bar displays an address for the current list window or open item. You can copy and paste the address to share it with other users. For example, you can paste a specific records address in an email so the user can click the hyperlink to go directly to the record. You can also enter an address in the Address bar to open an item. The Address bar can display ttstudio or http addresses.
n
Ttstudio addresses are generally used to open items in the TestTrack Client. If the TestTrack Client is not installed, the item is opened in TestTrack Web. The TestTrack URL Redirector must be installed on the client computer to open ttstudio addresses with TestTrack Web. Http addresses always open items in TestTrack Web.
1. Choose View > Window Toolbars > Address. The Address bar opens. The address for the current list window or open item is displayed. 2. To open a list window or item, enter the address. See Entering ttstudio addresses, page 14. You can also enter addresses that begin with http://, https:// or www. to open web pages in a browser. Note: You can also enter sscm addresses to open a repository or file in Surround SCM. 3. Click Go. The item is opened.
13
Op e n in g it e ms u sin g t t st u d io ad d r e sse s
Opening items using ttstudio addresses

You can use ttstudio addresses to open specific records or to open list windows. You can enter an address or copy and paste an address provided by another user. Note: You can also enter ttstudio addresses in the Address bar. See Using the Address bar, page 13. 1. Choose File > Go To Location. The Go To Location dialog box opens. The Address includes the TestTrack Server address, port, and project you are currently logged in to.
2. Select the Type of item you want to access. The address changes based on the record type. 3. Enter the Address. See Entering ttstudio addresses, page 14. 4. Click OK. The list window or item opens.
Entering ttstudio addresses

You can use ttstudio addresses to open a list window or specific item, such as an issue. See Using the Address bar, page 13. Addresses must use the following formats:
n n
To open a list windowttstudio://ServerAddress:Port//ProjectName/ItemType To open a specific item ttstudio://ServerAddress:Port//ProjectName/ItemType?Parameter&Parameter
Note: The TestTrack Server address and port, project name, and item type are required. For example, Joe wants to open the Issues list window in the WysiChart project. He uses the following address: ttstudio://server.wysicorp.com:99//WysiChart/dfct If you are not logged into TestTrack, the login dialog box opens when you enter the address. You can include your username and password in the address to automatically log in. For example, ttstudio://username:[email protected]:99//Wysi/dfct. Parameters are used to open a specific item. When you select an item in TestTrack, the ttstudio address displayed in the Address bar includes the recordID parameter, which identifies the record number in the TestTrack project database. Following are the item type and parameter values that can be used with ttstudio addresses:
14
En t e r in g t t st u d io ad d r e sse s
To open a specific: Customer
Use an item type parameter: cust
Use the specific item parameter: username (global customers only) recordID
Example cust?username=bobuser
cust?recordID=47 dfct?number=1 dfct?recordID=47 dfct?recordID=47&historyID=46 dflt?name=High%20Priority dflt?recordID=47 fold?path=Public%20Backlog fold?recordID=47 fold?recordID=47&historyID=44 rprt?name=Open Issues rprt?recordID=47 rqmt?number=1 rqmt?recordID=47 rqmt?recordID=47&historyID=46 rdmt?name=Wysi%20Doc rdmt?recordID=47 rdmt?recordID=47&historyID=46 ugrp?name=Administration ugrp?recordID=47 spec?number=1 spec?recordID=47 task?summary=Add%20report task?recordID=47
Issue
dfct
number recordID historyID
Filter
dflt
name recordID
Folder
fold
path recordID historyID
Report
rprt
name recordID
Requirement
rqmt
Requirement document
rdmt
name recordID historyID
Security group Specification document Task
ugrp
name recordID
spec
number recordID
task
summary recordID
15
Cu st omiz in g t ool b ar s
To open a specific: Test case
Use an item type parameter: tstc
Use the specific item parameter: number recordID historyID
Example tstc?number=1 tstc?recordID=47 tstc?recordID=47&historyID=46 scfg?name=Windows scfg?recordID=47 tstr?number=1 tstr?recordID=47 tstr?recordID=47&historyID=46 user?username=janeuser
Test config
scfg
name recordID
Test run
tstr
User
user
username (global users only) recordID
user?recordID=47
Note: If a parameter value includes spaces or special characters, such as hyphens, you must replace them with escape characters so TestTrack can resolve the address. For example, use %20 to escape a space. Standard URL escape characters are supported.
Customizing toolbars
Toolbars provide access to most TestTrack commands. You can display or hide toolbars and change their appearance. 1. To display a toolbar, choose View > Toolbars and select the toolbar to display. To hide a toolbar, choose View > Toolbars and select the toolbar to hide. 2. To change the toolbar buttons, choose View > Toolbars and select a display option.
n n n
Icon/TextDisplays icons and text on toolbar buttons IconDisplays icons on toolbar buttons TextDisplays text on toolbar buttons
3. To reduce the toolbar icon size, choose View > Toolbars > Use Small Size.
Changing the user interface mode

TestTrack can run in MDI or SDI mode. We recommend using the default mode for your operating system. 1. Choose View > User Interface Mode and select an option.
16
Ch an gin g t h e u se r in t e r face mod e
Select MDI to display multiple windows in one parent window. This is the default mode for Windows and Linux. Select SDI to display multiple windows individually. This is the default mode for Mac OS X.
17
Learning the Basics

TestTrack includes a core set of features that you will use frequently. In this section, you will learn more about using list windows, organizing and finding data, and generating reports.
TestTrack Items
TestTrack includes following types of items. Each item type has a list window, which is used for organization and providing access to items. See Using List Windows, page 21. Note: The items you can work with depend on the TestTrack products you have access to and security permissions.
Issues
An issue is a bug, enhancement, change request, work item, question, or any other product-related issue you need to track and resolve. Issues are available in TestTrack Pro. To work with issues, choose View > Issues. To create an issue, choose Create > Issue. See Adding Issues, page 159.
Requirements
A requirement is a specific business, functional, technical, or other type of defined requirement you need to track and manage. By default, TestTrack includes business, functional, and non-functional requirements. Requirements are available in TestTrack RM. To work with requirements, choose View > Requirements. To add a requirement, choose Create > Requirement. See Adding Requirements, page 183.
Requirement documents
A requirement document groups and organizes a set of related requirements. Requirement documents are available in TestTrack RM. To work with requirement documents, choose View > Requirement Documents. To add a requirement document, choose Create > Requirement Document. See Adding Requirement Documents, page 181.
Test cases
A test case is a set of conditions, actions, expected results, and other criteria used to determine if a product component is working correctly and meets its specified requirements. Test cases are available in TestTrack TCM. To work with test cases, choose View > Test Cases. To add a test case, choose Create > Test Case. See Adding Test Cases, page 255.
19
Te st Tr ack It e ms
Test runs
A test run is an instance of a test case that is generated at a milestone in the testing cycle, such as when a build is provided by the development group. A test run contains all information from the related test case, but also includes the results of a specific instance of the test. Test runs are available in TestTrack TCM. To work with test runs, choose View > Test Runs. To generate test runs, select a test case in a Ready state and choose Activities > Generate Test Runs. See Generating Test Runs, page 280.
Folders
Folders can help you organize items in TestTrack. A folder can contain any combination of issues, requirements, requirement documents, test cases, and test runs. Folders are available in all TestTrack products. To work with folders, choose View > Folders. To add a folder, choose Create > Folder. See Adding folders, page 61.
Users
TestTrack supports global and local users. Global users, which are created in the Seapine License Server or in TestTrack, have usernames and passwords and can generally access projects. Local users, which are created in TestTrack or when bugs are submitted via SoloSubmit or SoloBug, are usually created for tracking purposes. Users are available in all TestTrack products. To work with users, choose View > Users. To add a user, choose Create > User. See Adding users, page 330. To retrieve global users from the Seapine License Server and add them to TestTrack, click Retrieve Global User on the Users list window. See Retrieving global users, page 336.
Customers
Customers are generally the end-users of your products or services. Like users, TestTrack supports global and local customers. However, customers usually do not have access to projects and are created for tracking purposes. Customers are available in all TestTrack products. To work with customers, choose View > Customers. To add a customer, choose Create > Customer. To retrieve global customers from the Seapine License Server, click Retrieve Global Customer on the Customers list window. See Retrieving global customers, page 337.
Security groups
A security group is a collection of users who share responsibilities and perform similar tasks. Access to TestTrack functions and fields is controlled by group security. Users must be assigned to a security group before they can work with TestTrack projects. Security groups are available in all TestTrack products.
20
U sin g List Win d ows
To work with security groups, choose View > Security Groups. To add a security group, choose Create > Security Group. See Adding security groups, page 324.
Filters
A filter is a set of criteria used to work with a specific set of records. You can apply filters on list windows, in reports, and in other areas of TestTrack. Filters are available in all TestTrack products. To work with filters, choose View > Filters. To create a filter, choose Create > Filter and select an item type. See Creating Filters, page 97.
Reports
A report is used to analyze the data collected in a TestTrack project. TestTrack includes built-in detail, distribution, list, and trend reports. You can also view reports from external reporting services. Reports are available in all TestTrack products. To work with reports, choose View > Reports. To generate a report, select a report and click Preview. To add a report, choose Create > Report and select a report type. See Creating Reports, page 119.
Test configs
A test configuration, or test config, stores information about a specific computer used for testing and the hardware and software found on the computer. Test configs are available in all TestTrack products, but are primarily used with TestTrack Pro and TestTrack TCM. To work with test configs, choose View > Test Configs. To add a test config, choose Create > Test Config. See Adding test configs, page 177.
Using List Windows

List windows organize information and provide access to TestTrack records and data. TestTrack includes list windows for everything from issues to security groups. Note: You most likely will not work with all list windows and may not have access to some list windows or list window commands, depending on your security permissions.
n
Issues list window Provides access to issues. You can view, add, edit, and delete issues from this window. Test Cases list windowProvides access to test cases. You can view, add, edit, and delete test cases from this window. Test Runs list windowProvides access to test runs. You can view, add, edit, and delete test runs from this window. Requirements list windowProvides access to requirements. You can view, add, edit, and delete requirements from this window. Requirement Documents list windowProvides access to requirement documents. You can view, add, edit, and delete requirement documents from this window.
21
Workbook list windowProvides access to your assigned items and other tasks you add to the workbook. You can view, add, edit, and delete tasks from this window. Folders list windowProvides access to folders. You can add, view, edit and delete folders from this window. You can also add, view, edit, or remove items in folders, and drag folders and items to reorganize them. See Using the Folders list window, page 58. Customers list windowProvides access to customers. You can view, add, edit, and delete customers from this window. You can also retrieve global customers from the Seapine License Server or promote local customers to global customers. Users list windowProvides access to users. You can view, add, edit, and delete users from this window. You can also retrieve global users from the Seapine License Server or promote local users to global users. Security Groups list windowProvides access to security groups. You can view, add, edit, and delete security groups from this window. Test Configs list windowProvides access to test configurations. You can view, add, edit, and delete test configs from this window. Filters list windowProvides access to filters. You can view, add, edit, and delete filters from this window. You can also view information about specific filters. Reports list windowProvides access to creating and generating reports. You can view, add, edit, delete, print, or preview reports from this window.
Opening list windows

To open a list window and work with the corresponding records, click the toolbar button or select the list window from the View menu.
After the list window is open, you need to select the records you want to work with.
n n
To select more than one record, hold down the Ctrl key while clicking the records. To select a range of records, click the first record then hold down the Shift key and click the last record. To select all records, choose Edit > Select All or press Ctrl+A.
22
Tip: You can also open multiple list windows. For example, you may want to compare issues using two different filters. To open another list window, choose View > New List. You can use tabs to manage multiple open list windows. See Adding Tabs, page 32.
About list window indicators

List window indicators are icons that indicate new, changed, closed, and your assigned issues, requirements, requirement documents, test cases, or test runs. Icon Indicates Items added since you last logged in Items that changed since you last logged in Closed items Items assigned to you
Note: If TestTrack is minimized or in the background and a record is assigned to you, a notification icon is displayed in the computers system tray.
Customizing list windows

You can customize the information that is displayed on list windows by adding or removing columns, moving columns, changing column contents, and adding column totals. You can also change the font used for the text in list windows.
Changing font settings

You can change the font used to display information in list windows. 1. Right-click a column heading and select Font Settings. The Select Font dialog box opens. 2. Select the font settings you want to use and click OK. The changes are applied to text in all list windows.
Inserting columns
You can add columns to display the information you need. 1. Right-click the column you want to add a column next to and select Insert Column. An empty column is inserted. 2. Right-click the new column and select a field from the shortcut menu. The column is added. To change the width of a column, move the cursor to the divide bar between the column headings. Drag the divide bar to change the width of the column to its left.
23
Changing column contents

1. Right-click the column heading you want to change. The shortcut menu lists all the available fields. 2. Select a field from the menu. The column heading changes to the field name and the selected field contents are displayed.
Sorting columns
You can sort by any column on a list window. You can also perform primary and secondary sorts.
n
Click a column heading to perform a primary sort. An arrow is displayed next to the heading. Click the column heading again to toggle between sort order. Shift+click a column heading to perform a secondary sort. A double arrow is displayed next to the heading. Shift+click the column heading again to toggle between sort order.
Moving columns
1. Click the column you want to move and hold down the mouse button. 2. Drag the column to the new location and release the mouse button.
Removing columns
1. Right-click the column heading you want to remove. 2. Select Remove Column from the shortcut menu.
Displaying totals for numeric columns

You can insert column footers to display the total value of numeric columns. This is useful as a quick reference for release tracking information, such as estimated and actual hours, or for coverage analysis information, such as total number of test cases. 1. Right-click the list window toolbar area. 2. Select Numeric Column Totals. The column footer row is added to all list windows and displays totals for visible numeric columns.
Filtering list window columns

Column filters allow you to quickly filter list windows to display specific data. When you click a column filter, a menu of possible values for the column opens. After you select a value, the list window is updated to display corresponding records only. Tip: You can also use column filters to further limit the records displayed on a filtered list window. See Using Filters, page 29. 1. Click the column filter button next to the Filter list to enable column filters.
24
2. Filter buttons are displayed in each column header after column filters are enabled. Click the filter button in the corresponding column. A list of the column values is displayed. If the list has more than 30 values, only the All and Custom options are displayed.
3. Select the value to use as the filter. Records that include the selected value are displayed. Notice the Find Results filter is applied.
n n n
Select Custom to perform a more powerful search using more complex restrictions. Select All to clear the column filter. Filtered column headers are displayed in a different color. You can change the color in user options. See Setting search options, page 350.
4. Click All to clear all the column filters. Note: Click the column filters button next to the Filter list to disable column filtering.
Using type ahead searching

Type ahead searching makes it easy to quickly find records in list windows. 1. Open the list window you want to search. 2. Type the characters you are searching for in the list window. The search is not case sensitive. Matching text is highlighted in the list window as you type. Type additional characters to narrow the results.
25
Note: You can change the type ahead text color and format. See Setting search options, page 350. 3. Choose Edit > Find Next to find the next match. 4. Choose Edit > Find Previous to select the previous match. 5. Press Esc to clear the search.
Editing items inline in list windows

You can edit item fields directly in list windows to make changes without opening the Edit dialog box. Inline editing is available in the Issues, Requirements, Requirement Documents, Test Cases, Test Runs, and Folders list windows. Note: You cannot edit the following fields inline: system fields, calculated fields, workflow event fields, issue reported by fields, multi-line text fields, and other fields that cannot be edited in the item Edit dialog box. 1. Select an item in a list window and choose Edit > Edit Inline. The item opens in edit mode.
Note: You can also double-click items to edit them in list windows. Click the Toggle Inline Editing button. Click the button again to disable inline editing. 2. Make any changes. 3. Press Enter to save the changes. You can also click the Save button and then select Save to save the changes. Click Cancel to discard the changes. Note: You may be prompted to enter an electronic signature and change reason when saving items. See Entering Electronic Signatures, page 477.
Opening items in Microsoft Excel

You can open items in Microsoft Excel to provide information to stakeholders who do not have access to TestTrack. 1. Display the columns of information you want to open in Excel. 2. Select the items you want to open in Excel To select more than one item, Ctrl+click each item.
26
3. Choose Activities >Open inExcel. Excel starts automatically and the information is added to a new worksheet. If you are working a Windows computer, TestTrack Web hyperlinks for the items are also added. Note: You may be prompted to confirm opening the items in Excel because TestTrack creates a temporary file with the .xls file extension to hold the items. Click Yes to continue opening the items in Excel.
Printing list window records

You can print any of the records displayed in a list window. Tip: You can also print reports from the Issues, Folders, Requirements, Requirement Documents, Test Cases, and Test Runs list windows. Right-click the list window, choose Print, and then select the report to generate. The available reports depend on the list window and security permissions. 1. Select the records you want to print in the list window. Skip this step if you want to print all records. 2. Choose File > Print. The Print Options dialog box opens.
3. Select any print options.

n
Select Print as list to print all the records in a list format. Select a stylesheet if you do not want to use the default stylesheet, which is specified in your local options. See List window report stylesheets, page 562. Select Print gridlines to include gridlines in the report. Select Print as detail to print the details for each record. Select a stylesheet if you do not want to use the default stylesheet, which is specified in your local options. See List window report stylesheets, page 562. Optionally select Print items on separate pages to print each record on a separate page. Select Create report file from template to save a report as text based on a previously created template. After selecting this option, click Save. See Saving list window reports as text files, page 152. Optionally select Only print selected items to print the records selected on the list window.
27
Cr e at in g U se r -De fin e d Vie ws
4. Click Print. You can also click Preview to open the report in preview mode.
Creating User-Defined Views

If you frequently customize list windows to display specific information, you may want to create a view to save the column layout, sorting, and filtering of the current list window. You can apply a saved view to a list window. See Applying user-defined views, page 28. Note: Views cannot be created for the Folders list window. 1. Choose View > Save As View. The Save View dialog box opens.
Tip: If you perform a find or advanced find before saving the view, you are prompted to save the find results as a filter. If you do not save the results, the saved view uses the filter selected before you performed the search. 2. Select a Save View As option.
n n
Select New View to save the view using a new name. Enter a Name. Select Existing View to replace an existing view. Select the view to replace.
3. Click OK. The view is saved. Note: You can edit or delete views in user options. See Editing user-defined views, page 29 and Deleting user-defined views, page 29.
Applying user-defined views

You can apply a saved view to the current list window. You can only apply a view to the list window it was created for. For example, you cannot apply a Users view to the Issues list window. 1. Choose View > Apply View. 2. Select a view. The view is applied to the list window.
28
U sin g Fil t e r s
Note: If the view uses a filter with interactive restrictions, the Interactive Filter Wizard opens. See Using interactive filters, page 30.
Editing user-defined views

You can rename a view or select a different filter to use for the view. 1. Choose Tools > User Options then select the Views category. 2. Select the view you want to change and click Edit. The Edit View dialog box opens. 3. Make any changes and click OK. The changes are saved.
Deleting user-defined views

You can delete views that are no longer used. 1. Choose Tools > User Options then select the Views category. 2. Select a view and click Delete. You are prompted to confirm the deletion. 3. Click Yes. The view is deleted.
Using Filters
You can filter the list windows to view specific records. For example, you can apply a filter to the Issues list window to only view issues that are over three months old. 1. Select the filter from the Filter list on the corresponding list window. The Filter list includes private filters that you created and shared filters you have access to. See Adding Filters, page 97.
29
U sin g in t e r act ive fil t e r s
2. The filter is applied to the records. If the filter includes interactive restrictions, the Interactive Filter Wizard opens. See Using interactive filters, page 30.
n n
Records that meet the filter criteria are listed on the corresponding list window. Select Not Filtered to return to a list of all records.
Using interactive filters

Filters can include interactive restrictions that allow you to select criteria when you apply the filter. The Interactive Filter Wizard opens if you apply a filter with interactive restrictions to a list window, generate reports that use the filter, apply a user-defined view that uses the filter, or apply the filter to select items to add to links. The wizard guides you through entering information for each interactive restriction. The filter is applied using the information you enter plus any non-interactive restrictions specified for the filter. Tip: To make a restriction interactive, select the Prompt for restriction information at run time option in the Add Restriction or Edit Restriction dialog box. See Adding Filters, page 97. 1. The Interactive Filter Wizard opens when you select an interactive filter. The default restriction information is displayed. The restriction options change based on the restriction field.
30
Vie win g fil t e r s
Note: The filter name and fields the restrictions are based on are displayed at the top of the wizard. Fields with question marks (?) indicate interactive restrictions. 2. Enter or select the restriction information. 3. Click Next to enter information for any additional restrictions. 4. Click Finish when you finish entering the restriction information. The Interactive Filter Wizard closes and the filter is applied. Note: If you are applying the filter to a list window, records that meet the filter criteria are displayed. Select Not Filtered to return to a list of all records.
Viewing filters
1. Select the filter on the Filters list window. 2. Choose Edit > View Filter or click View on the Filters list window. The read-only View Filter dialog box opens. 3. Click Edit to edit the filter. See Editing filters, page 117. 4. Click OK when you are finished.
Viewing restrictions
1. Select the restriction on the Add Filter, Edit Filter, View Filter, or Advanced Find dialog box. 2. Click View. The read-only View Restriction dialog box opens.
31
Ad d in g Tab s
3. Click OK to close the Restriction dialog box.
Adding Tabs
Tabbed list windows makes it easy to quickly switch between customized list views, instantly changing the column layout and filter results. Instead of opening and switching between list windows, you can use tabs to manage multiple instances of the same list window. When you create a tab, another instance of current list window opens on a tab in the existing window. For example, you can add tabs to the Issues list window to view multiple Issues list windows with different filters or views applied. Tip: You can set an option to always display the tab bar on list windows. See Setting display options, page 348. 1. Select the list window you want to add a tab to. Note: Tabs cannot be added to the Folders list window. 2. Choose Tabs > Add Tab or click the add button on the tab bar. A new tab is added to the list window.
n n
You can rename the tab. See Renaming tabs, page 32. You can customize the information displayed on each tab. For example, you can add tabs to the Issues list window so you can view Issues list windows with different filters or views. You can save the information displayed on a tab as a view or apply a view to the tab. To save the tab as a view, right-click the tab and choose Save As View. See Creating User-Defined Views, page 28. To apply a view, right-click the tab, choose Apply View, and select the view to apply.
3. Click the tabs to navigate between list windows.
Renaming tabs
1. Choose Tabs > Rename Current Tab. The Rename Tab dialog box opens. 2. Enter a new Name and click OK. The tab name is changed.
Closing tabs
1. To close the current tab, choose Tabs > Close Current Tabor click the close button on the tab bar. 2. To close all tabs except the current tab, choose Tabs > Close All Other Tabs.
32
U sin g t h e Wor kb ook
Using the Workbook

The TestTrack workbook can help you stay organized by providing an easy way to track your assigned items and other tasks. You can also add project-related tasks to the workbook. For example, you can add a task to remind you about project notes that you need to complete for a meeting. Workbook tasks are private and are not shared with other users.
Adding tasks
1. Choose Create > Task. The Add Task dialog box opens.
2. Enter a Task name. 3. Select the task Priority. 4. The Date defaults to the current date. You can enter another date or click the calendar to select a date. 5. Select a Need by date and Need by version. 6. Enter a Description. 7. Click Add. The task is added to the workbook.
Viewing tasks
1. Select the task on the Workbook list window. 2. Choose Edit > View Task or click View. The read-only View Task dialog box opens. 3. Click Edit to edit the task. See Editing tasks, page 33. 4. Click OK when you are finished.
Editing tasks
1. Select the task on the Workbook list window.
33
Fin d in g Re cor d s
2. Choose Edit > Edit Task. The Edit Task dialog box opens. 3. Make any changes. Select Done if the task is complete. 4. Click OK. The changes are saved.
Duplicating tasks
If you add tasks with the same basic information, you can save time by duplicating and editing an existing task. 1. Select the task on the Workbook list window. 2. Choose Edit > Duplicate Task. The task is duplicated. 3. Modify the duplicated task and save the changes.
Deleting tasks
1. Select the task on the Workbook list window. 2. Choose Edit > Delete Task. You are prompted to confirm the deletion. 3. Click Yes. The task is deleted.
Finding Records
You can find items by searching against the summary and description fields, the requirement document name, the test case or test run steps, the workflow event notes, or all text fields. Tip: If you know the record number you can go directly to that record. Choose Edit > Go To. Select the record type, enter the record number, and click OK. 1. Choose Edit > Find. The Find dialog box opens.
34
Fin d in g Re cor d s
2. Select a record Type. 3. Select the search field from the Find list. You can search the Summary field, Description field, All Event Notes, or All Text. You can also search the requirement document Name field or the test case or test run steps. If a field is not included in the Find list, you do not have security permissions to search related fields. Note: All Text searches text field values. See Searching all text fields, page 37. 4. Enter the text you want to search for in the Contains field. You can enter a text string or text that includes the following wildcards:
n n
Use an asterisk (*) to match zero or more characters. Use a question mark (?) to match one character.
5. Select the type of search from the Use list.

n n
Select Plain Text Search to search for the exact text. Select Wildcards to perform a wildcard search.
6. Select a matching option.

n n n
Select Match phrase to search for the exact phrase. Select Match any search term to search for any of the search terms. Select Match all search terms to search for all of the search terms. Note: See Search examples, page 38 for examples.
7. Select Match case to match the case of the text. 8. If you applied a filter to the list window, select Based on current filter to only search filtered records. 9. Click Find.
35
Goin g d ir e ct l y t o a r e cor d
The search results are displayed in the corresponding list window. Notice the Find Results filter is applied. If matching records are not found, a warning message opens. Click OK. You return to the corresponding list window, which is empty. Notice the Find Results filter is applied.
Going directly to a record

If you know the number of a record, you can go directly to it. 1. Choose Edit > Go To. The Go To dialog box opens. 2. Select a record Type and enter the number. 3. Click OK. The record opens.
Using quick find

Use quick find to quickly find records in a list window. Note: To open the quick find toolbar, View > Toolbars > Quick Find. 1. Enter the value you want to search for in the Find field. You can enter a text string or text that includes the following wildcards:
n n
Use an asterisk (*) to match zero or more characters. Use a question mark (?) to match one character. Note: To use a previous search, select a value from the Find list. Search values are cleared when you close the list window.
2. Select the field to search from the In list. You can search text fields and the Notes fields in specific workflow events. You can also search the following information:
n n n
All Text searches all text fields. See Searching all text fields, page 37. All Event Notes searches all Notes fields in workflow action events, such as Assign and Fix. All Informational Event Notes searches all Notes fields in informational workflow events, such as Comment. Folders Path searches folder path names. File Attachment Name searches all file attachment names. SCC File Name searches all SCC file attachment names. Note: If a field is not included in the In list, you do not have security permissions to search related fields.
n n n
3. Click Options to select any search options.
36
U sin g q u ick fin d
Select Based on current filter to search the records in the list window based on the selected filter. Select Match case to match the case of the text. Select Match whole phrase to search for the exact phrase. Select Match any search term to search for any of the search terms. Select Match all search terms to search for all of the search terms. Select Match only open <item type> to only search open records. Select Match only closed <item type> to only search closed records. Select Text search to search for the exact text. Select Wildcard to perform a wildcard search. Select Advanced find to perform a more powerful search. The search criteria you entered is displayed in the Advanced Find dialog box. See Using advanced find, page 38. Note: See Search examples, page 38 for examples.
n n n n n n n n n
4. Click Find.
n
If matching records are found, the search results are displayed in the list window. Notice the Find Results filter is applied. If matching records are not found, a warning message opens. You return to the list window, which is empty. Notice the Find Results filter is applied.
5. Click Clear to clear the find results.
Searching all text fields

When you perform a search or create a restriction, you can select All Text to search all text fields. The following text fields are searched when the All Text option is selected:
n n n n n n n n n n n
IssuesSummary, Version, Reference, Workaround, and all Reported by text fields RequirementsSummary and Description Requirement documentsName and Description Test casesSummary and Steps Test runsSummary, Steps, and Problem Statements EventsNotes, Version, and attachment names Text custom fields Attachment file names Source file attachment names Link comments Tracked email subject and body
See Finding Records, page 34.
37
U sin g ad van ce d fin d
Search examples
The following examples are provided to help you understand how you can use search options and wildcards to perform more flexible and powerful searches. See Finding Records, page 34. For example, you want to perform a search using the terms 'run report'. The search results are different based on the search option you select.
n
Match exact phrasePerforms a search for an exact match and only returns records that include 'run report', including the space between the words. The results also include any instances of the phrase within other phrases, such 'run reporting' or 'overrun reported'. Match any search termPerforms an OR search and returns records that contain either 'run' or 'report'. The results also include any instances of either term in other words, such as 'truncated' or 'unreported'. Match all search termsPerforms an AND search and returns records that contain both 'run' and report'. The results also include any instances of both terms in other words, such as 'shrunk' and 'reportedly'.
You can use wildcard characters to replace characters in search terms. Wildcards are helpful if you are searching for terms with spelling variations or terms that may or may not include spaces, dashes, or other characters.
n
Use an asterisk (*) to substitute for zero or more characters including spaces. For example, if you enter 'p*int', the results include 'pint' and other words such as 'point', 'imprint', and 'complaint'. The results also include any phrases that contain a word ending with 'p' and another word that includes 'int ', such as 'map is disjointed'. The asterisk represents the characters between the 'p' and 'int'. Using the asterisk wildcard to search longer text fields, such as the Description field, may return a large number of results. Use a question mark (?) to substitute for one character including spaces. For example, if you enter 'p?int', the results include words such as 'print', 'point', and 'paint'. The results also include any phrases that contain a word ending with 'p', followed by a space, and another word starting with int, such as 'map internal'. The question mark represents the single character between the 'p' and 'int'.
Using advanced find

Use advanced find to perform a more powerful search using filters and Boolean logic. You can also search on multiple restrictions. See Using Filters, page 29. 1. Choose Edit > Advanced Find. The Advanced Find dialog box opens. 2. Select a record Type. Note: If the records are filtered, the Advanced Find dialog box is populated with the filter restrictions. Click Clear to remove the restrictions. 3. Click Add to add a restriction. The Add Restriction dialog box opens. You can add up to 20 restrictions to a search. See Adding Restrictions, page 99. 4. Select a field from the Restrict by list.
38
Fin d in g u se r s an d cu st ome r s
The restriction options you can set change based on the selected field. 5. Select the restriction options. 6. Click OK. The restriction is added to the search and you return to the Advanced Find dialog box. 7. Optionally select NOT/AND/OR operators and parentheses to build Boolean logic for the search. See Adding Filters, page 97. 8. Repeat steps 3 through 7 to add additional restrictions. 9. Click Validate to validate the search criteria. Click OK if the criteria is valid.
n
An error message opens if the criteria is not valid. Click OK to return to the Advanced Find dialog box and correct the error. Click Clear to clear all restrictions and start over.
10. Click Make Filter to save the search criteria as a filter. See Adding Filters, page 97. 11. Click Find when you finish adding restrictions and the criteria is validated.
n
If matching records are found, the search results are displayed on the list window. Notice the Find Results filter is applied. If matching records are not found, a warning message opens. You return to the list window, which is empty. Notice the Find Results filter is applied.
Finding users and customers

If a TestTrack project includes a large number of users or customers, it may be easier to search for users instead of locating them in a list. You can search all user record fields for a value or perform an advanced search to search specific fields, such as Company, Division, and Department. 1. To search for users or customers to add to a field, click the Find button next to the field. To search for a user or customer to edit, click Find on the Users or Customers list window. The Select Users dialog box opens.
39
Fin d in g u se r s an d cu st ome r s
Note: The available options depend on the type of search you are performing. 2. Enter the value you want to search for in the Search field. The search is not case sensitive. The following user record fields are searched: Last name, First name, MI, Security group, Company, Division, Department, and Address. 3. Optionally expand the Advanced Search area to display additional search options. Advanced Search options allow you to search for values in specific user record fields. Note: If the Search field contains a value, it is used with the Advanced Search criteria for the search. 4. Click Find. The search results are displayed. Click Clear to clear the search criteria and results. 5. Select a user in the Search Results area.
n n
If you are adding a user to a single user field or editing the user record, skip to step 6. To add users to a multiple user field, select the users in the Search Results area and click Add. To remove users, select the users in the selected users list and click Remove.
6. Click Select to add the users to the field. Click Edit to edit the user. See Editing users, page 339 and Editing customers, page 339.
40
Vie win g Wor kfl ow Eve n t Hist or y
Viewing Workflow Event History

After workflow events are entered for an item, you can view where the item is in the workflow, assignments, and any comments or additional information users entered. You may also be able to modify the event details. 1. Click the Workflow tab when you are viewing or editing an item. The events added to the item are displayed.
Note: Select Show System Comments to display events entered by automation rules. 2. Click Work Items to view events with time tracking information, including the estimated, actual, and remaining work for the item. See Viewing work items, page 44. 3. Click Diagram to view a diagram of the states the item was previously in, the events used to move the item between states, and next available states for the item. See Viewing item workflow history diagrams, page 43. 4. Select an event to view the event notes. 5. Select an event and choose Edit > View Event to view the event details. See Viewing workflow event details, page 41. 6. Select an event and choose Edit > Edit Event to edit the event details. See Editing workflow event details, page 42. 7. Select an event and choose Edit > Delete Event to delete it. See Deleting workflow events from items, page 42. 8. Click OK to close the dialog box.
Viewing workflow event details

You can view details about where an item is in the workflow, assignments, and any comments or additional information a user entered. You may also be able to modify the event details. 1. Click the Workflow tab and click Events when you are viewing or editing an item.
41
Ed it in g wor kfl ow e ve n t d e t ail s
Note: Select Show System Comments to display events entered by automation rules. 2. Select the event you want to view. 3. Choose Edit > View Event. A dialog box for the selected event opens. For example, the Estimate dialog box opens when you view an Estimate event.
4. Click OK to close the dialog box.
Editing workflow event details

You can edit workflow events, or activities, to add information or correct mistakes. For example, an issue resolution affects documentation but you forgot to select the Affects Documentation check box. You can edit the event to select the check box. 1. Click the Workflow tab and click Events when you are viewing or editing an item. Note: Select Show System Comments to display automation rule events. You cannot edit these events. 2. Select the event you want to edit. 3. Choose Edit > Edit Event. A dialog box for the selected event opens. 4. Make any changes and click OK.
Deleting workflow events from items

1. Click the Workflow tab and click Events when you are viewing or editing an item. 2. Select the event you want to delete. Note: You cannot delete events entered by System Comment, which are automation rule events. 3. Choose Edit > Delete Event.
42
Vie win g it e m wor kfl ow h ist or y d iagr ams
You are prompted to confirm the deletion. 4. Click Yes. The event is deleted.
Viewing item workflow history diagrams

Workflow diagrams display the path an item has taken through the workflow. The diagram includes the states the item was previously in, the current state, the events used to move the item to each state, and the next available states and events. 1. Click the Workflow tab and click Diagram when you are viewing or editing an item. The workflow diagram is displayed. Note: Select Show legend to display the diagram legend.
2. Select a Show option to indicate the diagram type to display.

n
Visited states displays the current state, states the item was previously in, the events used to move the item to each state, and the next potential states and events for the item. If the item was in a state more than once, the state is only displayed once. If the same event was entered more than once, the number of times the event was entered is displayed next to the event. Visited states (timeline) displays the same information as the Visited states diagram except states and events are displayed on a continuous line. If the item was in a state more than once, each instance of the state and event is displayed. Entire workflow displays the current and previous states for the item in context of the entire workflow configured for the item type. For example, if you are viewing the diagram for an issue, the workflow configured in the project for issues is displayed.
3. Click an event to view the event details. Events are displayed in blue text. See Viewing workflow event details, page 41. Tip: You can also mouse over an event to view when it was entered and who entered it.
43
Vie win g wor k it e ms
4. Click the Expand button to open the diagram in a new window. 5. Click Save As to save the diagram as a BMP, JPG, PNG, or SVG file. 6. Click Print Preview to preview the printed diagram or click Print to print it. 7. Click OK to close the dialog box.
Viewing work items

After workflow events are added to an item, you can view the estimated, actual, and remaining work for the item, and the variance between the estimated and actual hours. This can help you determine how much effort is required to complete an item. 1. Click the Workflow tab and click Work Items when you are viewing or editing an item. Workflow events that include time tracking information are displayed.
2. Select an event to view the event notes. 3. Select an event and choose Edit > View Event to view the event details. See Viewing workflow event details, page 41. 4. Select an event and choose Edit > Edit Event to edit the event details. See Editing workflow event details, page 42. 5. Select an event and choose Edit > Delete Event to delete it. See Deleting workflow events from items, page 42. 6. Click OK to close the dialog box.
Viewing Item History

You can view historical information for each item, including the user who created the item, when it was created, how it was created, who last modified it, and the date it was last modified. 1. Click the History tab when you are viewing or editing an item. The item history is displayed.
44
Vie win g ch an ge r e p or t s
2. Click a link in the Date column to view a change report that displays details about changes made to the item. To view changes for multiple entries, Ctrl+click each entry and click View Changes. See Viewing change reports, page 45. 3. Click OK to close the View or Edit dialog box.
Viewing change reports

Change reports display details of content added to and removed from an item each time it is saved. These reports can help you determine the specific changes made to an item over time. Change reports are only available if:
n
The Enable historical item information logging and Enable detailed audit trail logging project options are enabled for the item type. See Setting item compliance options, page 369. The item was modified in TestTrack 2011 or later.
1. Click the History tab when you are viewing or editing an item. See Viewing Item History, page 44. 2. Click a link in the Date column to view the change report for the entry. To select multiple entries, Ctrl+click each entry and click View Changes. The Change Report window opens. Content added to the item is displayed in green text and removed content is displayed in red strikethrough text. The electronic signature is also displayed if a change was made and signed in TestTrack 2012 and later and you have permission to view the audit log. Change reports are not available for duplicated items, which are displayed in gray. Note: You can change the added and removed text color and format in user options. See Setting differences display options, page 349.
45
Cr e at in g U se r N ot ificat ion Ru l e s
3. Click an attachment hyperlink to view the attachment. 4. Click Print Preview to preview the printed report or click Print to print it. 5. Click Close when you finish viewing the report.
Creating User Notification Rules

You can create notification rules to be informed of changes. Do not create notifications for every change. You may receive a large amount of email if you create too many rules. 1. Choose Tools > User Options then select the Notifications category.
2. Select a record Type. The items change based on the selected record type.
46
Note: Notifications are not sent for invalid rules, which are displayed in gray. For example, a rule becomes invalid if the filter used in the rule is deleted. You can edit an invalid rule to correct the problem. 3. Click Add to create a notification rule. See Adding user notification rules, page 47. 4. Select a rule and click Edit to change it. See Editing user notification rules, page 48. 5. Select a rule and click Inactivate to inactivate it. See Inactivating user notification rules, page 49. 6. Select a rule and click Delete to delete it. See Deleting user notification rules, page 49. 7. Click OK to save the changes.
Adding user notification rules

Make sure you do not create too many user notifications. Remember, you may receive a large number of emails if you create too many notifications or you create notifications that are not restrictive enough. Tip: You may also receive system notifications, which the TestTrack administrator creates. 1. Choose Tools > User Options then select the Notifications category. 2. Select a record Type. The items change based on the selected record type. 3. Click Add to add a rule. The Add Notification Rule dialog box opens with the Precondition tab selected.
4. Enter a Rule name. 5. Optionally select a Passes filter. You may want to select a filter if the project has a large number of records. Click Create Filter to create a filter. See Adding Filters, page 97. 6. Click the Trigger When tab.
47
7. Select the activity that causes the notification to be sent. 8. Click the Actions tab.
9. Select an email Template. 10. Select Do not send email if I made the change if you do not want to receive an email when you change a record. 11. Select Only send email if item is assigned to me to only receive email when you are the assigned user. 12. Click OK. The rule is added.
Editing user notification rules

You can edit user notification rules, but cannot change the activity selected on the Trigger When tab. 1. Choose Tools > User Options then select the Notifications category. 2. Select a record Type. The items change based on the selected record type. 3. Select a rule and click Edit. The Edit Notification Rule dialog box opens. 4. Make any changes and click OK. The changes are saved.
48
For mat t in g M u l t i-Lin e Te xt Fie l d s
Inactivating user notification rules

You can inactivate a rule if it is not used. You can activate the rule if you decide to use it again. 1. Choose Tools > User Options then select the Notifications category. 2. Select a record Type. The items change based on the selected record type. 3. Select a rule and click Inactivate. The rule is inactivated. Note: To activate an inactive rule, select the rule and click Activate.
Deleting user notification rules

You may want to delete notification rules that are no longer used. 1. Choose Tools > User Options then select the Notifications category. 2. Select a record Type. The items change based on the selected record type. 3. Select a rule and click Delete. You are prompted to confirm the deletion. 4. Click Yes. The rule is deleted.
Formatting Multi-Line Text Fields

You can change the appearance of text, insert links, images, horizontal lines, and tables, and check spelling in text fields. You can also insert stamps to mark changes.
Formatting text
You can use the formatting toolbar to customize the appearance of text in any field that allows multiple lines of text. For example, you can apply bold or italic styling to the text in a requirement's description to make the information stand out in a requirement document. Note: Text formatting is not available for test case and test run steps. 1. Click in the field you want to format. The formatting toolbar is displayed in the field. You can change the toolbar options to always display or hide it in text fields. See Setting formatting options, page 346.
49
Tip: Click the Expand view button to open the field editor in a new window. This may be helpful if you want more space to view or edit a field that contains large content. 2. Select the text you want to format and make any changes using the formatting toolbar. Mouse over a toolbar button to view the tool name.
n n
Click the Bold, Italic, Underline, and/or Strikethrough button to apply styles to the text. Click the Align left, Align center, Align right, or Align full button to set the alignment for the line of text. Select a Font from the list to change the font. Select a Font Size to increase or decrease the font size. Use the Select text color options to change the font color. Use the Select background color options to change the background color. Click the Bulleted list or Numbered list button to create a list. Note: To clear all text formatting, right-click the text field and choose Clear Formatting.
n n n n n
3. Click OK to save the changes.
Inserting hyperlinks
You can insert hyperlinks into fields that allow multiple lines of text. For example, you can insert a link to a web site used as a reference in a requirement's description. 1. Select the text you want to change to a link. 2. Click the Insert/edit link button on the formatting toolbar. The Insert Hyperlink dialog box opens.
3. Select the Type of hyperlink you want to insert. 4. Enter the URL. 5. Enter the Display Text. This field is automatically populated with the text you selected. 6. Click Insert. The hyperlink is inserted into the field. Note: To format the hyperlink, select it and choose Format >Hyperlink. You can edit, select, open, and remove the hyperlink.
50
Inserting images
You can insert images into fields that allow multiple lines of text. For example, you can insert an image in a test case's expected results field to provide a reference for results comparison. 1. Click the Insert/edit image button on the formatting toolbar in the field you want to add the image to. The Insert Image dialog box opens.
2. Click Browse to locate the image you want to insert. Note: Click Screen Capture to capture a screenshot to insert. See Capturing Screenshots, page 55. 3. Change the Dimensions if you want to resize the image. The Width and Height fields are automatically populated with the dimensions of the selected image. You can resize the dimensions by percentage or pixels. Select Maintain aspect ratio to avoid stretching the image out of proportion. 4. Click Insert. The image is inserted into the field. Note: To change an image's size, select the image and choose Format >Edit Image Size. Enter the new Width and Height values and click OK.
Inserting tables
You can insert tables into fields that allow multiple lines of text. For example, you can insert a table into an issue computer configuration field to help organize the hardware and software information. 1. Click the Insert/edit table button on the formatting toolbar in the field you want to add the table to. The Insert Table dialog box opens.
51
U sin g sp e l l ch e ck
2. Set the number of Rows and Columns for the table. 3. Optionally set any additional Table Options.
n n
Enter Width and Height values to set the size of the table. Enter a Cell Padding value to set the padding used between the contents of the table cells and the table borders. Enter a Cell Spacing value to set the space between individual cells. Select a table Frame. Frame on displays a visible table frame and Frame off does not display a table frame. If you select Frame on, set a Width for the thickness of the frame. Select an Alignment for the table contents. Select a Background Color. Select a color for the list or click the Background color button to choose from the color palette.
n n
n n
4. Click Insert. The table is inserted into the field. Note: To edit a table, click inside the table and choose Format >Table. You can change the properties of the individual cells, rows, and columns or the entire table. You can also insert and delete rows and columns and merge and split table cells.
Using spell check

TestTrack includes a spell check utility that can be used with text fields. You can also add words to the dictionary or customize spell check options. See Setting dictionary options, page 351 or Setting spell check options, page 353. 1. Choose Edit > Spell Check or right-click the text field and select Spell Check. The Check Spelling dialog box opens.
52
In se r t in g st amp s
2. Click Ignore to ignore a misspelled word or click Ignore All to ignore all instances of the word. 3. Click Add Problem Word to add the word in the Problem word field to the dictionary. 4. Click Delete Duplicate to delete a duplicate word. 5. To fix a misspelled word, select a word from the Suggestions list. You can also edit the word in the Change to field. If the spelling checker does not recognize a word, it tries to split the word into words it recognizes. Note: To search for replacement words, edit the word in the Change to field and click Suggest. 6. Click Change to use the selected suggestion or the edited word or click Change All to change all instances of the misspelled word at once. 7. The Check Spelling dialog box closes after all misspelled words are checked. Click Cancel to stop the spell check at any time.
Inserting stamps
You can use stamps to indicate changes or comments in multi-line text fields, such as the issue description. A stamp usually includes your name and the current date. Stamps can help other users identify comments added to a field. Note: The TestTrack administrator is generally responsible for setting the stamp format. See Setting general project options, page 355. 1. Move the cursor to the location in the text field where you want to insert the stamp. 2. Choose Edit > Insert Stamp. The stamp is inserted. You can change any of the information in the stamp.
53
At t ach in g Fil e s
Attaching Files
You can attach any type of file to issues, requirements, requirement documents, test cases, or test runs. For example, you may want to attach a flowchart, diagram, or screen mockup. Or, you may want to attach a screenshot to show the final result of performing a test. 1. If you are adding or editing an issue, click the Attachments mini tab on the Details tab. If you are adding or editing another item type, such as a test case, click the Files tab and then click the Attachments tab.
Note: You can attach automated tests to test cases and attach results reports to test runs. See Attaching automated tests to test cases, page 305 and Attaching automated test results to test runs, page 313. 2. Click Attach to attach a file. 3. Click Paste to paste a file from the clipboard. To rename the file, right-click it and choose Rename (Windows) or Ctrl+click it (Mac). Attachments cannot be renamed after a record is saved. 4. Click Screen Capture to capture and attach a screenshot. See Capturing Screenshots, page 55. 5. Select an attachment and click Remove to remove it. 6. Select an attachment and click View to view the file using the associated application. See Setting view file options, page 345. You may also be able to view thumbnails of image file attachments. Right-click a file and choose Show Thumbnail to view the thumbnail. 7. Select an attachment and click Extract to save a copy of the file.
54
Cap t u r in g S cr e e n sh ot s
8. Select an attachment and click Open to save a copy of the file and open it with the associated application. 9. Click Add or OK to save the changes. Note: If TestTrack is integrated with a source control tool, you can also attach source code files to items. See Attaching source code files, page 499.
Capturing Screenshots
You can capture, edit, and attach a screenshot to an item in TestTrack. For example, if you receive an unexpected error message during a test run, you can capture and attach a screenshot of the error message at the same time you add the new issue. You can also insert screenshots in multi-line text fields. 1. Minimize TestTrack and make sure the screen you want to capture is visible. 2. Maximize TestTrack and click Screen Capture. The screenshot opens in the Edit Screen Capture dialog box.
3. Use the Edit Screen Capture tools to make any changes to the screenshot.
n n
Click the Select Item tool button to move or resize the entire screenshot. Click the Select Area tool button to select part of the screenshot. With an area of the screenshot selected, you can click the Crop selected area button to crop the image or click the Copy selected area button to copy the selected area to the clipboard. Click the Undo button undo the most recent change. Click the Redo button to redo an undone change. Click the Text tool button to add text to the screenshot. You can change the font, font size, and font color as well as apply styles to the text used with the Text tool.
55
Or gan iz in g Dat a wit h Fol d e r s
Click the Pen tool button to draw on the screenshot. You can change the style, width, and color of the line used with the Pen tool. Click the Line tool button to draw straight lines on the screenshot. You can change the style, width, and color of the line used with the Line tool. Click the Rectangle, Rectangle with round corners, or the Ellipse tool button to add shapes to the screenshot. You can change the style, width, and color of the border as well as apply a fill color used with the shape tools. Click the Zoom actual, Zoom out, or Zoom in button to adjust the view of the screenshot. Click the Print preview button to preview the screenshot. Click the Print button to print the screenshot. Tip: Mouse over a toolbar button to view the tool name.
n n
4. Click Attach or Insert to add the screenshot to the item. 5. To rename an attached screenshot, right-click the file and choose Rename (Windows) or Ctrl+click the file (Mac). Note: Attachments cannot be renamed after an item is saved.
Organizing Data with Folders

Folders can help you organize items in TestTrack to help you manage products, releases, iterations, backlogs, and teams in a structure that best fits how you work. You can create a hierarchical folder structure to visually represent and manage any segment of a project. A folder can contain any combination of issues, requirements, requirement documents, test cases, and test runs. An item can also be added to multiple folders. Adding items to a folder tags a group of related items, which is useful for reporting and filtering on items of different types. TestTrack includes public and private folders. Public folders can be accessed by other users and are helpful for organizing items for your team. Access to public folders can be limited to specific security groups. Private folders cannot be accessed by other users and are helpful for organizing items related to your work. You can also create different folder types to control the appearance of folders and the type of data displayed for a group of folders. Following are some common uses for TestTrack folders.
Release planning and tracking

You can use folders to plan releases and iterations and track their progress. Before a release or iteration, you can enter the start and end dates, holidays and non-working days, working hours in a day, available users, vacation and sick day hours, and target story points for a folder. TestTrack automatically calculates the available man hours based on the information you enter. See Configuring release planning information, page 64. After you configure the release information, you and other team members can view the start and end dates, number of working days and remaining days in the period, available users, available man hours, and target story points in Release Planning pane in the Folders list window. See Using the Folders list window, page 58.
56
Or gan iz in g Dat a wit h Fol d e r s
Viewing live charts in the Folders list window can also help you monitor release or iteration progress. See Viewing Live Charts, page 71.
Project management and communication

You can use folders to group and organize items for a specific project and share project information with team members. For example, you may want to group requirements for a new feature in folders so you can track progress and communicate project information to other team members. You can display important messages about a project in the Folders list window Details pane. For example, you may want to provide schedule updates, milestones, or information about the next build. See Entering folder details, page 63. You can also display a web page related to the project in the Web View pane. For example, you may want to display a wiki related to a project. See Setting the default folder web page, page 64. The Folders list window can also display time tracking information in columns, such as estimated and actual hours and percent complete. This information can help you monitor progress of individual items and overall calculations for all displayed items.
Item organization by product and component

You can use folders to visually represent field relationships. For example, a project includes items for multiple products, which are values in the item Product field. Each product has multiple components, which are available in the Component field based on the value selected in the Product value. You can create a folder for each product and then create folders in each product folder to represent the related components.
Test organization
You can use folders to organize test cases in test suites. For example, you may want to group regression test cases together with the related test runs in child folders. You may also use folders to group test cases based on the areas to be tested, the test type, or tests that are automated. You can group test runs based on when they need to be performed, the system architecture, the assigned tester, or the test run results.
Issue triage
You can use folders and filters to create a triage system that decision makers can use to indicate an issue's priority. This can help you make sure high priority issues are fixed first, resolve priority conflicts, and maintain a history of issues fixed for a release. See Triaging Issues in TestTrack (http://downloads.seapine.com/pub/papers/TTTriageIssues.pdf) for more information.
Personal item tracking

You can use private folders to organize items related to your own work. For example, there may be change requests implemented that impact work you are responsible for. You can add these items to a private folder so you can easily locate and review the changes when you have time.
57
U sin g t h e Fol d e r s l ist win d ow
Using the Folders list window

The Folders list window provides access to folders, folder contents, and information about the contents. You can add, view, edit, or delete folders from this window. You can also add, view, edit, or remove items in folders, and drag folders and items to reorganize them. To open the Folders list window, choose View > Folders.
Configuring panes
You can move docked panes to a new position or create a tab from a docked pane. You can also hide panes you do not use. You cannot move or hide the Items pane.
n
To undock a pane to move to a new location, click the pane title bar and drag the pane to the new location. To dock a pane as a tab, drag the pane on top of the pane you want to combine it with. To hide a pane, choose View > Folder Panes and select the pane to hide. To view a hidden or closed pane, choose View > Folder Panes and select the pane to display.
n n n
Note: The Detail, Web View, and Release Planning panes may not be available depending on the folder type. See Adding folder types, page 412.
Folders tree
The Folders tree displays the hierarchy of folders in a project. The tree includes read-only Public and Private folders that store all other folders. Public folders can be accessed by other users and private folders cannot.
58
Click a folder to view its contents in the Items pane. Select List recursively to display all items in the folder and any child folders. Click the Add Folder button to add a new folder. See Adding folders, page 61. Select a folder and click the Remove Folder button to delete it. See Deleting folders, page 70. Select a folder and click the up or down arrows to move the folder in the hierarchy.
n n n
Items pane
The Items pane displays the items in a selected folder. You can limit the items displayed, view or edit items, and add new items to the project in this pane. You can also customize the pane columns and font size. See Customizing list windows, page 23.
Select an item type from the Show list to limit the items displayed. You can also apply a filter to display specific items. See Using Filters, page 29. Click Add to create a new item and add it to the selected folder. See Adding items to folders, page 66. Select an item and click View or Edit to open it. See Viewing items in folders, page 68 and Editing items in folders, page 68. Select an item and click Remove to remove it from the folder. See Removing items from folders, page 69. Select a folder and click Rank Items to rank the items in the folder. See Ranking items in folders, page 69.
Note: The folder type and name are displayed in the banner at the top of the pane. The banner color and folder icons can be customized for each folder type. See Adding folder types, page 412.
59
Release Planning pane

The Release Planning pane displays a release schedule overview. The release start and end dates, available working days, remaining days in the period, users available, total man hours, and total story points are displayed. The number of remaining days in the period is updated as the schedule progresses.
To set release planning information for the folder, see Configuring release planning information, page 64.
Details pane
The Details pane displays additional information about the folder. For example, the project manager may provide schedule updates or notes in this pane. To set the details, see Entering folder details, page 63.
You may also be able to edit the folder details directly in the Details pane. Note: See Adding folders, page 61 for information about allowing users to edit the Detail pane information.
Live Chart pane

The Live Chart pane displays project information in a chart format. Live charts are updated automatically when items in the project change and can help you monitor overall progress or a specific segment of a project in real time. See Creating live charts, page 143 and Viewing Live Charts, page 71.
60
Ad d in g fol d e r s
Web View pane

The Web View pane displays a default web page related to the folder. For example, this pane may display a wiki your team uses for additional product documentation. To set the folder's default web page, see Setting the default folder web page, page 64.
You can use the buttons in this pane to perform common browser functions, such as navigating forward and back and viewing a history of the last 25 pages you visited. You can also navigate to other pages from the default page.
Adding folders
1. Select the folder you want to add the new folder to on the Folders list window. 2. Click Add and then select Folder. The Add Folder dialog box opens.
61
3. Enter a Name and Description. 4. Select an Access option.

n n
Public folders can be accessed by other users and are helpful for organizing items for your team. Private folders cannot be accessed by other users and are helpful for organizing items related to your work. Shared with security groups folders are only shared with the selected security groups. Note: Access configured for parent folders is shared with all child folders. You can only change security access on parent folders.
5. The read-only Path field contains the folder the new folder will be created in. Click Browse to select a different folder. 6. Select a folder Type. The tabs displayed depend on the selected folder type. Note: Click the Configure button to create or change a folder type. See Configuring Folder Types, page 411 7. Click the Details tab to enter details about the folder. This information is displayed in the Details pane when the folder is open in the Folders list window. See Entering folder details, page 63. 8. Click the Web View tab to set the default web page for the folder. The page is displayed in the Web View pane when the folder is open in the Folders list window. See Setting the default folder web page, page 64. 9. Click the Release Planning tab to calculate the required release effort. This information is displayed in the Release Planning pane when the folder is open in the Folders list window. See Configuring release planning information, page 64. 10. Click Add. The folder is added.
62
Note: You may be prompted to enter an electronic signature and change reason. See Entering Electronic Signatures, page 477.
Entering folder details

You can provide additional information about a folder in the Details pane in the Folders list window. For example, you may want to provide links to additional project resources or general notes about the project. You can also allow other users to edit folder details in the Folders list window, which is useful for collaboration. See Using the Folders list window, page 58. Note: The Details pane in the Folders list window and the Detail tab in the Add Folder and Edit Folder dialog boxes are only available if the Enable Details pane option is selected for the folder type. See Adding folder types, page 412. 1. Click the Details tab when you are adding or editing a folder.
2. Enter any Notes. Tip: Use the formatting toolbar to apply formatting and add images and tables. See Formatting text, page 49. 3. Select Allow Details to be edited from the folder list window to allow users to edit the folder details in the Details pane in the Folders list window. 4. Click OK to save the changes. The information is displayed in the Details pane when the folder is open in the Folders list window.
63
Setting the default folder web page

You can display a default web page related to a folder in the Web View pane in the Folders list window. For example, you may want to display a wiki that provides additional project information. Users can also browse to other pages from the default page. See Using the Folders list window, page 58. Note: The Web View pane in the Folders list window and the Web View tab in the Add Folder and Edit Folder dialog boxes is only available if the Enable Web View pane option is selected for the folder type. See Adding folder types, page 412. 1. Click the Web View tab when you are adding or editing a folder.
2. Enter the Web address for the page you want to display in the Web View pane in the Folders list window. File addresses are only supported for images and HTML pages. For example, file:///C:/Projects/Sprint 1/calendar.htm. Note: Click Go to open the web page in your default browser. 3. Click OK to save the changes.
Configuring release planning information

If you use folders to track items, you may want to include information about the time and users available to work on an upcoming release, iteration, or project. This can help you estimate and calculate the man hours required to complete work in a specified time period. If you use Agile, you can indicate the number of target story points for an iteration. As you enter release planning information, calculations are automatically performed to determine the number of available man hours. The resulting information is displayed in the Release Planning pane in the Folders list window and is automatically updated as work progresses. See Using the Folders list window, page 58
64
Note: The Release Planning pane in the Folders list window and the Release Planning tab in the Add Folder and Edit Folder dialog boxes are only available if the Enable Release Planning fields option is selected for the folder type. See Adding folder types, page 412. 1. Click the Release Planning tab when you are adding or editing a folder.
2. Select a Start date and End date for the release. 3. Select Include weekends to include Saturday and Sunday in the total number of working days for the specified period. 4. Enter the number of holidays and other non-working days that apply to all users working on the release. This value is subtracted from the working days in the specified period. 5. Enter the number of working hours in day. This value supports up to two decimal places. The working days in the period (adjusted) value is multiplied by this value to determine the number of working hours in period. 6. Enter the number of users available to work on the release. This value supports up to two decimal places. The working hours in period value is multiplied by this value to determine the number of available man hours. 7. Enter the number of vacation and sick days in hours.
65
Ad d in g it e ms t o fol d e r s
This value supports up to two decimal places. This value is subtracted from the man hours in period value to determine the final available man hours value. 8. Enter the Target story points to indicate the story points to complete during the specified period. Story points are a relative unit of measurement used in Agile to estimate the difficulty or complexity of an item. Leave the value set to 0 if you do not use Agile or if you do not want to use story points. 9. Click OK to save the changes.
Adding items to folders

You can add items to folders when you are viewing or editing items. For example, a team lead may add issues for a product component to a public folder so she and other team members can quickly access all issues for the component. Tip: You can also drag records from the Issues, Requirements, Requirement Documents, Test Cases, or Test Runs list window to the Folders list window or create new items and add them directly to folders from the Folders list window. 1. Click the Folders tab when you are viewing or editing an item. 2. Click Add to Folder. The Browse for Folder dialog box opens.
3. Select the folder to add the item to. You cannot add items directly to the Public or Private folders. These folders only contain child folders. 4. Click OK to save the changes. The item is added to the folder and the folder path is displayed.
Moving items to folders

You can move items from one folder to other folders. This allows you to add items to different folders and remove them from previous folders at the same time. 1. Click the Folders tab when you are viewing or editing an item. 2. Select the folder that the item is currently in and click Move to Folder.
66
Vie win g fol d e r s
The Browse for Folder dialog box opens.
3. Select the folders to move the item to. 4. Click OK. The item is moved to the folder and the updated folder path is displayed.
Viewing folders
You can view read-only folder information, including the folder history. 1. Right-click the folder on the Folders list window and choose View Folder. The View Folder dialog box opens. 2. Click Edit to edit the folder. See Editing folders, page 68. 3. Click OK to close the View Folder dialog box.
Viewing folder history

You can view historical folder information, including the user who created the folder, when it was created, how it was created, who last modified it, and the date it was last modified. You can also view history entries added when folders are created, moved to a different parent folder, or deleted, or when items are added to or removed from folders. 1. Click the History tab when you are viewing or editing a folder. The folder history is displayed. 2. Click a link in the Date column to view a change report that displays details about changes made to the folder. To view changes for multiple entries, Ctrl+click each entry and click View Changes. See Viewing change reports, page 45.
67
Vie win g it e ms in fol d e r s
3. Click OK to close the View Folder or Edit Folder dialog box.
Viewing items in folders

You can view read-only item information in the Folders list window. 1. Select an item on the Folders list window and click View. The View dialog box opens. 2. Click OK to close the View dialog box.
Editing folders
You can edit a folder to rename it, modify the description, change the folder type, change the folder it is in, and modify other information. 1. Right-click the folder on the Folders list window and choose Edit Folder. The Edit Folder dialog box opens. Note: The folder history information is read-only. See Viewing folder history, page 67. 2. Make any changes and click OK. The changes are saved.
Editing items in folders

You can open items to edit from the Folders list window. Editing items from the Folders list window helps save time because you do not have to switch list windows or search for records. 1. Select an item on the Folders list window and click Edit. The Edit dialog box opens. 2. Make any changes and click OK. The changes are saved.
68
Ran kin g it e ms in fol d e r s
Ranking items in folders

You can rank items to indicate the priority or order of the items within the folder. For example, Agile teams may rank items in a backlog folder to indicate the priority of items to complete in a sprint or testers may rank test cases in a folder to indicate the sequence for performing tests. Item ranking is displayed in the Rank column in the Folders list window and on the Folders tab in the View and Edit item dialog boxes. 1. Right-click the folder in the Folders list window and choose Rank Items. The Rank Items dialog box opens. The folder is locked and cannot be edited or moved by other users. Note: If items in the folder have not been ranked, you are prompted to set the initial rank using the current sort order in the Folders list window. Click Rank Items to continue.
2. Select an item and click Move to Top, Move Up, Move Down, or Move to Bottom to change the rank. You can also drag and drop items to change the rank. Note: Select an item and click View to view it. 3. Click OK to save the ranking. The updated item rankings are displayed in the Folders list window. Note: If items are added while you are ranking, the new items are appended to the end of the list.
Removing items from folders

You can remove items from folders if they are no longer related to other items in the folder. Make sure you want to remove the item from the folder. You are not prompted to confirm the removal and the action cannot be undone. 1. Select the item on the Folders list window and click Remove. The item is removed from the folder. It is not deleted from the project.
69
De l e t in g fol d e r s
Deleting folders
You can delete folders that are no longer used. 1. Right-click a folder on the Folders list window and choose Delete Folder. You are prompted to confirm the deletion. 2. Click Yes. The folder is deleted.
Generating Reports
Reports provide the information you need to analyze the data collected in a TestTrack project. TestTrack includes built-in detail, distribution, list, and trend reports that you can preview, print, or save. You can also view reports from external reporting tools. See Report types, page 119.
Generating built-in reports

1. Select the report on the Reports list window. 2. Click Preview. A progress indicator opens. Click Cancel if you want to cancel the report generation. Note: If the report uses a filter with interactive restrictions, the Interactive Filter Wizard opens. See Using interactive filters, page 30. 3. The report opens in a new browser window. Depending on the browser, you can print the report, export the data, save the report to view later, or simply close the report after you view it.
Other ways to generate reports

You can also generate built-in reports from list windows or hyperlinks.
n
To generate reports from list windows, right-click the list window, choose Print, and then select the report to generate. The available reports depend on the list window and security permissions. To create a hyperlink that can be used to generate reports, right-click the report on the Reports list window and choose Copy Report Preview Hyperlink. Select ttstudio to copy a link that opens the report in the TestTrack Client or select http for a link that opens the report in TestTrack Pro Web. You can paste the link into TestTrack items or other applications. When the link is clicked, the report is generated in TestTrack.
Note: See Generating external reports, page 70 for information about external reports.
Generating external reports

When you generate an external report, the report is retrieved from the external reporting service and displayed in the viewer associated with the selected output type.
70
Vie win g Live Ch ar t s
To generate a report with parameters, such as filters, the external reporting client plug-in must be installed. Ask your TestTrack administrator for information. 1. Select the report on the Reports list window. 2. Click Preview. The Report Output Type dialog box opens if the report output format is set to <choose at runtime> or if there is only one valid output type. The available output types are defined in the server plug-in that communicates with the reporting service.
3. Select an Output Type. 4. Click OK. A progress indicator opens. Click Cancel if you want to cancel the report generation. 5. The report opens in the associated viewer. Depending on the viewer, you can print the report, export the data, save the report to view later, or simply close the report after you view it. If the output type is not associated with an application, you are prompted to save the report. Note: See Generating built-in reports, page 70 for information about generating built-in reports.
Viewing Live Charts

Live charts, which are updated automatically when items change, can help you monitor the overall progress or a specific segment of a project in real time. See Creating live charts, page 143. You can open live charts in one or more standalone windows, which can help you continuously monitor key indicators and team progress throughout the day. You can also open live charts in the Folders list window to chart the contents of a selected folder and view more focused data about a specific part of a project, release, or iteration.
71
Vie win g Live Ch ar t s
Note: You can set the live chart font in local options. See Setting live chart options, page 346.
Viewing a standalone chart

1. Choose View > Reports to open the Reports list window. 2. Select the live chart and click Preview. The chart opens.
Viewing a chart in the Folders list window

When you view a live chart in the Folders list window, the data is filtered to only include items in the selected folder. If the List recursively option is selected in the Folders list window, the chart includes items in any child folders. The items included in the chart are also limited based on the selected options in the Show and Filter lists. 1. Choose View > Folders to open the Folders list window. 2. If the Live Chart pane is not displayed, choose View > Folder Panes > Live Chart. The Live Chart pane is displayed. 3. Select a chart from the list in the Live Chart pane. The selected chart is displayed.
Live chart toolbar

The live chart toolbar includes commands to change the data displayed in a chart, copy a chart, open a chart in another window, and print a chart. The available commands depend on the window the live chart is displayed in.
72
Email in g fr om Te st Tr ack
Button Action Open the live chart in another window. Edit the live chart settings. See Editing reports, page 151. Copy the live chart to the clipboard. Show or hide the chart legend, title, data labels, axis labels, and axis titles. Print the live chart.
Emailing from TestTrack

You can send email directly from TestTrack, making it easy to communicate with users and customers without switching to your email application. Depending on your organizations use of TestTrack, emails may be tracked and added to the record they are sent from. You can view tracked email on the record Overview or Email tabs. See Viewing tracked email, page 75. 1. Select the record on the list window. Note: If you want to send an email that is not related to a specific record, make sure the list window does not have focus and then choose Email > Send Email. 2. Select the email recipient.
n n n
To email specific users, choose Email > Send Email. To email the currently assigned users, choose Email > Send to Currently Assigned Users. To email the user who found an issue, choose Email > Send to Found By User. If the record has multiple Found by users, they are all included as recipients. To email the user who entered the record, choose Email > Send to Entered By User. To email the user who last entered an event on the record, choose Email > Send to Last User Who Entered Event.
n n
The Send Mail dialog box opens.
73
Ad d in g e mail r e cip ie n t s
3. Enter the recipient email addresses in the To field. Separate multiple addresses with a semicolon. Click To to select recipients from a list or search for recipients. See Adding email recipients, page 74. Note: As you type, matches based on previously selected recipients are displayed. Select a name and press Enter to add it to the To field. 4. Optionally select an email Template if you are emailing from a selected record. Depending on your security permissions, you can click Configure to create or edit an email template. See Customizing Email Templates, page 466. 5. Enter a Subject. 6. Select Send as HTML to send the email in HTML format. You can use the style and formatting options or add HTML tags to the message. 7. Enter the message. 8. Click Send. The email is sent. If tracking is enabled, the email is added to the record.
Adding email recipients

Note: To send an email about a specific record, select it on the list window first. 1. Choose Email > Send Email. The Send Mail dialog box opens. 2. Click To.
74
Vie win g t r acke d e mail
The Send Mail Recipients dialog box opens. 3. Optionally select the Roles to use to filter the recipient list. You can filter the list by All Users, All Customers, or security groups. If you are emailing from a specific record, you can also select one of the following options:
n n n n n n
Entered by user (issues only) Created by users (all items except issues) Currently assigned users First, Last, or All Found by users (issues only) First, Last, or All Modified by users Last user to enter a specific event Note: To find a specific recipient in the list, enter the recipient name in the Type or select a name field. Matches are selected as you type. To search for recipients, click the Find button next to the field you want to add recipients to. See Finding users and customers, page 39.
4. Select the recipients and click To. 5. Optionally select the recipients you want to send a copy of the email to and click Cc. 6. Optionally select the recipients you want to send a blind copy of the email to and click Bcc. 7. Click OK. The recipients are added to the corresponding fields in the Send Mail dialog box.
Viewing tracked email

When email tracking is enabled, you can view tracked email when viewing or editing a record. 1. Select an email on the Email tab when you are editing or viewing a record. 2. Click View. The View Email dialog box opens with the Body tab selected. 3. Click the Attachments tab to manage files attached to the email.
n
Click View to view the file with the associated application. See Setting view file options, page 345. Click Extract to save a copy of the file. The Save As dialog box opens. Select the file location, enter a file name, and click Save. Click Open to save a copy of the file and open it with the associated application. The Save As dialog box opens. Select the file location and enter a file name. Click Save to open the file and save it in the selected directory.
75
Re p l yin g t o t r acke d e mail
4. Click Reply To to email the sender. See Replying to tracked email, page 76. 5. Click OK to close the View Email dialog box.
Replying to tracked email

You can reply to tracked email from TestTrack or from external email applications. Tracked email includes a code that tracks your reply with the related record. The reply address is automatically set to the email tracking address configured on the TestTrack Server. The reply is sent to TestTrack, added to the related record, and forwarded to the user you are replying to. 1. Select an email on the Email tab when you are editing or viewing a record. 2. Click Reply To. The Send Mail dialog box opens.
n
The To field contains the user or customer you are replying to. You can add additional recipients. See Adding email recipients, page 74. The Subject field contains the original email subject. The message body contains the original email message.
n n
3. Make any changes. 4. Click Send. The email is sent and added to the record.
Deleting tracked email

1. Select the email you want to delete on the Email tab when you are editing or viewing a record. Note: If the email contains a thread below it, the thread is also deleted. 2. Click Delete. You are prompted to confirm the deletion. This action cannot be undone. 3. Click Yes. The email is deleted.
76
Using Advanced Features

TestTrack includes advanced features that high-level or administrative users will use frequently. In this section, you will learn more about import and exporting data, changing bulk fields, linking items, creating filters and reports, creating RSS feeds, and managing orphaned email.
Linking Items
Linking items helps you establish relationships between items and manage related item changes. You can link related items in a project together in a parent/child relationship or peer relationship. If you only use one TestTrack product, such as TestTrack Pro, you can only link the same item types, such as issues. If you use multiple TestTrack products, such as TestTrack Pro and TestTrack RM, you can link different types of items, such as issues and requirements. Your use of linking depends on your companys business processes. For example, many companies do not merge issues because they need to maintain original issue numbers, so they use linking. When you link items, you use a link definition to specify the type of relationship linked items have. Link definitions may restrict the item types that you can link and number of items you can include in a link. An administrator or another high-level user is usually responsible for creating link definitions.
Adding links
1. Select the items you want to link on the list window. 2. Choose Activities > Add Link. The Add Link dialog box opens.
77
Ad d in g it e ms t o l in ks
Tip: You can also drag items from a list window directly onto another item in any list window to create a link. 3. Select a link Definition. To view more information about a definition, select it and click View Definition. The read-only View Link Definition dialog box opens. Tip: If you need to create a definition, see Configuring Link Definitions, page 470. 4. Optionally enter a Comment about the link. The comment is displayed on the Links tab and on the link diagram. 5. If you are adding a parent/child link, select the parent item and click Make Parent. 6. Click Select Items to Add to add additional items to the link. See Adding items to links, page 78. 7. Select an item and click Top, Move Up, Move Down, or Bottom to reorder the list. Reorder the list if the items must be closed in order or reopened in inverse order. 8. Select an item and click Remove to remove it from the link. To remove a parent item, you must first set another item as the parent. 9. Click OK to add the link.
Adding items to links

You can add additional items to existing links. For example, you might have created a link when generating a test case from a requirement. You can add test runs and issues that are generated from the test case to the existing link for traceability purposes. Tip: If you know which item is part of the existing link you want to add to, you can drag the item you want to add to the link directly onto that currently linked item in a list window. Select Add to existing link in the Link Items prompt. Select the link in the Add to Existing Link dialog box and click OK. 1. Click the Links tab when you are editing or viewing an item with links.
78
Diagr ammin g l in ks
2. Click Add Link. The Add Link dialog box opens. 3. Click Select Items to Add. The Select Items to Add dialog box opens.
Tip: This dialog box includes many of the same functions as the list windows. For example, you can filter the items or search for specific items. 4. Select a record Type. The records displayed depend on the selected record type. 5. Select the items you want to add and click Add.
Diagramming links
You can generate a link-based or object-based link diagram. This allows you to quickly view which links an item is included in and its relationship to other items in each link. 1. Click the Links tab when you are editing or viewing an item with links. 2. Click Diagram Links. The Diagram Link Options dialog box opens. 3. Select a Diagram Type. You can diagram links based on items or links. 4. Click OK. The diagram opens.
79
Vie win g l in ks
Viewing links
You can view read-only link information, including the definition, any comments, and the linked items. Tip: To see if an item includes links, add a Has Links column to the list window. See Using List Windows, page 21. 1. Click the Links tab when you are editing or viewing an item with links. 2. Click View Link. The View Link dialog box opens.
3. Click the Link History tab to view the link history. See Viewing link history, page 81. 4. Click OK to close the View Link dialog box.
80
Ed it in g l in ks
Viewing link history

You can view the history of any changes made to a link. A link history entry is created when a link is created or broken or an item is added, removed, or merged (issues only). 1. Click the Links tab when you are editing or viewing an item with links. 2. Select a link. 3. Click View Link or Edit Link then click the Link History tab. The following information may be displayed on the tab:
n
Link BrokenDate link was broken, user who removed parent item, item number, and summary information. Item AddedDate item was added, user who added it, item number, and summary information. Item RemovedDate item was removed, user who removed it, item number, and summary information. Issues MergedDate issue was merged, user who merged them, and old and new issue numbers. (Issues only)
n n
4. Click OK when you finish viewing the link history.
Editing links
You can edit a link to add or remove items to it, reorder items, or change the comment. 1. Click the Links tab when you are editing or viewing an item with links. 2. Select a link and click Edit Link. The Edit Link dialog box opens. 3. Make any changes and click OK.
Deleting links
1. Click the Links tab when you are editing or viewing an item with links. 2. Select a link and click Delete Link. You are prompted to confirm the deletion.
81
M ar kin g It e ms as S u sp e ct
3. Click Yes. The link is deleted.
Marking Items as Suspect

If an item changes, related items may be affected. You can mark related items as suspect to indicate they need to be reviewed to determine if any changes are needed. For example, if a requirement changes, test cases linked to the requirement may need to be updated. Marking the test cases as suspect when you edit the requirement adds a flag to the test cases to indicate the related requirement changed. Testers can click the flag to view the dependencies. See Investigating suspect dependencies, page 83. The following items can be marked as suspect:
n n
Items linked using a link definition that allows dependent items to be marked as suspect Requirements with parent/child relationships in requirement documents
Note: The following information explains how to mark individual items as suspect. You can also mark all dependent items as suspect. See Marking all dependent items as suspect, page 82. 1. Click the Links tab when you are viewing or editing an item. 2. Select an item in the Link Details area and click Mark Suspect. The Mark as Suspect dialog box opens.
3. Enter the reason you are marking the item as suspect. For example, you may want to indicate the changes you made that impact the related item. 4. Click OK. The item is marked as suspect.
Marking all dependent items as suspect

If you make changes to an item that may affect related items, you can enter a workflow event to mark all related items as suspect so other users can see that updates are needed. Dependent items are marked as suspect if:
n n
Items are linked using a link definition that allows dependent items to be marked as suspect Requirements are related in parent/child relationships in requirement documents
Note: The following steps use an example workflow event named Mark Suspects. Your organization may use different events to mark items as suspect. 1. Select an item and choose Activities > Mark Suspects.
82
In ve st igat in g su sp e ct d e p e n d e n cie s
The Mark Suspects dialog box opens.
2. Select a Marked By user. This field defaults to the logged in user. 3. Select Mark dependent items as suspect if you want to mark all linked and related items as suspect. If this option is not selected, the Mark Suspects event is added to the selected item, but related items are not marked as suspect. 4. The Date defaults to the current date and time. You can enter another date and time. 5. Enter any Notes. It is helpful to explain the change that is causing the related items to become suspect. 6. Click OK.
Investigating suspect dependencies

Items marked as suspect need to be reviewed because a related item changed. You can view the dependent items that caused the item to be marked as suspect and clear the suspect item if it does not need changes. 1. Select an item marked as suspect. A flag is displayed on items marked as suspect. 2. Choose Activities > Investigate Suspect Dependencies. The Investigate Suspect Dependencies dialog box opens. All items that are causing the item to be suspect are displayed. The Summary column displays the summary from the related item if the item was marked as suspect using a workflow event. If the item was manually marked as suspect, the column value is <manually marked as suspect>. Tip: You can also click the suspect flag displayed on items to view the dependencies.
83
Cl e ar in g su sp e ct it e ms
3. Select an item to view information entered when the item was marked as suspect in the Details area. 4. Select an item and click View Item to view it. 5. Select an item and click Clear Suspect to indicate that the item is no longer suspect. See Clearing suspect items, page 84. 6. Click Close to close the Investigate Suspect Dependencies dialog box.
Clearing suspect items

After you make changes to a suspect item or determine that changes are not needed, you can clear the suspect flag from the item. Suspect items are automatically cleared if:
n
A requirement marked as suspect based on a parent/child relationship in a requirement document is moved in the document. An item used as the source to mark all dependent items as suspect is removed from a link. A user with security permissions to edit links, but not clear suspects, removes an item from a link that is causing other items to be marked as suspect.
n n
1. Click the Links tab when you are viewing or editing an item. Note: You can also clear suspects in the Investigate Suspect Dependencies dialog box. See Investigating suspect dependencies, page 83. 2. Select an item marked as suspect in the Link Details area and click Clear Suspect. The item is no longer marked as suspect.
Updating Multiple Items

If you need to change the same information in a large number of items, use bulk changes instead of manually editing each record. For example, you may need to change the priority of 50 issues from low to high. Instead of editing each issue, you can use bulk changes to update the records simultaneously. The information you can change depends on the item type and your security permissions.
84
Ch an gin g b u l k fie l d s
Item type Issues
Bulk change fields General, reported by, steps to reproduce, computer config, events, custom fields General, events, custom fields
Security notes The Bulk Change Issues, Edit Issues, and Edit Issues Assigned To Anyone security commands must be enabled to access this command. The Edit Closed Issues security command must be enabled to change closed issues.
Requirements
The Bulk Change Requirements, Edit Requirements, and Edit Requirements Assigned To Anyone security commands must be enabled to access this command. The Edit Closed Requirements security command must be enabled to change closed requirements. Locked requirements cannot be changed. The Bulk Change Requirement Documents, Edit Requirement Documents, and Edit Requirement Documents Assigned To Anyone security commands must be enabled to access this command. The Edit Closed Requirement Documents security command must be enabled to change closed requirement documents. Locked requirement documents cannot be changed. The Bulk Change Test Cases, Edit Test Case, and Edit Test Cases Assigned To Anyone security commands must be enabled to access this command. The Edit Closed Test Cases security command must be enabled to change closed test cases. The Bulk Change Test Runs, Edit Test Runs, and Edit Test Runs Assigned To Anyone security commands must be enabled to access this command. The Edit Closed Test Runs security command must be enabled to change closed test runs.
General, events, custom fields
Test cases
General, step, event, test variant
Test runs
General, events
Changing bulk fields

Bulk changes allows you to simultaneously update field values in multiple items. See Updating Multiple Items, page 84. 1. Select the items you want to update on the list window. For example, if you need to change the priority for a set of issues, select the issues on the Issues list window. Make sure you only select items with records that you want to update. There is no undo available for bulk field changes. 2. Choose Activities > Bulk Changes. The Bulk Changes dialog box opens.
85
Ch an gin g t e st var ian t val u e s
Note: The menu name and dialog box name change based on the selected item type. For example, if you are updating issues, the menu is Activities > Bulk Field Changes and the dialog box title is Bulk Field Changes. 3. Click the tab that includes the field types you want to update. For example, click the Reported by tab to update the Date Found field for a list of issues.
4. Make any changes. The available options depend on the field type.
n n n n
To set the field to a new value, select Set to value and enter a value. To add text to the beginning of a text field value, select Prepend and enter the text. To add text to the end of a text field value, select Append and enter the text. To replace a text field value, select Replace and enter the text you want to search for. Enter the replacement text in the With field. Note: If you are updating issues with multiple records, and you are changing Reported By, Steps to Reproduce, or Computer Config values, select Apply changes to all records to change all records. If you do not select this option, only the first reported by record is changed. If you are updating any item type and you are changing Event values, select Apply to all events to change all item events. If you do not select this option, only the most recent event is updated.
5. Click OK. You are prompted to confirm the changes. 6. Click Yes. The records are updated.
Changing test variant values

You can add actions to add, remove, or set the included or excluded test variant values. For example, if an application no longer supports a database, you can add a Remove action to remove the database as an included test variant value so test runs are no longer generated for it. 1. Select the test cases you want to change. 2. Choose Activities > Bulk Test Case Changes. The Bulk Test Case Changes dialog box opens.
86
3. Click the Variants tab. 4. Make changes to the Included Test Variant Values.
n
Click Add to add an action to add, remove, or set included variant values. See Changing included test variant values, page 87. Select an action and click Edit to change it. See Changing included test variant values, page 87. Select an action and click Delete to delete it. You are prompted to confirm the deletion.
5. Make changes to the Excluded Test Variant Values.

n
Click Add to add an action to add, remove, or set excluded variant values. See Changing excluded test variant values, page 88. Select an action and click Edit to change it. See Changing excluded test variant values, page 88. Select an action and click Delete to delete it. You are prompted to confirm the deletion.
6. Click OK. You are prompted to confirm the changes. 7. Click Yes. The test cases are changed.
Changing included test variant values

You can add actions to change included test variant values, which are always used when test runs are generated. 1. Select the test cases you want to change. 2. Choose Activities > Bulk Test Case Changes. The Bulk Test Case Changes dialog box opens. 3. Click the Variants tab. 4. Click Add to add an action or select an action and click Edit to change it. The Change Included Test Variant Values dialog box opens.
5. Select an Action.
87
Select Add test variant values to add the values to the test cases. When test runs are generated, the new values plus any existing included variant values are used. Remove test variant values to remove the values from the test cases. Test runs will not be generated for the selected values. Select Set test variant values to set the values on the test cases. Test runs will always be generated for the selected values.
6. Select the Included variant. 7. Select the Values to change. Note: If you selected Set test variant values and do not select any values to change, the variant is removed from the list of included test variants. 8. Click OK. You return to the Bulk Test Changes dialog box. 9. Click OK. You are prompted to confirm the changes. 10. Click Yes. The test cases are changed.
Changing excluded test variant values

You can add actions to change excluded test variant values, which are never used when test runs are generated. 1. Select the test cases you want to change. 2. Choose Activities > Bulk Test Case Changes. The Bulk Test Case Changes dialog box opens. 3. Click the Variants tab. 4. Click Add to add an action or select an action and click Edit to change it. The Change Excluded Test Variant Values dialog box opens.
5. Select an Action.
88
Imp or t in g an d Exp or t in g Dat a
Select Add test variant values to add the values to the test cases. When test runs are generated, the new values plus any existing excluded test variant values are not used. Select Remove test variant values to remove the values from the test cases. Test runs will be generated for the selected values. Select Set test variant values to set the values on the test cases. Test runs will not be generated for the selected values.
6. Select an Excluded variant. 7. Select the Values to change. Note: If you selected Set test variant values and do not select any values to change, the variant is removed from the list of included test variants. 8. Click OK. You return to the Bulk Test Case Changes dialog box. 9. Click OK. You are prompted to confirm the changes. 10. Click Yes. The test cases are changed.
Importing and Exporting Data

You can export and import TestTrack data in XML or text format for data migration and sharing with thirdparty tools. For example, you may want to export data for use in Excel or another report tool.
About XML import and export

XML format is the recommended method for importing and exporting data. This method includes the following advantages over importing and exporting text files:
n n n n
You do not need to match project fields and data fields. You can import and export multiple issue Reported by records. You can import and export multiple instances of the same item actions. You can import and export more than one item type. For example, you can import/export issues and users in a single file. You can import and export links. You can import and export file attachments associated with items. You can import and export folder information.
n n n
Note: Limit XML import/export access to administrative security groups. Misusing this feature can result in a large number of unwanted records in a project. The import/export command does not enforce other command-level or field-level security options. For example, if users have export security access they can access security group information even if they do not have access to view security groups. Most users do not need access to the import/export commands.
89
Exp or t in g t o X M L
About text file import and export

You can import and export items as comma- and tab-delimited text files. You can also import and export files created in other applications such as FileMaker Pro. The recommended import/export method is XML. Note: Limit import/export access to administrative security groups. Misusing this feature can result in a significant number of unwanted items in your project. The import/export command does not enforce other command-level or field-level security options. For example, if users have export security access they can access security group information even if they do not have access to view security groups. Most users do not need access to the import/export commands.
Exporting to XML
You can export issues, requirements, requirement documents, test cases, test runs, folders, users, customers, security groups, and test configurations to an XML file. Keep the following in mind:
n
The status and assigned to fields can be exported but not imported. These fields are exported so you can use the data with a third-party application. The found and assigned fields are exported but not imported. Links can be exported but the link definition must already exist in the project you are importing to. At least two items associated with the link must be exported. Folder information can be exported but the folders must already exist with the same path in the project you are importing to. Usernames and passwords are both exported. Usernames are exported in plain text; passwords are always exported as encrypted text. You can export security groups and compare two or more exported XML files in a third-party differences utility to view differences between groups or changes to a group over time. Custom fields cannot be exported.
n n
1. If you only want to export specific items, select the items to export.
n
To export multiple items, select them in the list window. You can only export from one list window at a time. To export one item, select it in the list window or open it. Make sure you save any changes to the open item before exporting.
2. Choose File > Export > XML Export. The XML Export dialog box opens.
90
Exp or t in g t o X M L
3. Select the type of information you want to export.

n
Export only the selected items exports items selected in the list window. This option is only available if you selected items in a list window before you started the export process. Export only the open item exports the contents of the selected open item. This option is only available if you started the export process with an open item dialog box selected. Export all of the following information exports all the item types in selected in the list. To export multiple item types, Ctrl+click each type to include.
4. Select any Export Options. Most export options are only available for issues, requirements, requirement documents, test cases, and test runs.
n
Select Export historical log information to export a historical account of changes made to each exported record. Select Export file attachments to include file attachments associated with exported records. Records and file attachments are exported to a ZIP file. Select Export formatting and images for WYSIWYG fields to include text formatting and images used in multi-line text fields. Formatted items and images are exported to a ZIP file. Select Export links to include links associated with exported items. Select Export email messages to include tracked emails with exported items. Select Export folder information to include the path of the public folders that exported items are included in. Private folders are not exported.
n n n
5. Click Export. The Export XML File dialog box opens.
91
Imp or t in g X M L fil e s
6. Select the file location, enter a file name, and click Save. The progress is displayed as items are exported.
Importing XML files

You can import issues, requirements, requirement documents, test cases, folders, users, customers, and test configurations from an XML file that was exported from another TestTrack project. Keep the following in mind:
n
Refer to the TestTrackData.dtd file for formatting of your XML file. Do not modify the TestTrackData.dtd file. Modifying this file may result in validation errors or errors importing XML data. Leave <not set> elements empty. Special characters such as &, <, >, , and cannot be imported. You must replace these characters with their corresponding entity reference before importing. For example, & must be replaced with &. Control characters cannot be imported. When a user field, such as Fixed By, is imported, TestTrack tries to match the first name and last name with an existing user or customer. If an exact match is not found, the user or customer is created. Historical data is not imported. Historical data fields are system-generated. The Created by and Modified by fields are populated with the currently logged in users name. The Date created and Date last modified fields are populated with the current date and time. The Creation method field is populated with XML file import. Links cannot be imported unless the link definition already exists in the project and at least two of the items included in the link are in the XML file. Items cannot be added to folders unless the folders already exist in the same location as the project the items were exported from. When imported, the password field can be either encrypted or in plain text. If TestTrack generated the XML file, the password is encrypted. If a third-party XML file is imported, the password is in plain text.
n n
n n
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. The selected file is listed in the Import File area on the XML Import dialog box.
92
Exp or t in g t o t e xt fil e s
4. Select a Number Import option.

n
Assign the next available number automatically assigns the next available number for imported item. Import number field information imports number information from the XML file. If the number already exists, an error is generated and the item is not imported. Tip: The Number Import options may be disabled depending on project options.
5. Select a Pop-up Menu Item option. These options apply to pop-up menu fields, such as Priority, and do not apply to user fields.
n n
Add the pop-up menu item to the project automatically adds the menu item to the project. Use the default value uses the default value and ignores any value in the imported XML file.
6. Click Validate XML File to validate the file. Resolving problems before importing is much easier than cleaning up data in the TestTrack project. If there is a problem with the file format, the XML Import Warning and Errors dialog box opens. Click Save As to save the contents of the Warnings and Errors dialog box as a text file. Note: A warning means the item can be imported but some of the information could not be imported, while an error means the item cannot be imported. 7. Click Import to import the items. The items are imported. The XML Import dialog box closes and you return to the list window.
Exporting to text files

To export a limited set of items, select the items on the list window before selecting the export settings.
93
Exp or t in g t o t e xt fil e s
Note: Custom fields cannot be exported. 1. Choose File > Export > Text File Export. The Text Export dialog box opens.
2. Select the item type you want to export from the Export fields list. If you have an export template that matches the file format, click Load to load it and skip to step 6. 3. Select the fields to export. 4. Repeat steps 2 and 3 for all item types you want to export. 5. Select the Export Options.
n n n n n
Select Export selected records only to only export items selected in the list window. Select Include column headings to export the column headings. Select Convert EOLs to spaces to convert carriage returns and line feeds to spaces. Select a Delimiter character to insert between fields. Select the Date Format to use in the exported items. Client locale uses the locale set on the computer running the TestTrack Client and Server locale uses the locale set on the computer running the TestTrack Server. Decimal points are always exported as periods. Note: If you want to save the settings for future exports, click Save to create a text file export template. See Creating text file export templates, page 95.
6. Click Export. The Export File dialog box opens. 7. Select the file location and enter a file name.
94
Cr e at in g t e xt fil e e xp or t t e mp l at e s
8. Click Save. The progress is displayed as items are exported.
Creating text file export templates

If you export text files with the same field layout often, save the format as a template. 1. Set up the fields as described in Exporting to text files, page 93. 2. Click Save in the Export Templates area on the Text Export dialog box. The Save Export Template dialog box opens. 3. Select the file location and enter a file name. 4. Click Save. You return to the Text Export dialog box.
Using text file export templates

1. Choose File > Export > Text File Export. The Text Export dialog box opens. 2. Click Load in the Export Templates area. The Load Export Template dialog box opens. 3. Select the export template and click Open. The template is loaded and you return to the Text Export dialog box. 4. Click Export to start the export.
Importing text files

You can import text files that were exported from other TestTrack projects. 1. Choose File > Import > Text File Import. The Text Import dialog box opens. 2. Select the field type you want to import from the Import fields list. 3. Click Browse to select a file to import. The Open dialog box opens. 4. Select the file you want to import. 5. Click Open. The Select Code Page dialog box opens.
6. Select a character set and click OK.
95
Imp or t in g t e xt fil e s
The Text Import dialog box opens.
7. Select the Import options.

n n
Select Ignore first record to ignore the first record, which often contains field names. Select Handle quoted text if the program used to export records supports quoting fields. When a file is exported from a project, quotes are often inserted around comma- and tab-delimited records. Select Map vertical tab to return to restore the formatting of multi-line fields. Some applications map carriage returns in multi-line fields to vertical tab characters. Select the Delimiter character used to between fields.
8. Match the TestTrack fields in the right column to the fields in the left column.
n
The column on the left displays the fields as they appear in the file. Click the Previous and Next arrows to move from record to record. Click and drag the fields in the right column up or down to the reorder them. If you cannot find an exact match, use the closest equivalent.
9. Select the fields to import. To select a field, click in the middle column next to the field. A check mark is displayed next to selected fields. Click again to deselect the field. 10. Click Import. The fields are imported. Email notifications are not sent when you import files because a large number of emails could crash some email servers.
96
Cr e at in g t e xt fil e imp or t t e mp l at e s
Note: If you are going to reuse this layout, create a text file import template to save time.
Creating text file import templates

If you import text files with the same field layout often, save the format as a text file import template. 1. Map the fields as described in Importing text files, page 95. 2. Click Save in the Import Templates area on the Import dialog box. The Save Import Template dialog box opens. 3. Select the file location and enter a file name. 4. Click Save. The Import Template is saved. You return to the Text Import dialog box.
Using text file import templates

1. Choose File > Import > Text File Import. The Text Import dialog box opens. 2. Click Load in the Import Templates area on the Import dialog box. The Load Import Template dialog box opens. 3. Select the import template and click Open. The template is loaded. You return to the Text Import dialog box.
Creating Filters
TestTrack includes extensive filtering capabilities. You can use filters to sort records and list only those records that meet the criteria you select.
Adding Filters
Use filters to sort project information and view selected records. Filters can be private, shared with everyone, users, customers, and selected security groups, or published to be used as RSS feeds. For example, a project team lead may create a private filter that allows her to view a team members issue list. Or, she may create a shared filter that allows development team members to view the enhancement requests that customers request. 1. Click Add on the Filters list window. The Select Filter Type dialog box opens. 2. Select the filter type and click OK. The Add Filter dialog box opens.
97
Ad d in g Fil t e r s
3. Enter a Name and Description. 4. Select a Share option.

n n n n n n
Select Private to restrict other users from using the filter. Select Shared with Everyone to share the filter with all users and customers. Select Shared with Users to share the filter with other users. Select Shared with Customers to share the filter with customers. Select Shared with Security Groups to share the filter with selected security groups. Select Publish to create an RSS feed based on the filter. See Creating RSS Feeds, page 153.
5. Click Add to add a filter restriction. You can add up to 20 restrictions to a filter. See Adding Restrictions, page 99. Select Prompt for restriction information at run time in the Add Restriction dialog box 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. You may want to select this option if the restriction information changes frequently so you do not have to edit the filter. See Using interactive filters, page 30. Note: If this option is selected, the filter cannot be used in automation rules, user notification rules, or security groups, and cannot be published. 6. Optionally select NOT/AND/OR operators and parentheses to build Boolean logic for the filter. See About Boolean searches, page 99. 7. Click Validate to validate the filter criteria.
98
Ad d in g Re st r ict ion s
n n
Click OK if the filter criteria is valid. An error message opens if the filter criteria is not valid. Click OK to return to the Add Filter dialog box and correct the error. Click Clear to clear all restrictions and start over.
8. Click Add. The filter is added. Note: Click Apply to save the changes without closing the Add Filter dialog box.
About Boolean searches

You can use Boolean logic to create complex and highly precise filters. Boolean logic uses three connecting operators (AND, OR, NOT) to narrow or broaden a search or to exclude a term from a search. Boolean operators can also be used with parentheses, which allow you to create even more complex queries. The AND operator is used to narrow searches. When you use this operator, the filter or search returns records that match all of the criteria you choose. The OR operator is used to broaden searches. When you use this operator, the filter or search returns records that match any of the criteria you choose. The NOT operator is used to limit searches by eliminating terms from a search. When you use this operator, the filter or search returns records that do not contain any of the criteria you choose.
Adding Restrictions
Restrictions are criteria that files must meet to be included in filter and advanced find results. You can combine multiple restrictions to narrow the number of returned records. For example, you can create restrictions to find issues with a specific severity level that were last modified within a specific number of days. You can add up to 20 restrictions to a filter or advanced find. You add a variety of restrictions based on field values, link information, and other record attributes. You can also create restrictions based on workflow events, which can search the first or last instance of an event entered on a record or all instances of the event. TestTrack includes the following types of restrictions. Type Text Limits results to: Records with text that does or does not match all, any, or the exact text you enter or text that includes wildcards. See Adding text restrictions, page 100. Records with version values that do or do not match a specific version range or any, all, or the exact version you enter. See Adding string range restrictions, page 102. Records with dates that do or do not match a date range, date/time range, or time period. See Adding date range restrictions, page 104.
String range
Date range
99
Type Integer
Limits results to: Records with non-decimal numbers that do or do not match numbers in a range or list. See Adding integer restrictions, page 105. Records with decimal numbers that do or do not match numbers inside or outside of a specific range. See Adding decimal number restrictions, page 106. Records with pop-up menus that contain or do not contain a specific selected value. Applies to pop-up menus that allow only one selection. See Adding single list selection restrictions, page 108. Records with pop-up menus that do or do not contain any, all, or exactly the values selected. Applies to pop-up menus that allow multiple selections. See Adding multiple list selection restrictions, page 109. Records with check box fields that are selected or cleared or records with or without specific attributes. See Adding condition restrictions, page 110. Records with user fields that do or do not contain specific users, users in specific security groups, or users in a specific company, division, or department. See Adding user restrictions, page 111. Records that are or are not in any, all, or only the selected folders or child folders. See Adding folder restrictions, page 113. Requirements that are or are not in any, all, or only the selected requirement documents. See Adding requirement document restrictions, page 115. Test cases that do or do not contain any, all, or only selected values as included or excluded test variant values. You can also limit results by supported test variants to find test cases that do not explicitly include or exclude selected values. See Adding test variant value restrictions, page 116.
Decimal number Single list selection
Multiple list selection
Condition
User
Folder
Requirement document Test variant value
Adding text restrictions

Text field restrictions limit results to records that do or do not contain all, any, or the exact text you enter. For example, you can create a restriction based on the issue Summary field to find all issues that contain web server. 1. Click Add on the Add Filter, Edit Filter, or Advanced Find dialog box. The Add Restriction dialog box opens. 2. If you are creating a filter restriction, 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. You may want to select this option if the restriction information changes frequently so you do not have to edit the filter. The information you enter when creating the restriction is used by default in the wizard. See Using interactive filters, page 30.
100
Note: If this option is selected, the filter cannot be used in automation rules, user notification rules, or security groups, and cannot be published. 3. Select a field from the Restrict by list. The restriction options you can set change based on the selected field. You can also select additional options to perform a more comprehensive search:
n n n
All Text searches all text fields. See Searching all text fields, page 37. All Event Notes searches all Notes fields in workflow action events, such as Assign and Fix. All Informational Event Notes searches all Notes fields in informational events, such as Comment.
4. If the restriction is for a workflow event, select the Event to Search.

n n n
Select First event to only search the first instance of the event entered on the record. Select Last event to only search the last instance of the event entered on the record. Select All events to search all instances of the event entered on the record.

n n
Select Matches the following to search for records that contain the text. Select Does not match the following to search for records that do not contain the text.
6. Enter the text you want to search for. You can enter a text string or text that includes the following wildcards:
101
n n
Use an asterisk (*) to match zero or more characters. Use a question mark (?) to match one character.
7. Select the type of search from the Use list.

n n
Select Plain Text Search to search for the exact text. Select Wildcards to perform a wildcard search.

n n n
Select Match phrase to search for the exact phrase. Select Match any search term to search for any of the search terms. Select Match all search terms to search for all of the search terms. Note: See Search examples, page 38 for examples.
9. Select Match case to match the case of the text. 10. Click OK to add the restriction.
Adding string range restrictions

Range restrictions, which are based on version values and ranges, limit results to records that do or do not contain a specific version range or any, all, or the exact version you enter. For example, you can create a restriction based on the Version Found field to find all issues found in releases 4.0.0 through 4.1.5. 1. Click Add on the Add Filter, Edit Filter, or Advanced Find dialog box. The Add Restriction dialog box opens. 2. Select a field from the Restrict by list. The restriction options you can set change based on the selected field.
102
3. If you are creating a filter restriction, 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. You may want to select this option if the restriction information changes frequently so you do not have to edit the filter. The information you enter when creating the restriction is used by default in the wizard. See Using interactive filters, page 30. Note: If this option is selected, the filter cannot be used in automation rules, user notification rules, or security groups, and cannot be published. 4. If the restriction is for a workflow event, select the Event to Search.
n n n

n n
Select Matches the following to search for records that contain the range or value. Select Does not match the following to search for records that do not contain the range or value.
6. Select the type of value to search for and enter the value.
n n
Select Range to search a range of values. Enter the From and through values. Select String to search for a specific value. Enter the value to search for. Note: You can search for ranges greater than or less than a specific value. Leave the From field empty to search for matches less than the value in the through field. Leave the through field empty to search for matches greater than the value in the From field.
7. If you entered a string, select the type of search to use.

n n
Select Plain Text Search to search using the exact value. Select Wildcards to perform a wildcard search.
8. If you entered a string, select a matching option.

n n n
Select Match phrase to search for the exact phrase. Select Match any search term to search for any of the search terms. Select Match all search terms to search for all of the search terms. Note: See Search examples, page 38 for information.
9. If you entered a string, select Match case to match the case of the text. 10. Click OK to add the restriction.
103
Adding date range restrictions

Date range restrictions limit results to records that do or do not contain a date range, date/time range, or time period. For example, you can create a restriction based on the Date Entered field to find issues entered in the past month. 1. Click Add on the Add Filter, Edit Filter, or Advanced Find dialog box. The Add Restriction dialog box opens. 2. Select a field from the Restrict by list. The restriction options you can set change based on the selected field.
n n n
5. Select an option to indicate if the results meet the specified dates and times.
104
If the selected field only contains a date, select Matches the following dates to search for records that contain the selected dates. Select Does not match the following dates to search for records that do not contain the selected dates. If the selected field contains a date and time, select Matches the following dates and times to search for records that contain the selected dates and times. Select Does not match the following dates and times to search for records that do not contain the selected dates and times.
6. Select the time period to search.

n n
Select From date to search a specific date range. Enter the range. Select From date/time to search a specific date/time range. Enter the range. This option is only available for date/time fields. Select a time period option to search a specific period, such as last week or last year. This option is only available for date fields that include the time, such as event date/time fields. Select In the to search a specified number of days, weeks, months, or years before or after the current date. Select Last or Next, enter a number, and select the time period.
7. Click OK to add the restriction.
Adding integer restrictions

Integer restrictions, which are based on non-decimal numbers, limit results to records that do or do not contain numbers in a range or list. For example, you can create a restriction based on the test case number that returns all test cases numbered from 200 to 400. 1. Click Add on the Add Filter, Edit Filter, or Advanced Find dialog box. The Add Restriction dialog box opens. 2. Select a field from the Restrict by list. The restriction options you can set change based on the selected field.
3. If you are creating a filter restriction, select Prompt for restriction information at run time to be prompted to enter restriction information when the filter is applied.
105
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. You may want to select this option if the restriction information changes frequently so you do not have to edit the filter. The information you enter when creating the restriction is used by default in the wizard. See Using interactive filters, page 30. Note: If this option is selected, the filter cannot be used in automation rules, user notification rules, or security groups, and cannot be published. 4. If the restriction is for a workflow event, select the Event to Search.
n n n

n n
Select Matches the following to search for records that contain the numbers. Select Does not match the following to search for records that do not contain the numbers.
6. Select the type of value to search for and enter the value.
n n
Select Range to search a range of values. Enter the From and to values. Select Any of the following numbers to search for multiple numbers. Enter the numbers to search for, separated with spaces or commas. Tip: You can search for ranges greater than or less than a specific value. Leave the From field empty to search for matches less than the value in the to field. Leave the to field empty to search for matches greater than the value in the From field.
Adding decimal number restrictions

Decimal number restrictions limit results to records that do or do not contain numbers inside or outside of a specific range. For example, you can create a restriction to find records with 2.5 hours or less in the Estimated Effort field for the Estimate event. 1. Click Add on the Add Filter, Edit Filter, or Advanced Find dialog box. The Add Restriction dialog box opens. 2. Select a field from the Restrict by list. The restriction options you can set change based on the selected field.
106
n n n
5. Select a range option.

n n
Select Is within the range to search for records that contain the numbers in the range. Select Is not within the range to search for records that do not contain the numbers in the range.
6. Enter the range of numbers to search for in the From and to fields. Tip: You can search for ranges greater than or less than a specific number. Leave the From field empty to search for matches less than the value in the to field. Leave the to field empty to search for matches greater than the value in the From field. 7. Click OK to add the restriction.
107
Adding single list selection restrictions

Single list selection restrictions, which are based on pop-up menu fields that only allow one selection, limit results to records that contain or do not contain a specific value selected in a menu. For example, you can create a test case restriction to find records with the Regression value selected in the Type field. 1. Click Add on the Add Filter, Edit Filter, or Advanced Find dialog box. The Add Restriction dialog box opens. 2. Select a field from the Restrict by list. The restriction options you can set change based on the selected field.
n n n
108
5. Select an option to indicate if the results contain the selected values.

n n
Select Contains the following items to search for records that contain the values. Select Does not contain the following items to search for records that do not contain the values.
6. Select the values to search for. Click Select All to select all values or click Select None to clear any selected values. 7. Click OK to add the restriction.
Adding multiple list selection restrictions

Multiple list selection restrictions limit results to records that contain or do not contain any, all, or exactly the values selected in a pop-up menu. For example, you can create an issue restriction to find records with specific values selected in the Product field. 1. Click Add on the Add Filter, Edit Filter, or Advanced Find dialog box. The Add Restriction dialog box opens. 2. Select a field from the Restrict by list. The restriction options you can set change based on the selected field.
3. If you are creating a filter restriction, 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. You may want to select this option if the restriction information changes frequently so you do not have to edit the filter. The information you enter when creating the restriction is used by default in the wizard. See Using interactive filters, page 30.
109
Note: If this option is selected, the filter cannot be used in automation rules, user notification rules, or security groups, and cannot be published. 4. If the restriction is for a workflow event, select the Event to Search.
n n n

n n
Select Contains to search for records that contain the values. Select Does not contain to search for records that do not contain the values.
6. Select an option to indicate how to search for the selected values.

n n n
Select Any of the following items to search for records with one or more of the values. Select All of the following items to search for records with all of the values. Select Exactly the following items to search for records only with the values.
7. Select the values to search for. Click Select All to select all values or click Select None to clear the selected values. 8. Click OK to add the restriction.
Adding condition restrictions

Condition restrictions limit results to records with check box fields that are selected or cleared, or records with or without specific attributes. For example, you can create a restriction to find all issues with file attachments. 1. Click Add on the Add Filter, Edit Filter, or Advanced Find dialog box. The Add Restriction dialog box opens. 2. Select a field from the Restrict by list. The restriction options you can set change based on the selected field.
110
n n n
5. Select an option to indicate the condition to use for the search. For example, if the Fix Affects Documentation restriction is selected, select Affects Documentation is selected to find issues with the check box selected in the Fix event dialog box. 6. Click OK to add the restriction.
Adding user restrictions

User restrictions, which are based on user fields such as Found by or event assignment fields, limit results to records that do or do not contain specific users, users in specific security groups, or users in a specific company, division, or department. For example, you can create a restriction to find issues entered by users in the Quality Assurance security group. Note: Users restrictions also apply to customers. 1. Click Add on the Add Filter, Edit Filter, or Advanced Find dialog box. The Add Restriction dialog box opens. 2. Select a user field from the Restrict by list. The restriction options you can set change based on the selected field.
111
n n n

n n
Select Contains the following to search for records that contain the values. Select Does not contain the following to search for records that do not contain the values.
6. Select the category to search on.
112
n n n
Users is selected by default. This option allows you to search for specific users by name. Select Security Groups to search by specific security groups. Select Company to search by a specific company, department, and division. Tip: You can only use one category per restriction. For example, you cannot use one restriction to search based on security group and company. You must create multiple restrictions to search on a combination of users, security groups, or company.
7. Select an option to indicate how to search for the selected values. This option is only available for multiple list selection user fields.
n n n
Select Any of the following items to search for records with one or more of the values. Select All of the following items to search for records with all of the values. Select Exactly the following items to search for records only with the values.
8. Select the values to search for.

n
If you are creating a users restriction, you can select <current user> to search for the logged in user. Select <Unknown> to search for records with <not set> or <Unknown> selected in user fields. A field may be set to Unknown if a user was selected in the field but was later deleted from the project. If you are creating a security groups restriction and want to search for users that are not in a security group, select <not set>. If you are creating a company restriction, note that the values in the Division field are based on the selected Company value, and the values in the Department field are based on the selected Division value. Select <Any Company>, <Any Division>, or <Any Department> to perform a more extensive search. Select <not set> to search for users without company, division, or department information in their user records. Note: If Users is selected, click Find to search for users. See Finding users and customers, page 39. If Users or Security Groups is selected, click Select All to select all values or click Select None to clear any selected values.
Adding folder restrictions

Folder restrictions limit results to records that are or are not in any, all, or only the selected folders or child folders. For example, you can create a restriction to find test runs that are in the Windows folder. 1. Click Add on the Add Filter, Edit Filter, or Advanced Find dialog box. The Add Restriction dialog box opens. 2. Select Folders from the Restrict by list.
113
3. If you are creating a filter restriction, 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. You may want to select this option if the restriction information changes frequently so you do not have to edit the filter. The information you enter when creating the restriction is used by default in the wizard. See Using interactive filters, page 30. Note: If this option is selected, the filter cannot be used in automation rules, user notification rules, or security groups, and cannot be published. 4. Select an option to indicate where to search for records in the selected folders.
n n
Select Resides in to search for records that are in the folders. Select Does not reside in to search for records that are not in the folders.
5. Select an option to specify how to search for the values.

n n n
Select Any of the following items to search any of the folders. Select All of the following items to search all of the folders. Select Exactly the following items to only search the folders.
6. Select Search recursively to search all child folders in the selected folders. 7. Select the folders to search. Click Select All to select all folders or click Select None to clear the selected folders. 8. Click OK to add the restriction.
114
Adding requirement document restrictions

Requirement document restrictions limit results to requirements that are or are not in any, all, or only the selected requirement documents. For example, you can create a restriction to find requirements that are in multiple requirement documents. 1. Click Add on the Add Filter, Edit Filter, or Advanced Find dialog box. The Add Restriction dialog box opens. 2. Select Requirement Documents from the Restrict by list.
3. If you are creating a filter restriction, 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. You may want to select this option if the restriction information changes frequently so you do not have to edit the filter. The information you enter when creating the restriction is used by default in the wizard. See Using interactive filters, page 30. Note: If this option is selected, the filter cannot be used in automation rules, user notification rules, or security groups, and cannot be published. 4. Select an option to indicate where to search for requirements in the selected requirement documents.
n n
Select Resides in to search for requirements that are in the requirement documents. Select Does not reside in to search for requirements that are not in the requirement documents.
5. Select an option to specify how to search for the values.

n n n
Select Any of the following items to search any of the folders. Select All of the following items to search all of the folders. Select Exactly the following items to only search the folders.
115
6. Select the requirement documents to search. Click Select All to select all folders or click Select None to clear the selected folders. 7. Click OK to add the restriction.
Adding test variant value restrictions

Test variant value restrictions limit results to test cases that do or do not contain any, all, or only selected values as included or excluded test variant values. You can also limit results by supported test variant values, which finds test cases that do not explicitly include or exclude selected values. For example, you can create a restriction based on the Platform test variant to find test cases with Windows as an included test variant value. 1. Click Add on the Add Filter, Edit Filter, or Advanced Find dialog box. The Add Restriction dialog box opens. 2. Select the test variant you want to include in the restriction from the Restrict by list. The restriction options you can set change based on the selected test variant.
3. If you are creating a filter restriction, 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. You may want to select this option if the restriction information changes frequently so you do not have to edit the filter. The information you enter when creating the restriction is used by default in the wizard. See Using interactive filters, page 30. Note: If this option is selected, the filter cannot be used in automation rules, user notification rules, or security groups, and cannot be published. 4. Select the type of test variant values to search.
116
Ed it in g fil t e r s
Select Included Test Variant Values to search for test cases with the selected values added as included test variant values. Select Excluded Test Variant Values to search for test cases with the selected values added as excluded test variant values. Select Supported Test Variant Values to search for test cases that support the selected values. Supported test variant values are not excluded values, but may not be included values.
5. Select an option to indicate if the results contain the selected variant values.
n n
Select Contains to search for test cases that contain the variant values. Select Does not contain to search for test cases that do not contain the variant values.
6. Select an option to indicate how to search for the selected values.

n
Select Any of the following items to search for test cases that contain one or more of the variant values. Select All of the following items to search for test cases that contain all the variant values. Select Exactly the following items to search for test cases that contain only the variant values.
n n
7. Select the variant values to search for. Click Select All to select all values or click Select None to clear all any selected values. 8. Click OK to add the restriction.
Editing filters
1. Select the filter on the Filters list window. 2. Choose Edit > Edit Filter. The Edit Filter dialog box opens. 3. Make any changes and click OK. If the filter is used in automation rules, reports, or security groups, you are prompted to save the changes.
Editing restrictions
1. Select the restriction on the Add Filter, Edit Filter, or Advanced Find dialog box. 2. Click Edit. The Edit Restriction dialog box opens. Note: The Prompt for restriction information at run time option is disabled if the restriction is included in a filter used in automation rules, user notification rules, or security groups, or if the filter is published. 3. Make any changes and click OK. The changes are saved.
117
In se r t in g r e st r ict ion s
Inserting restrictions
If a filter or search includes a large number of restrictions, you can insert a restriction in a specific position. 1. Select the restriction on the Add Filter, Edit Filter, or Advanced Find dialog box. The new restriction is added above the selected restriction. 2. Click Insert. The Insert Restriction dialog box opens. 3. Select a field from the Restrict by list. The restrictions you can set change based on the selected field. 4. Select the restriction options. 5. Click OK. The restriction is inserted.
Duplicating filters
If you add filters with the same information, you can save time by duplicating and editing an existing filter. 1. Select the filter you want to duplicate. 2. Choose Edit > Duplicate Filter. The filter is duplicated and a number is added to the end of the filter name. For example, if you duplicate Priority Filter twice, the duplicated filters are named Priority Filter 1 and Priority Filter 2. 3. Modify the duplicated filter and save the changes.
Deleting restrictions
Make sure you want to delete the restriction. You are not prompted to confirm the deletion and the action cannot be undone. 1. Select the restriction on the Add Filter, Edit Filter, or Advanced Find dialog box. 2. Click Delete. The restriction is deleted.
Deleting filters
You cannot delete filters used in automation rules and security groups. If you want to delete the filter, you must first change the filter used in the automation rule or security group. 1. Select the filter on the Filters list window and click Delete. You are prompted to confirm the deletion. 2. Click Delete. The filter is deleted.
118
Cr e at in g Re p or t s
Creating Reports
Reports are useful for tracking the status of projects and analyzing the data collected in a TestTrack project. You can build reports that include the specific information you need. For example, you can see who reported the most issues, how many issues are open, and how much time was spent resolving issues. You can share reports with other users or keep them private. TestTrack includes several built-in reports. You can also add reports from external reporting tools that can be viewed from TestTrack. See Report types, page 119.
Report types
TestTrack includes the following built-in reports. Report type Detail Displays: Detailed information for individual issues, requirements, requirement documents, test cases, test runs, folders, customers, users, security groups, or test configurations in a project. The allocation of issues, requirements, requirement documents, test cases, or test runs in a project. Use this report to view the count of currently assigned issues by product, status by priority, severity by version, and more. You can add a chart to display data as a count or percentage. Selected fields from issues, requirements, requirement documents, test cases, test runs, folders, customers, users, security groups, or test configurations in rows and columns. You can add a chart to display data as a count or totals. Issue, requirement, requirement document, test case, or test run workflow events entered over time. Use this report to determine the efficiency of a project. You can add a chart to display items in a timeline. Project information in a chart format that is updated automatically when items in the project change. Can include one or more item types or items in a specific folder. Live charts can be displayed in the Folders list window or in a standalone window. See Live chart types, page 145. Detailed information that helps with planning a project, release, or iteration. See Release planning reports, page 120. Detailed information that helps with tracking and communicating the status or progress of a project, release, or iteration. See Release status reports, page 120. Information that helps with tracking and communicating actual work performed on items. See Time tracking reports, page 121. Detailed information that allows you to perform coverage analysis by viewing relationships between requirements and related items in a project. See Traceability reports, page 121.
Distribution
List
Trend
Live Chart
Release Planning Release Status Time Tracking Traceability
119
Re p or t t yp e s
Note: Reports from external reporting services, such as SQL Server Reporting Services or Crystal Reports, can also be added to TestTrack. External reporting gives you access to more data in the TestTrack project databases, provides more flexibility and control of the report content and layout, and offers more output format options. Ask your TestTrack administrator for additional information about external reporting. See Adding external reports to TestTrack, page 142.
Release planning reports

TestTrack includes the following built-in release planning reports. See Creating release planning reports, page 130. Report name Release Plan Description Assists in the planning of a project by comparing the current estimated effort for items within each folder for a project, release, or iteration to the target goals specified for the iteration in the folders. Estimated effort and goals can be in man hours or story points. Only available if time tracking is used and requires selecting a folder with release planning enabled. Assists in the planning of a project by comparing target goals for the selected folders to the estimated effort for the items in the folders. Organized by the users currently assigned to the items. Only available if time tracking is used and requires selecting a folder with release planning enabled.
Release Allocation
Release status reports

TestTrack includes the following built-in release status reports. See Creating release status reports, page 133. Report name Burn Down Chart Description Displays a graphical representation of work left to do versus time available for the project. The outstanding work, or backlog, is generally displayed on the vertical axis with time on the horizontal axis. Only available if time tracking is used and requires selecting a folder with release planning enabled. Displays a graphical representation of work done versus time available for the project. The completed work, or effort, is generally displayed on the vertical axis with time on the horizontal axis. Only available if time tracking is used and requires selecting a folder with release planning enabled. Displays a graphical representation of the flow of work through development phases over time. The estimated effort for completion of each item is grouped by each development phase (Not Started, In Progress, Done, and Accepted) over time. Only available if time tracking is used and requires selecting a folder with release planning enabled.
Burn Up Chart
Cumulative Flow Chart
120
Re p or t t yp e s
Report name Folder Task Board / Folder Task Board Alternate Style Folder Task Board With Configurable Columns Release Status by Item Release Status by Specification Document Release Status by User Velocity Chart
Description Displays the progress a team is making on tasks for an iteration. Displays columns and rows for each folder in the iteration and organizes the items in folders into columns for their current development phase (Not Started, In Progress, Done, and Accepted). Requires selecting a folder with release planning enabled.
Displays the progress a team is making on tasks for an iteration. Organizes items in configurable columns based on the workflow states mapped to each column. Requires selecting a folder with release planning enabled.
Displays the current progress on items within folders including details on the workflow events that impacted the time tracking information. Only available if time tracking is used and requires selecting a folder with release planning enabled. Displays the current progress on items within the document. Other items linked to the items within the document can be included.
Displays the current progress on items within folders organized by the currently assigned to user. Only available if time tracking is used and requires selecting a folder with release planning enabled. Displays a graphical representation of the amount of work done in each iteration. Velocity is used to measure the rate at which development teams complete development for each iteration. Requires selecting a folder with release planning enabled.
Time tracking reports

TestTrack includes the following built-in time tracking reports. These reports are only available if time tracking fields are used in the project. See Creating time tracking reports, page 135. Report name Time Tracking by Item Time Tracking by User Description Displays the detailed time tracking workflow events for each item selected. Organized by user. Displays the detailed time tracking working events entered by users. Organized by date.
Traceability reports
TestTrack includes the following built-in traceability reports. See Creating traceability reports, page 138.
121
Cr e at in g b u il t -in r e p or t s
Report name Detailed Requirement Forward Traceability Requirement Document Forward Traceability Requirement Document Impact Requirement Folder Coverage Requirement Forward Traceability Requirement Test Case Coverage Requirement Test Run Coverage Test Case Backwards Traceability
Description Displays the relationships between the selected requirements, the test cases and test runs associated with those requirements, and any issues reported for the test cases. It also includes the other requirements and requirement documents each requirement is linked to, and its parent and child requirements. Displays the relationships between requirements within the selected requirement documents, the test cases associated with the requirements, and any issues reported for the test cases.
Displays the hierarchical relationships between the requirements within the selected requirement documents and any requirements, issues, test cases, or test runs linked to the requirements. Displays detailed status information about the test runs generated for all test cases associated with the selected requirements, organized by folder. Requires a TestTrack TCM license to view the test runs. Displays the relationships between the selected requirements, the test cases associated with the requirements, and any issues reported for the test cases.
Displays detailed status information about the test cases generated for the selected requirements. Requires a TestTrack TCM license to view the test cases.
Displays detailed status information about the test runs generated for all test cases associated with the selected requirements. Requires a TestTrack TCM license to view the test runs. Displays the relationships between the selected test cases and the requirements the test cases were generated for. Requires a TestTrack RM license to view the requirements.
Creating built-in reports

TestTrack includes several built-in reports to help you track the status of projects and analyze the data. You can create reports to display general project information or data about items. 1. Choose Create > Report. The Select Report Type dialog box opens. 2. Select a report type and click OK. See Report types, page 119. The Add Report dialog box opens. 3. Enter a Name and Title. The title appears at the top of the report when it is viewed or printed. 4. Select a Share option.
122
n n n n n
Private restricts other users from using the report. Shared with Everyone shares the report with all users and customers. Shared with Users shares the report with other users. Shared with Customers shares the report with customers. Shared with Security Groups shares the report with selected security groups.
5. Select a report type or an item type to include in the report on the Report On tab. The available options depend on the report type. 6. Click the Source tab to select the data to include in the report. This tab is not available for detail, distribution, list, or trend reports. 7. Click the Options tab to select additional report display options. The available options depend on the selected report type and content. 8. Click the Sorting tab to select a primary or secondary sort column and set the column sort order. Trend reports do not have sorting options. 9. If you are creating a distribution or trend report, click the Charting tab to add a chart to the report. See Charting report data, page 139. 10. If you are creating a list report, click the Formatting tab to override the field and table formatting defined in the stylesheet used for the report. 11. To preview the report, click the Preview button. 12. Click Add. The report is added. See Generating built-in reports, page 70 for information about running reports.
Creating detail reports

Detail reports include detailed information about individual issues, requirements, requirement documents, test cases, test runs, folders, customers, users, security groups, or test configurations in a project. 1. Choose Create > Report. The Select Report Type dialog box opens. 2. Select Detail and click OK. The Add Detail Report dialog box opens.
123
3. Enter a Name and Title. The title appears at the top of the report when it is viewed or printed. 4. Select a Share option.
n n n n n
5. On the Report On tab, select the item type to report on from the Report contains list. If the report is based on folders, users, customers, security groups, or test configs, you can choose to include all or selected items. 6. Click the Options tab to select report display options.
n
Select a Stylesheet, which is a template used to generate formatted reports. See Detail report stylesheets, page 552. Click Browse to select a custom stylesheet. Optionally select a Filter to only include specific records in the report. You can only select a filter if you are reporting on issues, requirements, requirement documents, test cases, and test runs. Filters with an ellipsis (...) after the name prompt you to enter restriction information when the report is generated. See Using interactive filters, page 30. Select Print items on separate pages to print each item included in the report on a separate page.
7. Click the Sorting tab to select a primary or secondary sort column and set the column sort order. This tab is not available for reports based on folders.
8. To preview the report, click the Preview button. 9. Click Add. The report is added. See Generating built-in reports, page 70 for information about running reports.
124
Creating distribution reports

Distribution reports allocation of issues, requirements, requirement documents, test cases, or test runs in a project. For example, use these reports to view the count of currently assigned issues by product, status by priority, severity by version, and more. You can add a chart to display data as a count or percentage. 1. Choose Create > Report. The Select Report Type dialog box opens. 2. Select Distribution and click OK. The Add Distribution Report dialog box opens.
n n n n n
5. On the Report On tab, select the data to include in the report.

n n
Select the item type to report on from the Report contains list. Select an option to specify the data to include in the report. The available options depend on the selected item type.
6. Click the Options tab to select report display options.
125
n n
Select the date range to report on in the Period from and through fields. Select a Stylesheet, which is a template used to generate formatted reports. See Distribution report stylesheets, page 556. Click Browse to select a custom stylesheet. Optionally select a Filter to only include specific records in the report. You can only select a filter if you are reporting on issues, requirements, requirement documents, test cases, and test runs. Filters with an ellipsis (...) after the name prompt you to enter restriction information when the report is generated. See Using interactive filters, page 30. Select Include totals to include totals in the report rows and columns. To add totals to a chart, use the Data to Graph list on the Charting tab. Select Hide empty columns and Hide empty rows to hide columns and rows that do not contain any data. Enter the number of Records per printed page to limit the number of records included on one printed page.
7. Click the Sorting tab to select a primary or secondary sort column and set the column sort order.
8. Click the Charting tab to add a chart to the report. See Charting report data, page 139. 9. To preview the report, click the Preview button. 10. Click Add. The report is added. See Generating built-in reports, page 70 for information about running reports.
Creating list reports

List reports include selected fields from issues, requirements, requirement documents, test cases, test runs, folders, customers, users, security groups, or test configurations in rows and columns. 1. Choose Create > Report. The Select Report Type dialog box opens.
126
2. Select List and click OK. The Add List Report dialog box opens.
n n n n n

n n
Select the item type to report on from the Report contains list. Select the fields to include in the report from the Available Fields list and click the Add button to move them to the Fields in Report list. Click Top, Move Up, Move Down, or Bottom to reorder the fields.

n
Select a Stylesheet, which is a template used to generate formatted reports. See List report stylesheets, page 557. Click Browse to select a custom stylesheet. Optionally select a Filter to only include specific records in the report. You can only select a filter if you are reporting on issues, requirements, requirement documents, test cases, and test runs. Filters with an ellipsis (...) after the name prompt you to enter restriction information when the report is generated. See Using interactive filters, page 30.
127
Enter the number of Records per printed page to limit the number of records included on one printed page.
8. Click the Formatting tab to override the field and table settings defined in the selected stylesheet.
Creating trend reports

Trend reports include issue, requirement, requirement document, test case, or test run workflow events entered over time. Use these reports to determine the efficiency of a project. You can add a chart to display items in a timeline. 1. Choose Create > Report.
128
The Select Report Type dialog box opens. 2. Select Trend and click OK. The Add Trend Report dialog box opens.
n n n n n

n n
Select the item type to report on from the Report contains list. Select an option to specify the data to include in the report. The available options depend on the selected item type.

n n
Select the date range to report on in the Period, from, and through fields. Select a Stylesheet, which is a template used to generate formatted reports. See Trend report stylesheets, page 562. Click Browse to select a custom stylesheet.
129
Optionally select a Filter to only include specific records in the report. You can only select a filter if you are reporting on issues, requirements, requirement documents, test cases, and test runs. Filters with an ellipsis (...) after the name prompt you to enter restriction information when the report is generated. See Using interactive filters, page 30. Select Include totals to include totals in the report rows and columns. To add totals to a chart, use the Data to Graph list on the Charting tab. Select Hide empty columns to hide columns that do not contain any data. Enter the number of Records per printed page to limit the number of records included on one printed page.
n n
7. Click the Charting tab to add a chart to the report. See Charting report data, page 139. 8. To preview the report, click the Preview button. 9. Click Add. The report is added. See Generating built-in reports, page 70 for information about running reports.
Creating release planning reports

Release planning reports include detailed information that helps with planning a project, release, or iteration. 1. Choose Create > Report. The Select Report Type dialog box opens. 2. Select Release Planning and click OK. The Add Release Planning Report dialog box opens.
130
n n n n n
5. On the Report On tab, select the report you want to create. See Release planning reports, page 120. Note: The report stylesheet is automatically applied based on the selected report. See Release planning report stylesheets, page 557. 6. Click the Source tab to select the data to include in the report.
n
Click Browse to select the folder that contains the items you want to include. Folders are required for some reports. The folder icon and type are displayed and the release start and end dates are displayed if release planning is enabled for the selected folder. Select Recursive to include child folders of the selected folder and then select the child folder types to include. Click Clear to clear the selected folder path if a folder is not required.
131
Select the item types to include in the report. If an item type is required, it is selected by default and you cannot change the setting. Optionally select a filter for each selected item type if you only want to include filtered records in the report. Click Create Filter to add a filter. See Adding Filters, page 97. Select Include data for all linked items to include information about any items linked to records included in the report. Select a link definition from the list to specify the links to include.
7. Click the Options tab to select report display options. The available options depend on the selected report and content.
n
Select Show report data to display the text-based portion of the report. Clear this option if you only want to include a chart in the report. Select Show chart to display an interactive chart in the report.
132
Creating release status reports

Release status reports include detailed information that helps with tracking and communicating the status or progress of a project, release, or iteration. 1. Choose Create > Report. The Select Report Type dialog box opens. 2. Select Release Status and click OK. The Add Release Status Report dialog box opens.
n n n n n
5. On the Report On tab, select the report you want to create. See Release status reports, page 120.
133
Note: The report stylesheet is automatically applied based on the selected report. See Release status report stylesheets, page 558. 6. Click the Source tab to select the data to include in the report.
n
Click Browse to select the folder that contains the items you want to include. Folders are required for some reports. The folder icon and type are displayed and the release start and end dates are displayed if release planning is enabled for the selected folder. Select Recursive to include child folders of the selected folder and then select the child folder types to include. Click Clear to clear the selected folder path if a folder is not required. Select the item types to include in the report. If an item type is required, it is selected by default and you cannot change the setting. Optionally select a filter for each selected item type if you only want to include filtered records in the report. Click Create Filter to add a filter. See Adding Filters, page 97. Select Include data for all linked items to include information about any items linked to records included in the report. Select a link definition from the list to specify the links to include.
n
Select Show report data to display the text-based portion of the report. Clear this option if you only want to include a chart in the report. Select Show chart to display an interactive chart in the report.
If you creating a folder task board report with configurable columns, click Add in the Columns area to add a column and then enter the column name and select the column background color. To choose the workflow states to include in a selected column, select a state in the States list and click the left arrow button to add it to the column. Select a column and click Top, Move Up, Move Down, or Bottom to reorder the column display order.
134
8. Click the Sorting tab to select a primary or secondary sort column and set the column sort order. This tab is not available for all release status reports.
Creating time tracking reports

Time tracking reports include information that helps with tracking and communicating actual work performed on items. 1. Choose Create > Report. The Select Report Type dialog box opens. 2. Select Time Tracking and click OK. The Add Time Tracking Report dialog box opens.
135
n n n n n
5. On the Report On tab, select the report you want to create. See Time tracking reports, page 121. Note: The report stylesheet is automatically applied based on the selected report. See Time tracking report stylesheets, page 560. 6. Click the Source tab to select the data to include in the report.
n
Click Browse to select the folder that contains the items you want to include. Folders are required for some reports. The folder icon and type are displayed and the release start and end dates are displayed if release planning is enabled for the selected folder. Select Recursive to include child folders of the selected folder and then select the child folder types to include. Click Clear to clear the selected folder path if a folder is not required.
136
Select the item types to include in the report. If an item type is required, it is selected by default and you cannot change the setting. Optionally select a filter for each selected item type if you only want to include filtered records in the report. Click Create Filter to add a filter. See Adding Filters, page 97. Select Include data for all linked items to include information about any items linked to records included in the report. Select a link definition from the list to specify the links to include.
n n
Select the date range to report on in the Include workflow events from and through fields. Select Show report data to display the text-based portion of the report. Clear this option if you only want to include a chart in the report. Select Show chart to display an interactive chart in the report.
9. To preview the report, click the Preview button.
137
10. Click Add. The report is added. See Generating built-in reports, page 70 for information about running reports.
Creating traceability reports

Traceability reports include detailed information that allows you to perform coverage analysis by viewing relationships between requirements and related items in a project. 1. Choose Create > Report. The Select Report Type dialog box opens. 2. Select Traceabilityand click OK. The Add Traceability Report dialog box opens.
n n n n n
5. On the Report On tab, select the report you want to create. See Traceability reports, page 121. Note: The report stylesheet is automatically applied based on the selected report. See Traceability report stylesheets, page 561. 6. Click the Source tab to select the data to include in the report.
138
Ch ar t in g r e p or t d at a
Click Browse to select the folder that contains the items you want to include. Folders are required for some reports. The folder icon and type are displayed and the release start and end dates are displayed if release planning is enabled for the selected folder. Select Recursive to include child folders of the selected folder and then select the child folder types to include. Click Clear to clear the selected folder path if a folder is not required. Select the item types to include in the report. If an item type is required, it is selected by default and you cannot change the setting. Optionally select a filter for each selected item type if you only want to include filtered records in the report. Click Create Filter to add a filter. See Adding Filters, page 97. Select Include data for all linked items to include information about any items linked to records included in the report. Select a link definition from the list to specify the links to include.
7. Click the Sorting tab to select a primary or secondary sort column and set the column sort order. This tab is not available for all traceability reports.
Charting report data

You can add charts to distribution and trend reports. The available charts include pie, 3D pie, bar, 3D bar, area, 3D area, line, and 3D line.
139
Note: You can also include interactive charts in release planning, release status, and time tracking reports. The chart settings for these reports can only be customized in the stylesheet, not the report settings. 1. Click the Charting tab when you are creating or editing a distribution or trend report. See Creating distribution reports, page 125 or Creating trend reports, page 128.
2. Click New Chart. 3. Select the chart Type and enter the Chart Title. 4. Select the Data to Chart. 5. Select or enter any additional chart options. Note: To add another chart to the report, click New Chart. To reorder multiple charts on a report, select a chart and click Move Up or Move Down. Select a chart and click Delete Chart to delete it. 6. Click Add or OK to save the changes.
140
Bar, area, and line chart fields

Field Size Color Height Width Background Color X Axis Title Y Axis Title Size Color Show Labels X Axis Size Y Axis Size Spacing Color Density Show Grid Show X Axis Show Y Axis Color Description Chart title size Chart title font color Chart height Chart width Chart background color X (horizontal) axis title Y (vertical) axis title X and Y axis title size X and Y axis title font colors Displays chart component labels X axis label size Y axis label size Amount of space (pixels) between labels X and Y axis label color Density percentage. 80% displays all labels, 40% displays half, etc. Displays the chart grid pattern Displays the X axis on the chart Displays the Y axis on the chart Grid line color
141
Ad d in g e xt e r n al r e p or t s t o Te st Tr ack
Pie charts
Field Size Color Height Width Background Color Show Labels Show Percents Label Size Color Label Position Description Chart title size Chart title font color Chart height Chart width Chart background color Displays chart data labels Displays chart data in percents Chart label size Label font color Spacing of chart labels
Note: Pie charts are scaled based on a number of factors, including image size, label size, and number of labels. You may need to change the image height and width dimensions for the pie chart to display correctly.
Adding external reports to TestTrack

Adding external reports to TestTrack gives you the ability to launch an external report viewer from TestTrack to view reports stored in reporting services. 1. Choose Create > Report. The Select Report Type dialog box opens. 2. Select the name of the reporting service you want to add the report from and click OK. The Select External Reports dialog box opens. A list of the available reports is displayed.
3. Select the report you want to add.
142
Cr e at in g l ive ch ar t s
To add more than one report, Ctrl+click each report. Note: Click Create to create a report in the external reporting service. You can only create reports if an external reporting client plug-in that supports report editing is installed. Ask your TestTrack administrator for information. 4. Click Add. The report is added and displayed in the Reports list window. Note: By default, external reports are private. You can edit the report to share it with everyone, users, customers, or specific security groups. See Editing reports, page 151.
Creating live charts

Live charts are a type of report that provides advanced charting capabilities across all of your development and testing artifacts. Use these reports to monitor overall progress or a specific segment of a project in real time. TestTrack includes several types of live charts, including column, bar, line, pie, and scatter charts. Each chart has several variations to help you chart data exactly as you want to view it. You can open live charts in one or more standalone windows, which can help you continuously monitor key indicators and team progress throughout the day as you perform other work. For example, you may want to use a live chart to display an overview of the actual hours spent on items versus the estimated hours to see how a project is progressing and identify any overruns. You can also open live charts in the Folders list window to chart the contents of a selected folder to and view more focused data for a specific part of a project, release, or iteration. See Viewing Live Charts, page 71. You can create live charts based on one item type or a combination of types. You can also limit the items included in the chart to a specific folder. For example, you may only want to include issues and test runs for a specific release or iteration. To create a live chart, you configure the following information: chart type, data to include, fields for the X and Y axis, and legend position. Each field you add to the chart is a series, which is a group of related data points. Each series is listed in the chart legend. Most charts support multiple series. Conical, meter, and pie charts only support one series. Note: Live charts can only be viewed in the TestTrack Client. 1. Choose Create > Report. The Select Report Type dialog box opens. 2. Select Live Chart and click OK. The Add Live Chart dialog box opens with the Type tab selected.
143
3. Enter a Name and Title. The title appears at the top of the chart. 4. Select a Share option.
n n n n n
Private restricts other users from viewing the chart. Shared with Everyone shares the chart with all users and customers. Shared with Users shares the chart with other users. Shared with Customers shares the chart with customers. Shared with Security Groups shares the chart with selected security groups.
5. Select a chart type in the left pane and then select the chart to create in the right pane. See Live chart types, page 145. 6. Click the Source tab to select the data to include in the chart.
n
Select the item types to include in the chart. Optionally select a filter for each type if you only want to include specific records in the chart. Interactive filters are not available for live charts. Click Create Filter to add a filter. See Adding Filters, page 97. Select Items in folder to only include items in a specific folder. Click Browse to select a folder. Select Recursive to include any child folders.
144
7. Click the X-Axis tab to specify the data to display on the horizontal axis. See Configuring the live chart X axis, page 146. 8. Click the Y-Axis tab to specify the data to display on the vertical axis. See Configuring the live chart Y axis, page 148. 9. Click the Legend tab and select the position of the legend relative to the chart.
10. Click Preview to preview the chart to make sure you configured it correctly. 11. Click Add. The live chart is added.
Live chart types

TestTrack includes the following types of live charts. Each chart type has multiple variations available to help you customize the chart appearance. Thumbnails of each chart type and variation are displayed on the Type tab in the Add Live Chart dialog box. See Creating live charts, page 143. Chart type Area Description Displays data points plotted on lines with shading in the area between the axis and lines. Multiple series are displayed in layers or stacked. Useful for evaluating changes over time and identifying trends.
145
Chart type Bar
Description Displays rectangular bars for each series that are sized based on the values they represent. Same as column charts except the bars are horizontal. Multiple series are displayed in layers, stacked, overlapping, or in 3D depth. Useful for evaluating changes over time and comparing categories of data. Displays the minimum, 25th percentile, median, 75th percentile, and maximum values for a series using a box and maximum and minimum lines. Only used for numeric fields. Useful for statistical analysis and determining the distribution of items in categories. Displays rectangular bars for each series that are sized based on the values they represent. Same as bar charts except the bars are vertical. Multiple series are displayed in layers, stacked, overlapping, or in 3D depth. Useful for evaluating changes over time and comparing categories of data. Displays multiple series using a combination of column, line, area, and scatter chart types. The chart type for each series is selected in the Configure Series area in the Add Live Chart dialog box. Useful for clearly differentiating multiple data categories. Displays data points in slices that represent a percentage of a whole pyramid, cone, or funnel shape. Useful for comparing groups of data. Displays data points plotted on lines. Multiple series are displayed on multiple lines. Useful for displaying continuous data over time and evaluating data trends in equal intervals, such as weeks or months. Displays each series as one point on a meter. Data groups are determined by the X-axis field values and values are determined by the Y-axis configuration. Useful for data visualization in a gauge format. Displays data points in slices that represent a percentage of the whole pie. Data can be displayed in a flat pie, exploded pie with slices separated from the center of the pie, or a donut. Useful for comparing groups of data. Displays a symbol to represent each data point. Useful for evaluating relationships between values in multiple data categories.
BoxWhisker
Column
Combo
Conical
Line
Meter
Pie
Scatter
Configuring the live chart X axis

When you create a live chart, you need to specify the field used to group data on the horizontal chart axis. For example, if you want a chart to display actual versus estimated hours data for all item types, you may choose to display the item types on the X-axis. 1. Click the X-Axis tab in the Add Live Chart or Edit Live Chart dialog box.
146
2. Enter an X-Axis Title and optionally select a title color. Conical, meter, and pie charts do not have X-axis titles. 3. Select a Field Type to indicate the type of fields to display in the Fields list. The available field types depend on the item types selected on the Source tab and the chart type.
147
Field type All field types Date
Displays All available fields for the selected item types. Date/time fields, such as Created Date, for the selected item types and workflow events related to the items. Pop-up menus, such as Version and Product, and other drop-down lists for the selected item types and workflow events related to the items. User and customer fields, such as Assigned To User and Created By User, for the selected item types and workflow events related to the items. Check box fields and other Boolean fields, such as Is Marked As Suspect and Issue Has Links, for the selected item types and workflow events related to the items. The state of the selected item types (Open or Closed). Integer and decimal number fields, such as Actual Hours and Percent Done, for the selected item types and workflow events related to the items. The Folder Name field selected in the Items in folder field on the Source tab. The item type: Issue, Requirement, Requirement Document, Test Case, or Test Run.
List
User/Customer
Boolean
State attribute Numeric
Folder name Item type
4. Select the field to include on the X axis from the Fields list. The available fields depend on the selected field type and your security permissions. If multiple item types are selected on the Source tab, only fields that are common between item types are included in the list. If one item type and the Items in folder option are selected on the Source tab, item-specific fields and common fields between the item type and folder are displayed. Note: To search for a field, enter the characters to search for in the Search field. Matching fields are displayed in the list as you type. Enter additional characters to narrow the results. 5. Select the Field Values to include. The available options depend on the selected field. Note: If a user or customer field is selected, click Find User to search for users or customers to include the chart. See Finding users and customers, page 39. 6. Select Hide empty category items if you do not want to include items without values in the X axis. This option is not available for numeric fields. 7. Click Add or OK to save the changes.
Configuring the live chart Y axis

When you create a live chart, you need to specify the fields to display data for on the vertical chart axis. You can use the left and right vertical axis to display different series.
148
You can also configure options for each series included in the chart, such as the name used in the legend, the Y-axis scale, and data field for axis labels. Note: Conical, meter, and pie charts only support one series. If you select a field on the X-Axis tab, you cannot add additional fields on the Y-Axis tab. You can configure series options for these chart types on the Y-Axis tab. 1. Click the Y-Axis tab in the Add Live Chart or Edit Live Chart dialog box.
2. Enter a Y-Axis Left Title and Y-Axis Right Title. Optionally select title colors. Conical, meter, and pie charts do not have Y-Axis titles. 3. Select a Field Type to indicate the type of fields to display in the Fields list. The available field types depend on the item types selected on the Source tab and the chart type.
149
Field type All field types Date
Displays All available fields for the selected item types. Date/time fields, such as Created Date, for the selected item types and workflow events related to the items. Pop-up menus, such as Version and Product, and other drop-down lists for the selected item types and workflow events related to the items. User and customer fields, such as Assigned To User and Created By User, for the selected item types and workflow events related to the items. Check box fields and other Boolean fields, such as Is Marked As Suspect and Issue Has Links, for the selected item types and workflow events related to the items. The state of the selected item types (Open or Closed). Integer and decimal number fields, such as Actual Hours and Percent Done, for the selected item types and workflow events related to the items. The Folder Name field selected in the Items in folder field on the Source tab. The item type: Issue, Requirement, Requirement Document, Test Case, or Test Run.
List
User/Customer
Boolean
State attribute Numeric
Folder name Item type
4. Select a field in the Fields list and click the right arrow button to add it to the Series list. The available fields depend on the selected field type and your security permissions. If a list, Boolean, user/customer, or state attribute field is selected on the X-Axis tab, it is automatically added to the Series list. Note: To search for a field, enter the characters to search for in the Search field. Matching fields are displayed in the list as you type. Enter additional characters to narrow the results. To filter the field list, select All Fields, Common Fields, or an item type from the drop-down list. You can only filter the field list if multiple item types are selected on the Source tab. 5. Arrange the fields in the Series area. Options selected in the Configure Series area are displayed in parentheses after the series.
n
The order that series are displayed reflects the layering order on the chart. The series at the top of the list is displayed as the top layer or left-most item in the chart. To reorder the series, select a series and click Top, Move Up, Move Down, or Bottom. To remove a series from the chart, select the series and click Remove.
6. Select a series and then select any Configure Series options. The available options depend on the selected series.
150
Vie win g r e p or t se t t in gs
Field Name Type Y-Axis
Description The series name displayed in the chart legend. The chart type for the selected series. The axis scale the selected series is associated with (left or right). Bar and column charts can only use the left axis. The color, line type, and symbol to use for the selected series. Plots a trend line on the chart for the selected series and specifies the line style and color. Plots an average line on the chart for the selected series and specifies the line style and color. The value type used to display data on the Y axis, such as Count, Percent, or Sum. The Y-value number is displayed in conical, meter, and pie charts. The data field to use for the Y axis.
Style Trend Line Average Line Y-Value
Field Value
7. Click Add or OK to save the changes.
Viewing report settings

1. Select the report on the Reports list window. 2. Click View. The read-only View Report dialog box opens. 3. Click Edit to edit the report. See Editing reports, page 151. 4. Click OK to close the View Report dialog box.
Editing reports
1. Select the report on the Reports list window. 2. Click Edit. The Edit Report dialog box opens. 3. Make any changes. If you are editing an external report, you can only change the Name, Output Type, and Share fields. The other field information is stored in the reporting service. Note: Click Edit in External Report Tool to edit the report content in the external reporting service. You can only edit reports if a client plug-in that supports report editing is installed. Ask your TestTrack administrator for information. 4. Click OK. The changes are saved.
151
Du p l icat in g r e p or t s
Duplicating reports
If you add reports with the same basic information, you can save time by duplicating and editing an existing report. 1. Select the report you want to duplicate. 2. Choose Edit > Duplicate Report. The report is duplicated and a number is added to the end of the report name. For example, if you duplicate the Product A report, the duplicated report is named Product A.1. 3. Modify the duplicated report and save the changes.
Deleting reports
1. Select the report on the Reports list window and click Delete. You are prompted to confirm the deletion. 2. Click Yes. The report is deleted. Note: If you delete an external report, the report is only deleted from TestTrack and not the external reporting service.
Creating text file report templates

Note: We recommend using stylesheets to customize reports. See Report Stylesheets, page 551. You can create custom text-based report templates that can be used when saving list window reports. See Saving list window reports as text files, page 152. You can create templates using a text editor, field codes, and alphanumeric characters. You can also create a tab- or comma-delimited template for use with other databases and tools. 1. Create the text document using Notepad or another text editor. You can use any alphanumeric character and field codes. The saved report is formatted based on the text code layout. Field codes are replaced with the corresponding text. See Field Codes, page 529 for field code information. 2. Save the document. You can now save a report based on the template you created.
Saving list window reports as text files

You save a list window reports as a text file using a text-based report template. See Creating text file report templates, page 152. Note: We recommend using stylesheets to customize reports. See Report Stylesheets, page 551. 1. Open the list window you want to save the report for.
152
Cr e at in g RS S Fe e d s
If you do not want to include every record, select the records you want to include on the list window first. If you apply a filter, only the records that pass the filter are included in the report. 2. Choose File > Print. 3. Select Only print selected items if you selected specific items to save. 4. Select Create report file from template. 5. Click Save. The Select Report Template dialog box opens. 6. Select the report template you want to use and click Open. The Save Report As dialog box opens. 7. Select a directory and enter a filename. 8. Click Save. The report is saved as a text file.
Creating RSS Feeds

You can create RSS feeds to help team members stay up-to-date on projects, even when they are not using TestTrack. Because TestTrackRSSfeeds are based on filters, you can create an RSSfeed by publishing a filter. Records that pass the filter are displayed in the feed. For example, management wants to keep all team leads aware of critical open customer issues. You can create a filter that includes open issues with Critical selected in the Severity field and then publish the filter. Users can add the feed URL to their RSS aggregator or you can add the feed to an internal web page. See Accessing RSS feeds, page 154. Keep the following in mind:
n n n
RSSfeeds must be enabled for the project. See Setting hyperlink options, page 360. You must have security permissions to mark filters as published to create RSS feeds. TestTrack data in RSS feeds can be viewed by anyone, not just TestTrack users and customers. Make sure that feeds do not contain confidential information.
1. Choose View > Filters to open the Filters list window. 2. Select the filter you want to publish and click Edit. The Edit Filter dialog box opens. 3. Select Publish from the Share list. Note: You cannot publish filters that include restrictions based on <current user> because users do not have to be logged in to view RSS feeds. You also cannot publish filters with interactive restrictions. 4. Click OK to save the changes. The filter is published. The RSS icon is displayed next to the filter in the Filters list window.
153
Acce ssin g RS S fe e d s
Accessing RSS feeds

To access RSS feeds, you subscribe to published filters. When you subscribe, you can choose how to display data and copy the feed URL so you can add it to your RSS aggregator or a web page. Feeds can display a summary of records that pass the filter with a link to the related records or the number of records that pass the filter and the total number of records in the project. Note: You can only view feeds in browsers that support RSS. Refer to your browser documentation for information. 1. Choose View > Filters to open the Filters list window. 2. Select the published filter you want to subscribe to. An RSS icon is displayed next to published filters. 3. Click Subscribe. The Subscribe dialog box opens.
4. Select the data format you want to use.

n
Select List of items to display a list of items that pass the published filter. The record number, summary, description (first 128 characters), status, and a hyperlink to the related record are displayed. Select RSS feed using http hyperlinks to items to provide an http hyperlink for TestTrack Web users. Select RSS feed using ttstudio hyperlinks to items to provide a ttstudio hyperlink for TestTrack Client and TestTrack Web users. TestTrack Web users can only open ttstudio links if the TestTrack URL Redirector is installed on their computer. Select Number of records passing the filter and total number of records to display the number of records that pass the published filter and the total number of records in the project. For example, this data can be used to publish charts and graphs that communicate overall project status on an internal web page. Note: The RSS feed using http hyperlinks to items option is only available for published issue filters.
5. Click Copy to copy the URL generated for the RSS feed. 6. Paste the URL in your RSS aggregator to add the feed. 7. Click OK to close the Subscribe dialog box.
154
M an agin g Or p h an e d Email
Managing Orphaned Email

When email tracking is enabled, email sent from records and replies to these emails are added to the corresponding records. Emails contain a tracking code in the header and message, which is used to associate email with records. The email is orphaned on the TestTrack Server if TestTrack cannot associate a reply email with a record. An email may be orphaned if the associated record is deleted from the project, the tracking code in the email is modified, or TestTrack cannot associate related email during an XML import. You can view orphaned emails and associate them with related records or delete them from the TestTrack Server. 1. Choose Tools > Administration > Orphaned Email. The Orphaned Email dialog box opens.
2. Select an email and click View to view it. See Viewing orphaned email, page 155. 3. Select an email and click Attach To to associate it with a record. See Attaching orphaned email to records, page 156. 4. Select an email and click Delete to delete it from the TestTrack Server. See Deleting orphaned email, page 157. 5. Click OK to close the Orphaned Email dialog box.
Viewing orphaned email

1. Choose Tools > Administration > Orphaned Email. The Orphaned Email dialog box opens. 2. Select an email and click View. The View Orphaned Email dialog box opens with the Body tab selected.
155
3. Click the Attachments tab to manage files attached to the email.

n n
Select an attachment from the Attachments list. Click View to view the file using the associated application. See Setting view file options, page 345. Click Extract to save a copy of the file. The Save As dialog box opens. Select the file location, enter a file name, and click Save. Click Open to save a copy of the file and open it with the associated application. The Save As dialog box opens. Select the file location and enter a file name. Click Save to open the file and save it in the selected directory.
4. Click Attach To to attach the email to a record. See Attaching orphaned email to records, page 156. 5. Click Delete to delete the email from the TestTrack Server. See Deleting orphaned email, page 157. 6. Click OK to close the View Orphaned Email dialog box.
Attaching orphaned email to records

1. Choose Tools > Administration > Orphaned Email. The Orphaned Email dialog box opens. 2. Select an email and click Attach To.
156
The Select Items to Add dialog box opens. You can search, go directly to a specific record, or apply a filter to find records.
3. Select a record Type. The items change based on the selected record type. 4. Select the record to attach the email to. 5. Click Add. The Associate Email dialog box opens. The selected records are displayed.
6. Click Add to select additional records. This is helpful if you want to attach the email to different record types. For example, you can attach an email to an issue and a test case. 7. Select a record and click Delete to remove it from the list. 8. Click OK. The email is associated with the records.
Deleting orphaned email

You can delete orphaned email if it is not associated with a record. 1. Choose Tools > Administration > Orphaned Email. The Orphaned Email dialog box opens. 2. Select an email and click Delete.
157
You are prompted to confirm the deletion. 3. Click Yes. The email is deleted.
158
Using TestTrack Pro

This guide includes information for working with the issues other items you track and manage with TestTrack Pro.
Adding Issues
1. Choose Create > Issue. The Add Issue dialog box opens with the Detail tab selected. The Detail tab includes 4 mini tabs: Found By, Reproduce, Computer Config, and Attachments. Note: You can configure the TestTrack Client to display all of the issue information in a single page instead of mini tabs. See Setting display options, page 348. 2. Enter the information in the top portion of the Add Issue dialog box. TestTrack Pros fields and workflow can be customized. The information you enter may be different depending on your companys use of TestTrack Pro.
n n n n n n n n n n n
Enter an issue Summary. You can enter up to 255 characters. Status displays the issue state and assignment. Select the issue Disposition. Select the issue Type. Select the issue Priority. Select the Product. Select the Component. Enter an issue Reference number. Select the issue Severity. Entered by defaults to the logged in user or you can select another user. Date Entered defaults to the current date or you can enter another date.
3. Enter details about the issue on the Detail tab. See Entering issue details, page 160. 4. Click the Custom Fields tab and enter or select custom field information. See Entering custom issue fields, page 162. 5. Click the Workaround tab to enter a workaround solution for the bug that can be used until the issue is fixed or implemented. See Entering issue workarounds, page 162. 6. Click the Email tab if you want to automatically notify users and customers when the issue changes. See Managing Issue Email, page 171. 7. Click the Files tab to attach files to the issue. See Attaching Files, page 54. If TestTrack is integrated with a source control tool, you can also attach source code files. See Attaching source code files, page 499. 8. Click Add when you finish entering the issue information. The issue is added to the project.
159
Ad d in g Issu e s
Note: You may be prompted to enter an electronic signature and change reason. See Entering Electronic Signatures, page 477.
Entering issue details

The issue detail helps other users fix the issue and test the fix. It is helpful to provide as much information as possible in the issue, including a detailed description, the steps to reproduce the issue, the computer configuration the issue occurred on, and any supporting file attachments such as screenshots. 1. Click the Detail tab when you are adding or editing an issue.
Tip: You can configure TestTrack to display the issue information in a single page instead of mini tabs. The instructions and examples in this section refer to the mini tab layout. See Setting display options, page 348. 2. Enter the information on the Detail: Found by mini tab.
n
Found by defaults to the logged in user or you can select another user. To search for a user, click the Find button next to the Found By field. See Finding users and customers, page 39. Date defaults to the current date or you can enter another date. Select the software Version. Enter a detailed issue Description.
n n n
3. Enter the information on the Detail: Reproduce mini tab.

n n
Select a Reproduced level. Enter the detailed Steps to Reproduce the issue.
160
Ad d in g Issu e s
4. Enter the information on the Detail: Computer Config mini tab.

n n
Select a Computer Config. The default is the logged in users configuration. Enter information about Other Hardware and Software.
5. Click the Detail: Attachments mini tab to attach a file to the issue. See Attaching Files, page 54. Note: The TestTrack administrator is generally responsible for setting the file type for pasted or captured images. See Setting file attachment options, page 358.
n
Click Attach to attach a file. Browse to the directory that contains the file, select the file, and click Open. The file is attached. Click Paste to paste a file from the clipboard. To rename the file, right-click it and choose Rename (Windows) or Ctrl+click it (Mac). Attachments cannot be renamed after an issue is saved. Click Screen Capture to capture and attach a screenshot. See Capturing Screenshots, page 55. Select an attachment and click Remove to remove it. Select an attachment and click View to view the file using the associated application. See Setting view file options, page 345. You may also be able to view thumbnails of image file attachments. Right-click an image file and click Show Thumbnail to view the thumbnail. Select an attachment and click Extract to save a copy of the file.
n n
161
Ad d in g Issu e s
Select an attachment and click Open to save a copy of the file and open it with the associated application.
6. Click Add or OK to save the changes, or click another tab to enter additional issue information.
Entering custom issue fields

If the project contains custom fields, they may be displayed on the Custom Fields tab. 1. Click the Custom Fields tab when you are adding or editing an issue.
2. Enter or select the custom field values. 3. Click Add or OK to save the changes, or click another tab to enter additional issue information.
Entering issue workarounds

You can provide a workaround for the bug that can be used until it is fixed or implemented. 1. Click the Workaround tab when you are adding or editing an issue.
2. Enter the workaround. 3. Click Add or OK to save the changes, or click another tab to enter additional issue information.
162
Ad d in g ad d it ion al issu e r e p or t s
Adding additional issue reports

Users, customers, or beta sites often report the same issue. To eliminate duplicates in a project, you can create one issue and add additional reports to the same issue. 1. Select the issue you want to add an additional report to. 2. Choose Edit > Edit Issue. The Edit Issue dialog box opens. 3. Click the Detail tab. 4. Choose Activities > New Reported By. You can also click New on the Detail tab. 5. Enter the additional report information. See Adding Issues, page 159. 6. Click OK when you finish adding the additional report. Note: The Detail tab includes a counter. When an issue is reported multiple times, the counter increases and shows the number of times the issue is reported.
Working with Issues

An issue is a bug, enhancement, change request, question, or any other product-related issue you need to track and resolve. It can be as simple as a typo in a help file or as complicated as a system crash. You will be tracking issues in no time at all after learning about adding issues, deleting issues, and everything in between. The TestTrack Pro workflow consists of states, events, and transitions that define the path an issue takes from initial reporting to resolution. To move an issue from state to state, the issue is assigned to users who perform the event assigned to them. The default workflow includes the following events: Assign, Estimate, Enter Work, Fix, Verify, Force Close, Re-Open, Release Notes, and Comment. Remember that the steps you follow and the issue events you use may differ depending on your companys workflow.
About the default issue tracking workflow

The issue tracking workflow consists of states, events, and transitions that define the path an issue takes from initial reporting to resolution. To move an issue from state to state, the issue is assigned to users who perform the event assigned to them. TestTrack Pros issue tracking workflow can be used out of the box or customized to support your business processes. See Customizing Workflows, page 414. The default issue tracking workflow includes the following events: Assign, Estimate, Enter Work, Fix, Verify, Force Close, Re-Open, Release Notes, and Comment. See Working with Issues, page 163.
Assigning issues
To move an issue through its lifecycle, you need to assign it to a user. For example, you may want to assign a new issue to a support engineer for review. The support engineer can then assign the issue to a programmer to fix. 1. Select the issue and choose Activities > Assign. The Assign dialog box opens.
163
Ab ou t t h e d e fau l t issu e t r ackin g wor kfl ow
2. Select an Assign By user. This field defaults to the logged in user. 3. Select an Assign To user. Click the Find button to search for a user. See Finding users and customers, page 39. 4. The Date defaults to the current date and time. You can enter another date and time. 5. Enter any Notes about the issue assignment. For example, you can let the user know why you are assigning the issue to them, what action you want them to take, or who to contact for additional help. 6. Click OK. Note: When an issue is assigned to you, open the issue and click the Workflow tab to review the assignment notes. The user who assigned the issue should let you know what work you are responsible for and provide detailed information. If you need more information, email the user who assigned the issue. See Emailing from TestTrack, page 73.
Estimating fix time

You may want to enter the estimated effort required to resolve an issue or implement a feature. In most companies, a project manager or team lead is responsible for entering the estimate effort before assigning the bug to a developer to work on. After the estimate information is entered, you can track and view the time it should take to complete a task. Tip: Estimate metrics improve both planning and allocation. An estimated resolution or implementation time should be added to any issue in a development process or other managed lifecycle process. 1. Select the issue and choose Activities > Estimate. The Estimate dialog box opens.
164
2. Select an Estimate By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the estimated Effort in hours to complete the fix. 5. Enter any Notes. 6. Select a Version number. You may also be able to enter a version number. 7. Enter the estimated Completion Date. 8. Click OK.
Entering work on issues

As you work on issues, you can enter the work you have completed to keep the project manager or development manager informed about your progress. 1. Select the issue and choose Activities > Enter Work. The Enter Work dialog box opens.
2. Select an Enter Work By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time.
165
4. Enter the Actual Effort in hours to work on the issue. This information can help with future planning and metrics. 5. Enter any Notes. It is helpful to provide information about the work you completed so far. 6. Enter the Remaining Time in hours to complete the issue. 7. Click OK.
Fixing issues
After you fix a bug, resolve an issue, or implement a feature, you need to mark the issue as fixed. The developer or team member who fixed the issue or implemented the feature is generally responsible for entering the fix information. 1. Select the issue and choose Activities > Fix. The Fix dialog box opens.
2. Select a Fixed By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Optionally select a Resulting State. You can only select a state if the workflow allows multiple resulting states. 5. Enter the fix Effort in hours to complete the fix. This information can help with future planning and fix metrics. 6. Enter any Notes about the fix. 7. Select Affects Documentation or Affects Test Plan if either applies. 8. Select a fix Resolution. 9. Select the Version number. You may also be able to enter a version number. 10. Enter the Remaining Time in hours to complete any additional work related to the fix. 11. Click OK.
166
Verifying a fix
After an issue is fixed, it needs to be verified. If an issue fails the verification, it can be re-assigned. 1. Select the issue and choose Activities > Verify. The Verify dialog box opens.
2. Select a Verify By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Optionally select a Resulting State. You can only select a state if the workflow allows multiple resulting states. 5. Enter any Notes. If a fix fails, you may want to describe why it failed. 6. Select the Version number. You may also be able to enter a version number. 7. Click OK.
Closing issues
Some issues may not follow the standard issue fix lifecycle. For example, an issue may be caused by third-party software. In this case, you can force close the issue. 1. Select the issue and choose Activities > Force Close. The Force Close dialog box opens.
167
2. Select a Force Close By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to provide information about why the issue was closed. 5. Select a Resolution. 6. Click OK.
Reopening issues
You can reopen closed issues if they resurface and need to go through your fix process again. 1. Select the issue and choose Activities > Re-Open. The Re-Open dialog box opens.
2. Select a Re-Open By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to include the reason the issue was reopened. 5. Click OK.
Adding comments to issues

Add comments to an issue to clarify an issue or add notes other users. 1. Select the issue and choose Activities > Comment. The Comment dialog box opens.
2. Select a Comment By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the comments and click OK. The comments are recorded with the issue history.
168
Vie win g issu e wor kfl ow h ist or y
Note: To view issue comments, select the issue, click View or Edit, and then click the Workflow tab. All comments are displayed on the Workflow tab.
Viewing issue workflow history

You can view where an issue is in the workflow, issue assignments, and any comments or additional information entered about an issue. You can also view time tracking information and a workflow history diagram. 1. Click the Workflow tab when you are viewing or editing an issue. The events added to the issue are displayed.
Note: Select Show System Comments to display events added by automation rules. 2. Click Work Items to view events with time tracking information, including the estimated, actual, and remaining work for the issue. See Viewing work items, page 44. 3. Click Diagram to view a diagram of the workflow states the issue was previously in, the events used to move the issue between states, and next available states. See Viewing item workflow history diagrams, page 43. 4. Select an event to view the event notes. 5. Select an event and choose Edit > View Event to view the event details. See Viewing workflow event details, page 41. 6. Select an event and choose Edit > Edit Event to edit the event details. See Editing workflow event details, page 42. 7. Select an event and choose Edit > Delete Event to delete it. See Deleting workflow events from items, page 42. 8. Click OK to save the changes.
169
M an agin g Issu e Lin ks
Managing Issue Links

You can link issues to other items in the same project. Linking helps you establish relationships between items and manage changes to related items when issues change. You can link items in a parent/child relationship or a peer relationship. Following are a few examples that illustrate the different uses for linking issues:
n
QA is testing a new software component and reports five issues. When the team lead reviews the issues, she realizes they are all symptoms of the same coding problem. She links the issues to make sure the same fix is applied to all issues. Your company is getting ready to release a major software upgrade. In conjunction with the release, the marketing department needs to update the web site, write a press release, create a direct mail campaign, and create an email marketing blast. The marketing director creates a parent issue named Upcoming Release and creates four separate issues for each task that needs to be accomplished. He then links the issues together in a parent/child relationship. A problem is found that includes a code change, a documentation change, and an update to an existing knowledgebase article. Instead of creating one issue, you create three different issues, link them together, and specify the order you want the issues to be closed. Requiring the code change issue to be closed first, then the documentation change issue, and finally the knowledgebase issue ensures the documentation and the knowledgebase article both reflect the code changes.
1. Click the Links tab when you are viewing or editing an issue.
2. Click Add Link to create a link. See Adding links, page 77. 3. Select a link and click View Link to view it. See Viewing links, page 80. 4. Select a link and click Edit Link to change it. See Editing links, page 81. 5. Select a link and click Diagram Links to generate a link diagram. See Diagramming links, page 79. 6. Select a link, click an item in the Link Details area, and click View Item to view the linked item. 7. Select a link, select an item in the Link Details area, and click Edit Item to edit the linked item.
170
M an agin g Issu e Fol d e r s
8. Select a link, select an item marked as suspect in the Link Details area, and click Investigate to view the suspect dependencies. See Investigating suspect dependencies, page 83. 9. Select a link, select an item marked as suspect in the Link Details area, and click Clear Suspect to clear the suspect. See Clearing suspect items, page 84. 10. Select a link, select an item in the Link Details area, and click Mark Suspect to mark the item as suspect. See Marking Items as Suspect, page 82. 11. Select a link and click Delete Link to delete it. See Deleting links, page 81. 12. Click Add or OK to save the changes.
Managing Issue Folders

You can add issues to folders to group them with other records. See Organizing Data with Folders, page 56. 1. Click the Folders tab when you are viewing or editing an issue. Folder paths are displayed if the issue is included in folders.
2. Select a folder and click Open Folder to open the folder. 3. Click Add to Folder to add the issue to a folder. See Adding items to folders, page 66. 4. Select a folder and click Move to Folder to move the issue to a folder. See Moving items to folders, page 66. 5. Select a folder and click Remove from Folder to remove the issue from the folder. See Removing items from folders, page 69. 6. Click OK to save the changes or click another tab to enter additional issue information.
Managing Issue Email

You can notify users and customers when an issue changes and work with emails sent about the issue if email tracking is enabled. Note: Tracked email is only displayed when you are viewing or editing an issue. 1. Click the Email tab when you are adding, editing, or viewing an issue. 2. If you are adding or editing an issue, select the users or customers you want to notify when the issue changes.
n n
Click Add to search for recipients. See Finding users and customers, page 39. To remove recipients, select the user or customer and click Remove.
3. Select an email and click View to view it. See Viewing tracked email, page 75.
171
Vie win g Issu e s
4. Select an email and click Reply To to reply to it. See Replying to tracked email, page 76. 5. Select an email and click Delete to delete it. See Deleting tracked email, page 76. You cannot delete email if you are viewing an issue. 6. Click Add or OK to save the changes, or click another tab to enter additional issue information.
Viewing Issues
You can view read-only issue information. You can also send email and enter issue events when viewing issues. 1. Select the issue on the Issues list window. 2. Choose Edit > View Issue or click View on the Issues list window. The View Issue dialog box opens. 3. Click Create Test Case to create a test case based on the issue. See Adding Test Cases, page 255. 4. Click Send Email to email a user or customer about the issue. See Emailing from TestTrack, page 73. 5. Click Edit to edit the issue. See Editing Issues, page 172. 6. Click OK to close the View Issue dialog box.
Editing Issues
Tip: If you need to update field values for multiple issues, use bulk field changes. This allows you to quickly update multiple records simultaneously. See Updating Multiple Items, page 84. 1. Select the issue on the Issues list window. 2. Choose Edit > Edit Issue. The Edit Issue dialog box opens. Note: If another user is editing an issue, a read-only icon is displayed next to the OK button. When the user closes the issue, it is updated and becomes available for editing. 3. Make any changes. 4. Click Create Test Case to create a test case based on the issue. See Creating Test Cases From Issues, page 175. 5. Click Send Email to email a user or customer. See Emailing from TestTrack, page 73. Note: Click the Email tab to view, reply to, or delete tracked email. See Viewing tracked email, page 75 and Replying to tracked email, page 76. 6. Click OK to save the changes. Note: If the changes impact linked or related items, you may want to mark the items as suspect. This adds a flag to the items to indicate they should be reviewed. See Marking Items as Suspect, page 82.
172
Ed it in g ad d it ion al issu e r e p or t s
Editing additional issue reports

1. Select the issue with the record you want to edit. 2. Choose Edit > Edit Issue. The Edit Issue dialog box opens. 3. Click the Detail tab and select the report you want to edit. 4. Make any changes and click OK.
Duplicating issues
If you add issues with the same basic information, you can save time by duplicating and editing an existing issue. 1. Select the issue on the Issues list window. 2. Choose Edit > Duplicate Issues. The Duplicate Issue Options dialog box opens.
3. Select Link duplicated issue with original to link the new issue with the original issue.
n n
Select a Link definition. The list includes all issue link definitions. Enter a Link comment. The comment is displayed on the issue Links tab and in the link diagram.
4. Select Identify original issue in system comment to add a system comment to the Workflow tab of the new issue that indicates the original issue number and summary. 5. Select Identify original issue in Description text to add a line to the Description field of the new issue that indicates the original issue number and summary. 6. Select the information to copy from the original issue.
173
M e r gin g issu e s
n n n n n n
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 issue to the same folder as the original issue. Issues can only be copied to folders you have access to.
7. Click OK. The issue is duplicated and assigned the next available issue number. 8. Modify the issue and save the changes.
Merging issues
You can merge issues that report the same issue. When issues are merged, the original issues are deleted from the project. All issue information is retained as multiple issue records. For example, if you merge three issues, the Detail tab shows three records. Each record includes the original issue information. Note: When issues are merged, the original issues are deleted from the project and the resulting issue assumes the lowest number. If you want to maintain unique issues you can link issues instead. See Linking Items, page 77. 1. Select the issues you want to merge. To select a range of issues, click the first issue in the range then Shift+click the last issue. To select multiple issues not in a range, Ctrl+click each issue. 2. Choose Edit > Merge Issues. You are prompted to confirm the merge. 3. Click OK. The issues are merged. The resulting issue assumes the lowest issue number and the type, priority, and severity of that issue.
Assigning issue numbers

After you review deferred issues, you can assign issue numbers to them. 1. Select the unnumbered issue on the Issues list window. 2. Choose Activities > Assign Issue Numbers. The issue is assigned the next available issue number.
Renumbering issues
You can renumber issues at any time. For example, deleting and merging issues may leave gaps in the issue numbers and you may want to renumber the issues.
174
De l e t in g ad d it ion al issu e r e p or t s
1. Select the issue you want to renumber. 2. Choose Activities > Renumber Issues. The Renumber Issues dialog box opens. The number is set to the next available issue number.
3. Enter a new issue number and click OK. The Renumber Issues dialog box closes and the issue is renumbered.
n
If the renumbered issue number is higher than the next available issue number, the next available issue number is set to one higher than the renumbered issue. If you renumber the entire issue list, the next available issue number must be set to one greater than the highest issue number.
Deleting additional issue reports

1. Select the issue on the Issues list window. 2. Choose Edit > Edit Issue. The Edit Issue dialog box opens. 3. Choose Activities > Delete Reported By. The additional report is deleted.
Deleting issues
1. Select the issue on the Issues list window. You can select more than one issue to delete. 2. Click Delete on the Issues list window. You are prompted to confirm the deletion. 3. Click Yes. The issue is deleted.
Creating Test Cases From Issues

If you use TestTrack TCM, you can create test cases from issues. The issue information is copied to the test case so users can review the details and add information to complete the test case details. 1. Click Create Test Case in the Edit Issue dialog box. The Add Test Case dialog box opens. It is populated with the following issue information by default:
n n
Summary fieldIncludes the issue number and summary. Steps tabIncludes the steps to reproduce.
175
Cr e at in g Re q u ir e me n t s Fr om Issu e s
Files tabIncludes file and source code attachments. Note: Depending on the item mapping rules configured for the project, additional information may be copied from the issue. See Configuring Item Mapping Rules, page 460.
2. Make any changes. 3. Click Add when you finish entering the test case information. You may be prompted to link the test case with the related issue. Click Add Link if you want to create a link or click Do Not Link if you do not want to create a link. See Linking Items, page 77. The test case is saved and added to the project.
Creating Requirements From Issues

If you use TestTrack RM, you can create requirements from issues. For example, you may create a requirement from a feature request you want to implement in an upcoming release. The issue information is copied to the requirement so users can review the issue details when defining additional requirement details. 1. Click Create Requirement in the Edit Issue dialog box. The Select Requirement Type dialog box opens. 2. Select a requirement type. Make sure you select the correct requirement type because cannot change it after you add the requirement. 3. Click OK. The Add Requirement dialog box opens. It is populated with the following requirement information by default:
n n n
Summary fieldIncludes the issue number and summary. Description fieldIncludes the issue description from each Reported by record. Detail tabCustom issue field values are copied if a requirement custom field with the same field name and type exists. Files tabIncludes source code attachments.
176
M an agin g Te st Con figs
Note: Depending on the item mapping rules configured for the project, additional information may be copied from the issue. See Configuring Item Mapping Rules, page 460.
4. Make any changes. 5. Click Add when you finish entering the requirement information. You may be prompted to link the requirement with the related issue. Click Add Link if you want to create a link or click Do Not Link if you do not want to create a link. See Linking Items, page 77. The requirement is saved and added to the project.
Managing Test Configs

A test configuration generally refers to a specific computer used for testing and the hardware and software found on this computer. Tracking test configurations helps identify patterns in issues that may be related to specific hardware or software. You can verify that an application functions the same, or in a similar manner, across all supported platforms or configurations.
Adding test configs

1. Click Add on the Test Configs list window. The Add Test Config dialog box opens with the CPU tab selected. 2. Enter a Name to uniquely identify the test config. 3. Enter the information on the CPU tab.
n
Click Capture Config if you are entering a test config for the computer you are currently working with. TestTrack can automatically fill in some of the fields. This option is only available to Windows users. Enter information in the other CPU fields.
4. Click the Peripherals tab and enter the peripherals information. These fields are optional but you should enter as much information as possible. 5. Click Add. The test config is added.
177
Vie win g t e st con figs
Viewing test configs

1. Select the test config on the Test Configs list window. 2. Choose Edit > View Test Config or click View on the Test Configs list window. The read-only View Test Config dialog box opens. 3. Click Edit to edit the test config. See Editing test configs, page 178. 4. Click OK when you are finished. You return to the Test Configurations list window.
Editing test configs

1. Select the test config on the Test Configs list window. 2. Choose Edit > Edit Test Config. The Edit Test Config dialog box opens. 3. Make any changes and click OK. The changes are saved.
Duplicating test configs

If you add test configs with the same basic information, you can save time by duplicating and editing an existing config. 1. Select the test config on the Test Configs list window. 2. Choose Edit > Duplicate Test Config. The test config is duplicated and a number is added to the end of the config name. For example, if you duplicate Eng-cube, the duplicated test config is named Eng-cube1. 3. Modify the duplicated test config and save the changes.
Deleting test configs

1. Select the test config on the Test Configs list window. You can select more than one test config to delete. 2. Choose Edit > Delete Test Config. You are prompted to confirm the deletion. 3. Click Yes.
Creating Release Notes

You can add release notes to issues. Before your product is released, you can build a text-based release notes file that can be included in a Read Me file or distributed directly to customers. See Building release notes, page 179. 1. Select the issue and choose Activities > Release Notes.
178
B u il d in g r e l e ase n ot e s
The Release Notes dialog box opens.
2. Select a Release Notes By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the Release Version. 5. Enter the release Notes. The notes are recorded with the issue history. 6. Click OK.
Building release notes

Note: To generate release notes for specific issues, select the issues on the Issues list window. If you do not know which issues contain release notes, add a column to the Issues list window to display the Has Release Notes field. 1. Choose File > Build Release Notes. The Build Release Notes dialog box opens.
2. Enter the From version and the Through version you want to include in the release notes. If the release notes are specific to one version, enter the same version number in both fields.
179
B u il d in g r e l e ase n ot e s
3. Select a filter from the Use Filter list to generate release notes for issues that meet the filter criteria. 4. Select a product from the Limit to Product menu to generate release notes for a specific product. 5. Select Only include issues selected in the issue list to include only the issues you selected in the Issues list window. 6. Select any Presentation Options.
n
Select Sort versions from newest to oldest to sort the release notes in order starting with the newest version. Select Insert a blank line between each release note to add a blank line between each note. Optionally enter a character in the Begin each release note with field. You can also enter ASCII characters or leave the field empty.
n n
7. Click Preview. The Release Notes preview dialog box opens. You can edit the release notes if necessary. 8. Click Create and Save to save the release notes. The Save Release Notes As dialog box opens. 9. Select a location and enter a filename. 10. Click Save. The release notes are generated and saved in the specified location.
180
Using TestTrack RM
This guide includes information for working with the requirements and requirement documents you track and manage with TestTrack RM.
About default requirement types

Every requirement has an assigned requirement type, which helps you identify the purpose of each requirement and manage groups of requirements. Each requirement has a unique tag that includes a number and an identifier to help you distinguish between different requirement types. Note: If you have administrative privileges, you can modify the default requirement types or add new ones. See Configuring Requirement Types, page 381. Requirement Tag Description type identifier Business requirement BRDescribe overall business needs that must be fulfilled. These requirements focus on organizational goals, business rules, and processes that must be supported and are typically provided by project stakeholders, business users, or customers. Describe what the product or service you are developing must do. For example, in software development projects, functional requirements describe the specific behavior and functions of the software. Functional requirements generally support any defined business requirements. Describe the attributes or qualities of the product or service you are developing and any constraints that must be considered. These requirements may expand on functional requirements to explain the qualities the defined functionality must have. For example, non-functional requirements may focus on qualities such as usability, performance, reliability, and security.
Functional requirement
FR-
Nonfunctional requirement
NFR-
Adding Requirement Documents

Requirement documents group and organize a set of related requirements. For example, you may want to add a requirement document to group requirements based on functional area, release, or component. You can add requirement documents before or after you add requirements to a project. If you add a requirement document first, you can add new or existing requirements to it. If you add requirements first, you can add a requirement document when you are ready to organize the requirements and add them to the document. 1. Choose Create > Requirement Document. The Add Requirement Document dialog box opens with the Detail tab selected.
181
Ad d in g Re q u ir e me n t Docu me n t s
2. Enter the requirement document information.

n n
Enter a requirement document Name. You can enter up to 255 characters. Status displays the requirement document workflow state and assignment information. New requirement documents are in the Draft state. See About the default requirement documents workflow, page 211. Enter a Description to provide information about the requirement document. For example, you may want to explain the purpose of the requirement document. Note: Use the formatting toolbar to apply formatting and add images and tables to the description. See Formatting text, page 49.
3. Enter or select details about the requirement document on the Detail tab. See Entering requirement document details, page 183. 4. Click the Files tab to attach files to the requirement document. See Attaching Files, page 54. If TestTrack is integrated with a source control tool, you can also attach source code files. See Attaching source code files, page 499. 5. Click Add when you finish entering the requirement document information or click Add and Open Specification Document to add the requirement document and open it in the Specification Document window. See Using the Specification Document Window, page 186. The requirement document is saved and added to the project. Note: To add a requirement document that includes requirements, select the requirements on the Requirement list window, right-click, and choose Create Requirement Document. You can also import Microsoft Word requirement documents. See Importing Requirement Documents from Microsoft Word, page 249.
182
Ad d in g Re q u ir e me n t s
Entering requirement document details

You can enter requirement document details to provide more information about a document, such as its owner and the project it applies to. The following information applies to the default requirement document detail fields. Your organization may use different fields. Note: If you have administrative privileges, you can customize the fields on the Detail tab. To change the existing fields or add new fields, see Configuring Custom Fields, page 384. To change the list values, see Modifying Value Lists, page 379. 1. Click the Detail tab when you are adding or editing a requirement document.
2. Select the requirement document Owners. Owners are typically responsible for approving requirement documents. For example, owners may be stakeholders or subject matter experts. Click the Find button to search for owners. See Finding users and customers, page 39. 3. Select the Project the requirement document applies to. 4. Select the Release the requirement document applies to. 5. Click Add or OK to save the changes.
Adding Requirements
Add requirements to TestTrack to start adding content to and tracking them. You can enter details about a requirement when you add it or as you learn more about the requirement. Team members in a variety of roles, such as stakeholders, subject matter experts, developers, and testers, will use the requirement. Make sure each requirement clearly communicates a specific need. Note: The following information explains how to add an individual requirement. You can also add requirements to a requirement document. See Adding new requirements to requirement documents, page 193. 1. Choose Create > Requirement. The Select Requirement Type dialog box opens.
183
2. Select a requirement type. 3. Click OK. The Add Requirement dialog box opens with the Detail tab selected.
4. Enter the requirement information.

n n
Enter a requirement Summary. You can enter up to 255 characters. Status displays the requirement workflow state and assignment information. New requirements are in the Draft state. See About the default requirements workflow, page 202. Version displays the requirement version number, which is <current> for new requirements. Type displays the selected requirement type. Select the requirement Importance. Entered By defaults to the logged in user or you can select another user. Date Entered defaults to the current date or you can enter another date. Enter a requirement Description to provide specific information about the requirement.
n n n n n n
184
Tip: Use the formatting toolbar to apply formatting and add images and tables to the description. See Formatting text, page 49. 5. Enter or select additional requirement information on the Detail tab. See Entering requirement details, page 185. 6. Optionally click the Files tab to attach files to the requirement. See Attaching Files, page 54. If TestTrack is integrated with a source control tool, you can also attach source code files. See Attaching source code files, page 499. 7. Click Add when you finish entering the requirement information. The requirement is saved and added to the project. Note: After you add a requirement, you can add it to a requirement document at any time. See Adding existing requirements to requirement documents, page 193.
Entering requirement details

You can enter requirement details to provide more information about a requirement, such as its owner and risk to the project. The following information applies to the default requirement detail fields. Your organization may use different fields. Note: If you have administrative privileges, you can customize the fields on the Detail tab. To change the existing fields or add new fields, see Configuring Custom Fields, page 384. To change the list values, see Modifying Value Lists, page 379. 1. Click the Detail tab when you are adding or editing a requirement.
2. Select the requirement Owners. Requirement owners are typically responsible for approving requirements. For example, owners may be stakeholders or subject matter experts. Click the Find button to search for owners. See Finding users and customers, page 39. 3. Select the Origin to indicate where the requirement came from. 4. Select the Source to indicate who provided the requirement, such as a customer. Click the Find button to search for owners. See Finding users and customers, page 39. 5. Select the requirement Risk.
185
U sin g t h e S p e cificat ion Docu me n t Win d ow
Your organization's use of this field depends on your definition of risk. For example, risk may indicate the impact of not implementing a requirement, the number of unknown issues related to the requirement, or other factors. 6. Select the Difficulty to indicate how difficult it is to implement the requirement. 7. Select the Product the requirement applies to. 8. Select the Release the requirement applies to. 9. Click Add or OK to save the changes.
Using the Specification Document Window

The Specification Document window displays the requirements in a requirement document in a hierarchical outline format. You will perform most of your work in this window if you are responsible for developing or reviewing requirements and requirement documents. The Specification Document window includes two views.
n
Document View is used for adding, modifying, and organizing requirements in a requirement document. You can also enter workflow events on requirements and requirement documents in this view. See Modifying Requirement Documents, page 191. Review Mode View is used for reviewing and commenting on requirements and requirement documents. You can enter review workflow events, such as Review Note and Comment, in this view. See Reviewing Requirements and Requirement Documents, page 221.
1. Choose View > Requirement Documents to open the Requirement Documents list window. 2. Select a requirement document and click Open Specification Document. The Specification Document window opens. Note: You can only open five instances of the Specification Document window at once. 3. Choose View > Specification Document View Mode and then choose the view you want to work in.
Customizing the Specification Document window

You can customize the Specification Document window to change how information is displayed.
Hiding the formatting toolbar

1. Right-click the Specification Document toolbar and choose Hide Formatting Toolbar to hide the toolbar. 2. To display the toolbar, right-click the Specification Document window toolbar and choose Show Formatting Toolbar.
Displaying numeric column totals

You can insert column footers to display the total value of numeric columns. This is useful for viewing time tracking information, such as estimated and actual hours, and other numeric field data.
186
Cu st omiz in g t h e S p e cificat ion Docu me n t win d ow
1. Right-click the Specification Document toolbar and choose Show Numeric Column Totals to display the totals. A column footer row is added to all Specification Document windows and displays totals for visible numeric columns. Note: If a requirement is shared multiple times in the requirement document, a column total only includes one instance of the numeric field. 2. To hide totals, right-click the Specification Document window toolbar and choose Hide Numeric Column Totals.
Hiding requirement summaries

You can display only the requirement outline number and tag in the requirement tree. 1. Right-click the Specification Document toolbar and choose Hide Requirement Summary in Tree. 2. To display the number, tag, and summary, right-click the toolbar and choose Show Requirement Summary in Tree.
Adjusting document width

You can adjust the width of the Specification Document window to display more or less text on each line. 1. Right-click the Specification Document window toolbar and choose Set Specification Document Width. The Set Specification Document Width dialog box opens.
2. Select a width option.

n
Use default document width uses the default width set in the local options. Click Set default width to change the defaults. See Setting formatting options, page 346. Set document width to set a specific width for the open document. Enter the Page Width to display text in before it wraps to the next line and enter the Left Margin to indent text relative to the first column in the detail area.
Hiding field labels

You can hide multi-line text field labels to reduce the amount information displayed in the details area. 1. Right-click the Specification Document window toolbar and choose Hide Multi-Line Field Labels.
187
Ab ou t r e q u ir e me n t an d r e q u ir e me n t d ocu me n t in d icat or s
2. To display field labels, right-click the toolbar and choose Show Multi-Line Field Labels. Tip: You can also sort, insert, change, move, or remove columns in the Specification Document window. See Using List Windows, page 21. If you frequently customize the Specification Document window, you may want to create a view to save the column layout, sorting, and other changes. See Creating User-Defined Views, page 28.
About requirement and requirement document indicators

The following indicators are displayed in the Specification Document window to point out additional information about requirements and requirement documents. Icon Description The requirement or requirement document is locked. Click the lock to view more information. See Viewing lock information, page 221. The requirement or requirement document is marked as suspect because a related item changed. Click the flag to view the dependencies. See Investigating suspect dependencies, page 83. The requirement is shared with another requirement document. The requirement changed since the last requirement document snapshot was captured.
You are editing the requirement and the changes have not been saved.
You cannot edit the requirement because you do not have security access to edit it, it is locked for editing by another user, you are editing it in the Edit Requirement dialog box, or it is locked through the workflow. A message that explains the reason you cannot edit the requirement is displayed. If you are already editing the requirement, click the Go To link to go to the Edit Requirement dialog box.
Using Document View

You can use Document View in the Specification Document window to add, modify, organize, and remove requirements or view snapshots of previous versions. Requirement documents are displayed in an outline format. Outline numbers are automatically assigned to requirements based on their position in the requirement document.
188
U sin g Docu me n t Vie w
Information is displayed in the following areas: Area Header Description Displays the requirement document name, status and assignment information, and document description. Provides access to commands to add, reorganize, remove, and filter requirements. Hierarchically displays the requirements in the requirement document. Requirements are labeled with the outline number, requirement tag, and requirement summary. Click a requirement to select the corresponding requirement in the details area. Double-click a requirement to edit it in the Edit Requirement dialog box. Displays the requirements included in the requirement document. Double-click a requirement to edit it. See Editing Requirements in the Specification Document Window, page 195.
Toolbar Requirements tree
Detail
Note: Indicators, such as locks and flags, are displayed to point out additional information. See About requirement and requirement document indicators, page 188.
Document View toolbar

The Document View toolbar includes commands to add, reorganize, and remove requirements in the requirement document. Tip: Right-click the Document View toolbar to customize how requirements are displayed in the details area. See Customizing the Specification Document window, page 186. Button Action Add a requirement to the requirement document. See Adding Requirements to Requirement Documents, page 192.
189
U sin g Re vie w M od e Vie w
Button Action Remove the selected requirement from the requirement document. See Removing Requirements from Documents, page 196. Move a requirement up one level in the requirement document hierarchy. Move the selected requirement down one level in the requirement document hierarchy. Make the selected child requirement a parent or sibling requirement. Make the selected parent requirement a child requirement.
Using Review Mode View

If you need to review a requirement document and provide feedback, you can use Review Mode View in the Specification Document window. Review Mode View provides a hierarchical view of all requirements in a requirement document and allows you to add review notes on requirements and the entire document.
Information is displayed in the following areas: Area Header Description Displays the requirement document name, status and assignment information, and document description. Provides access to commands to add, display, and navigate review notes and filter requirements.
Toolbar
190
M od ifyin g Re q u ir e me n t Docu me n t s
Area Requirements tree
Description Hierarchically displays requirements in the requirement document. Requirements are labeled with the outline number, requirement tag, and requirement summary. Click a requirement to select the corresponding requirement in the details area. Double-click a requirement to edit it in the Edit Requirement dialog box. Displays the requirements included in the requirement document. Double-click a requirement to edit it. See Editing Requirements in the Specification Document Window, page 195. Displays requirement document review notes. See Adding requirement document review notes, page 222.
Details
Document Notes
Note: Indicators, such as locks and flags, are displayed to point out additional information. See About requirement and requirement document indicators, page 188.
Review Mode View toolbar

The Review Mode View toolbar provides access to commands to navigate and add requirement review notes. Note: Right-click the Review Mode toolbar to customize how requirements are displayed in the details area. See Customizing the Specification Document window, page 186. Button Action Go to the previous requirement review note in the requirement document. Go to the next requirement review note in the requirement document. Filter the review notes displayed in the requirement document. You can view all notes since the last snapshot, all notes, only notes you add during the previous review sessions or the current session, or hide all notes. Add a review note to the selected requirement. See Adding requirement review notes, page 223.
Modifying Requirement Documents

You can add, reorganize, and remove requirements in requirements documents in Document View in the Specification Document window. You can also view snapshots of previous requirement documents. See Using Document View, page 188. 1. Select the requirement document you want to modify on the Requirement Documents list window and click Open Specification Document. The Specification Document window opens in Document View.
191
Ad d in g Re q u ir e me n t s t o Re q u ir e me n t Docu me n t s
2. To view a snapshot of the requirement document, select the snapshot from the version list in the header area. The window changes to gray to indicate you are viewing a read-only snapshot. Select <Current Version> to view the current requirement document. Note: You can only enter review workflow events on snapshots. 3. Optionally select a Filter to display specific requirements. For example, you may only want to view business requirements. You can also filter the columns in the details area. See Filtering list window columns, page 24. Note: You cannot apply filters to snapshots. 4. Click the Add toolbar button to add requirements. See Adding Requirements to Requirement Documents, page 192. 5. Double-click a requirement to edit the summary, description, and other fields. See Editing Requirements in the Specification Document Window, page 195. To edit information that is not displayed in the Specification Document window, such as custom fields or workflow events, select a requirement and choose Edit > Edit Requirement in Detail Window. See Editing Requirements, page 198. Note: You cannot edit historical requirement versions included in requirement document snapshots. 6. Select a requirement and click the arrows in the toolbar to move the requirement or change the requirement document hierarchy. 7. Select a requirement and choose Edit > Remove Requirement to remove it. See Removing Requirements from Documents, page 196. Note: Indicators, such as locks and flags, are displayed to point out additional information. See About requirement and requirement document indicators, page 188.
Adding Requirements to Requirement Documents

After you create a requirement document, you need to add requirements to it. You can use the following methods to add requirements to requirement documents:
n
Add new requirements directly to a requirement documentSee Adding new requirements to requirement documents, page 193. Adding existing requirements to a specific location in a requirement documentSee Adding existing requirements to requirement documents, page 193. Append existing requirements to the end of a requirement documentSee Appending requirements to requirement documents, page 194.
192
Adding new requirements to requirement documents

You can add requirements to requirement documents and enter the requirement information at the same time. New requirements are added as siblings or children of other requirements in the requirement document. 1. Open the Specification Document window for the requirement document you want to add the requirement to. Make sure Document View is selected. 2. Select the requirement above where you want to add the new requirement. Child requirements are added one level under the selected requirement. Sibling requirements are added at the same level as the selected requirement. 3. Click the Add button and select Add Requirement as Child or Add Requirement as Sibling. The Select Requirement Type dialog box opens. 4. Select a requirement type. 5. Click OK. The Add Requirement dialog box opens with the Detail tab selected. 6. Enter the requirement information. See Adding Requirements, page 183. 7. Click Add when you finish entering the requirement information. The requirement is saved and added to the project.
Adding existing requirements to requirement documents

You can add existing requirements to requirement documents. Requirements can be shared between requirement documents or a new copy can be created. 1. Open the Specification Document window for the requirement document you want to add the requirement to. Make sure Document View is selected. 2. Select the requirement above where you want to add the requirement. 3. Click the Add button and select Add Existing Requirement. The Select Requirements to Add dialog box opens.
193
Tip: This dialog box includes many of the same functions as the Requirements list window. For example, you can filter the requirements or search for specific requirements. 4. Select the requirement you want to add. 5. Click Add as Sibling to add the requirements as siblings or click Add as Child to add the requirements as children. Child requirements are added one level under the selected requirement. Sibling requirements are added at the same level as the selected requirement. 6. If the requirement is already in another requirement document, you are prompted to share or copy the requirement.
n
Click Share to add the existing requirement to the requirement document and create a share between the requirements. If a shared requirement is modified, the changes are made in all requirement documents the requirement is included in. Click Copy to create a copy of the existing requirement and adds it to the requirement document.
Tip: You can also drag requirements from the Requirements or Folders list windows or from another Specification Document window to add them to a requirement document.
Appending requirements to requirement documents

If a requirement in the requirement document you are working on applies to another document, you can append the requirement to the end of the other document without opening it. If the appended requirement has child requirements, they are also appended to the requirement document. Appended requirements can be shared between requirement documents or a new copy of the requirement can be appended. 1. Open the Specification Document window for the requirement document that contains the requirement you want to append. Make sure Document View is selected. 2. Right-click the requirement you want to append and choose Append to Requirement Document. The Select Requirement Document dialog box opens.
194
Ed it in g Re q u ir e me n t s in t h e S p e cificat ion Docu me n t Win d ow
Tip: This dialog box includes many of the same functions as the Requirement Documents list window. For example, you can filter the requirement documents or search for specific documents. 3. Select the requirement document you want to append the requirement to. 4. Select an option to indicate how to requirements should be copied to the requirement document.
n
Copy the requirements and add the copies to the selected requirement document creates a copy of the existing requirement and adds it to the selected requirement document. Share the existing requirements with the selected requirement document adds the requirement to the selected requirement document and creates a share between the requirements. If a shared requirement is modified, the changes are made in all documents the requirement is included in.
5. Click Select. The requirement is appended to the requirement document.
Editing Requirements in the Specification Document Window

You can edit requirements directly in the Specification Document window. This helps you make changes within the context of the entire requirement document and work on changes to several requirements at once instead of opening each requirement you want to edit individually. Keep the following in mind:
n
To enter or modify requirement workflow events or edit other information that is not displayed in the Specification Document window, select the requirement and choose Edit > Edit Requirement in Detail Window. See Editing Requirements, page 198. If the current requirement version is shared in multiple requirement documents, all instances of the requirement are updated. You cannot edit requirements in requirement document snapshots.
1. Double-click a requirement in the Detail area in the Specification Document window. The requirement opens in edit mode. A red line and pencil icon are displayed to indicate you are editing the requirement. Other indicators may be displayed to provide additional information about the requirement. See About requirement and requirement document indicators, page 188.
195
M ovin g Re q u ir e me n t s b e t we e n Re q u ir e me n t Docu me n t s
2. Make any changes and click Save to save the selected requirement. Click Save All to save changes to all modified requirements. Click Don't Save to discard the changes. When you are prompted to confirm the deletion, click Don't Save. Note: You may be prompted to enter an electronic signature and change reason when saving requirements. See Entering Electronic Signatures, page 477.
Moving Requirements between Requirement Documents

You can drag requirements between requirement documents in different Specification Document windows. You can only move requirements into documents you have security privileges to edit. 1. Open the Specification Document windows for the requirement document that you want move the requirement to and the requirement document that contains the requirement. 2. Select the requirement you want to move in the requirement tree. To select more than one requirement, Ctrl+click each requirement. 3. Drag the requirement to the requirement document tree you want to move it to and select Move requirements. The requirement is added to the new requirement document and removed from the previous document. Note: You can also copy or share requirements between requirement documents. See Appending requirements to requirement documents, page 194.
Removing Requirements from Documents

You can remove a requirement from a requirement document if the requirement is no longer used. Removed requirements are not deleted from TestTrack. 1. Open the Specification Document window for the requirement document you want to remove the requirement from. Make sure Document View is selected. 2. Select a requirement and choose Edit > Remove Requirement. 3. If you are removing a requirement with child requirements, you are prompted to delete the child requirements. Click Yes to remove the requirement and child requirements or click No to only remove the parent requirement. The requirement is removed from the requirement document.
Unsharing Requirements
If a shared requirement is modified, the changes are made in all requirement documents it is included in. If you want to change a requirement without affecting it in other requirement documents, you can break the requirement share. This creates a copy of the existing requirement and adds it to the requirement document, which allows you to maintain separate requirements. 1. Open the Specification Document window for the requirement document that includes the requirement you want to unshare. Make sure Document View is selected.
196
Vie win g Re q u ir e me n t s
2. Right-click a shared requirement and choose Break Requirement Share. The requirement is unshared.
Viewing Requirements
You can view read-only requirement information. You can also send email, perform requirement activities, and generate test cases when viewing requirements. 1. Select the requirement on the Requirements list window or the Specification Document window. 2. Choose Edit > View Requirement. The View Requirement dialog box opens with the Overview tab selected, which displays a summary of requirement workflow activities and tracked emails.See Using the Overview tab, page 12. 3. The Status field displays the requirement workflow state and assignment information.
n
A lock is displayed if the requirement is locked by the requirement or requirement document workflow. Click the lock to view lock information. See Viewing lock information, page 221. A flag is displayed if the requirement is marked as suspect because a related item changed. Click the flag to view the dependencies. See Investigating suspect dependencies, page 83.
4. Click Generate Test Cases to generate a test case based on the requirement. See Generating Test Cases from Requirements, page 241. 5. Click Send Email to email users about the requirement. See Emailing from TestTrack, page 73. 6. Click Edit to edit the requirement. See Editing Requirements, page 198. 7. Click OK to close the View Requirement dialog box.
Viewing Related Requirement Documents

From a requirement, you can view the requirement documents the requirement is included in. All versions of the requirement in all requirement document snapshots are available. 1. Click the Documents tab when you are viewing or editing a requirement. Information is displayed in the following columns:
n n n n n
DocumentThe requirement document that includes the requirement. Snapshot LabelThe snapshot label that includes the requirement. Snapshot VersionThe snapshot version that includes the requirement. Requirement VersionThe requirement version included in the snapshot. LocationThe section number of requirement in the requirement document.
2. Select a document and click View to open it in the Specification Document window.
197
Ed it in g Re q u ir e me n t s
The Specification Document window opens. See Using the Specification Document Window, page 186.
Editing Requirements
You can edit a requirement to add additional information or make changes based on review comments or changes to related items. If the current requirement version is shared in multiple requirement documents, all instances of the requirement are updated. Tip: If you need to update field values for multiple requirements, use bulk field changes. This allows you to quickly update multiple records simultaneously. See Updating Multiple Items, page 84. 1. Select the requirement on the Requirements list window. You can also edit requirements directly in the Specification Document window. See Editing Requirements in the Specification Document Window, page 195. 2. Choose Edit > Edit Requirement. The Edit Requirement dialog box opens. Note: If another user is editing the requirement, a read-only icon is displayed next to the OK button. When the user closes the requirement, it is updated and becomes available for editing. 3. Make any changes.
n
A lock is displayed next to the Status field if the requirement is locked. Depending on your security permissions, you may not be able to edit locked requirements. Click the lock to view more information. See Viewing lock information, page 221. A flag is displayed next to the Status field if the requirement is marked as suspect because a related item changed. Click the flag to view the dependencies. See Investigating suspect dependencies, page 83. Note: To change the requirement type, see Changing requirement types, page 200.
4. Click Generate Test Case to create a test case based on the requirement. See Generating Test Cases from Requirements, page 241. 5. Click Send Email to email a user or customer. See Emailing from TestTrack, page 73. Click the Email tab to view, reply to, or delete tracked email. See Viewing tracked email, page 75 and Replying to tracked email, page 76. 6. Click OK to save the changes. Note: If the changes impact linked or related items, you may want to mark the items as suspect. This adds a flag to the items to indicate they should be reviewed. See Marking Items as Suspect, page 82.
198
Du p l icat in g r e q u ir e me n t s
Duplicating requirements
If you add requirements with the same basic information, you can save time by duplicating and editing an existing requirement. Note: You can also copy a requirement between specification documents. Copying creates a new requirement with the same information as the original requirement, while duplicating lets you choose the information to include. See Using the Specification Document Window, page 186. 1. Select the requirement on the Requirements list window or the Specification Document window. 2. Choose Edit > Duplicate Requirement. The Duplicate Requirement Options dialog box opens.
3. Select Link duplicated requirement with original to link the new requirement with the original requirement.
n n
Select a Link definition. The list includes all requirement link definitions. Enter a Link comment. The comment is displayed on the requirement Links tab and in the link diagram.
4. Select Identify original requirement in system comment to add a system comment to the Workflow tab on the new requirement that indicates the original requirement number and summary. 5. Select the information to copy from the original requirement.
n n n n n
Select History information to copy information from the History tab. Select File attachments to copy file attachments from the Files tab. Select SCC attachments to copy source code attachments from the Files tab. Select Workflow to copy workflow information from the Workflow tab. Select Email messages to copy emails from the Email tab.
199
Ch an gin g r e q u ir e me n t t yp e s
Select Folder information to copy the new requirement to the same folder as the original requirement. Requirements can only be copied to folders you have access to. Click Select All to select all options or click Select None to clear the selected options.
6. Click OK. The requirement is duplicated and assigned the next available tag number. 7. Modify the requirement and save the changes.
Changing requirement types

You can change a requirement's type after it is added to a project. 1. Select the requirement in the Requirements list window, SpecificationDocument window, or Folders list window. To select more than one requirement, Ctrl+click each requirement. 2. Choose Edit >Change Requirement Type. The Select Requirement Type dialog box opens. 3. Select the new requirement type. 4. Click OK. The requirement type is changed.
Assigning requirement numbers

After you review deferred requirements, you can assign requirement numbers to them. 1. Select the unnumbered requirement on the Requirements list window. 2. Choose Activities > Assign Requirement Numbers. The requirement is assigned the next available requirement number. If the requirement type uses a tag, it is added to the number.
Renumbering requirements
You can renumber requirements at any time. For example, deleting requirements may leave gaps in requirement numbers and you may want to renumber the requirements. 1. Select the requirement you want to renumber. 2. Choose Activities > Renumber Requirements. The Renumber Requirements dialog box opens. The starting number is set to the next number.
3. Enter a new requirement number and click OK.
200
De l e t in g r e q u ir e me n t s
The Renumber Requirements dialog box closes and the requirement is renumbered.
n
If the renumbered requirement number is higher than the next available requirement number, the next available number is set to one higher than the renumbered requirement. If you renumber the entire requirement list, the next available requirement number must be set to one greater than the highest number.
Deleting requirements
A requirement cannot be deleted if:
n n n n
It is locked for editing by another user It is included in current versions of multiple requirement documents (shared) Versions of the requirement are included in a requirement document snapshot You do not have security permissions to delete requirements
Note: You can remove requirements from requirement documents, but they are not deleted. See Removing Requirements from Documents, page 196. 1. Select a requirement on the Requirements list window or the Specification Document window. You can select more than one requirement to delete. 2. Choose Edit > Delete Requirement. You are prompted to confirm the deletion. Note: If any of the selected requirements cannot be deleted, a dialog box that includes the requirement tag number and reason it cannot be deleted opens. Click OK to close the dialog box. 3. Click Yes. The requirement is deleted.
Working with Requirements

You may perform activities on a requirement, such as submitting it for review, reviewing it, and approving it. TestTrack RM guides you through the requirement management process and maintains a complete history of all activities performed on requirements. When a requirement is assigned to you, open the requirement and review the assignment notes. When you complete the assigned work, add information to the requirement about the work you completed and move the requirement to the next step in the process. This changes the requirement status and may assign the requirement to another user to keep the process moving. Note: TestTrack RM includes a default requirements workflow that your organization may use as is or customize for your organization. See About the default requirements workflow, page 202.
201
Ab ou t t h e d e fau l t r e q u ir e me n t s wor kfl ow
About the default requirements workflow

The default requirements workflow consists of the states, events, and transitions that define the path a requirement takes from initial entry to implementation. To move a requirement from state to state, the requirement is assigned to users who perform the event assigned to them. TestTrack RM's requirements workflow can be used out of the box or customized to support your business processes. See Customizing Workflows, page 414. The default requirements workflow includes the following events: Assign, Estimate, Enter Work, Ready for Review, No Changes Needed, Review Note, Ready for Approval, Approve, Reject, Needs Change, Mark Suspects, Implemented, Obsolete, Re-Open, and Comment. The steps you follow and available requirement events may differ depending on your organization's workflow.
Assigning requirements
To move a requirement through your requirement development, review, and approval process, you need to assign it to a user. For example, you may want to assign a draft requirement to another user who can estimate the time it will take to implement it. 1. Select the requirement and choose Activities > Assign. The Assign dialog box opens.
2. Select an Assign By user. This field defaults to the logged in user. 3. Select an Assign To user. Click the Find button to search for a user. See Finding users and customers, page 39. 4. The Date defaults to the current date and time. You can enter another date and time. 5. Enter any Notes. It is helpful to provide additional information about the assignment. For example, you can let the user know why you are assigning the requirement to them and the work you want them complete. 6. Select Due Date to set a due date. This field defaults to the current date. You can enter another date. 7. Click OK.
202
Note: When a requirement is assigned to you, open the requirement and click the Workflow tab to review the assignment notes. The user who assigned the requirement should let you know what work you are responsible for and provide detailed information. If you need more information, email the person who assigned the requirement. See Emailing from TestTrack, page 73.
Estimating requirement time

You can estimate the effort needed to work on a requirement. For example, you may want to enter the estimated effort to complete development of a requirement. After the estimate information is entered, you can track and view the time it takes to complete the requirement. 1. Select the requirement and choose Activities > Estimate. The Estimate dialog box opens.
2. Select an Estimate By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the Estimated Time in hours to work on the requirement. 5. Enter any Notes. It is helpful to include details about the activities included in the estimate. 6. Select Completion Date to set the date you expect to complete the work. This field defaults to the current date. You can enter another date. 7. Click OK.
Entering work on requirements

As you work on requirements, you can enter the work completed and work remaining to complete a requirement. This can keep the project manager informed about your progress. 1. Select the requirement and choose Activities > Enter Work. The Enter Work dialog box opens.
203
2. Select an Enter Work By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the Actual Effort in hours to work on the requirement. This information can help with future planning and metrics. 5. Enter any Notes. It is helpful to provide information about the work you completed so far. 6. Enter the Remaining Time in hours to complete the requirement. 7. Click OK.
Submitting requirements for review

A requirement needs to be reviewed after you complete a draft or make changes. For example, you may want a stakeholder to review a requirement to make sure it is accurate and complete. 1. Select the requirement and choose Activities > Ready for Review. The Ready for Review dialog box opens.
2. Select a Ready for Review By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to provide information about why you want the user to review the requirement or what changed since the last review. 5. Select Due Date to set a due date. This field defaults to the current date. You can enter another date. 6. Click OK.
204
The requirement status changes to Awaiting Review.
Requesting requirement changes

Changes may be needed after a requirement is reviewed. For example, you may indicate a requirement needs changes after a review cycle is complete. 1. Select the requirement and choose Activities > Needs Change. The Needs Change dialog box opens.
2. Select a Needs Change By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to provide details about the changes needed. 5. Optionally attach any files that a user needs to make the changes. See Attaching Files, page 54. 6. Click OK. The requirement status changes to Change Needed.
Accepting requirements after review

If you review a requirement and accept it, you can indicate that changes are not needed. 1. Select the requirement and choose Activities > No Changes Needed. The No Changes Needed dialog box opens.
205
2. Select a No Changes Needed By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. 5. Click OK. The requirement status changes to Reviewed.
Submitting requirements for approval

When a requirement is complete, you can submit it for approval. For example, you may submit a requirement to a project manager to approve it for an upcoming release. 1. Select the requirement and choose Activities > Ready for Approval. The Ready for Approval dialog box opens.
2. Select a Ready for Approval By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes.It is helpful to provide information about any changes made to the requirement after it was reviewed. 5. Select Due Date to set a due date. This field defaults to the current date. You can enter another date. 6. Click OK. The requirement status changes to Awaiting Approval and the requirement is locked to prevent changes.
206
Approving requirements
Approve requirements to indicate they are complete and ready for the next step in your process. For example, you may approve a requirement after all review feedback is implemented to indicate the requirement will be addressed in an upcoming release. 1. Select the requirement and choose Activities > Approve. The Approve dialog box opens.
2. Select an Approve By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to provide information about any changes made to the requirement after it was reviewed. 5. Click OK. The requirement status changes to Approved and the requirement is locked to prevent changes.
Rejecting requirements
You can reject a requirement if it is not complete or approved. For example, you may reject a requirement that will not be included in an upcoming release. 1. Select the requirement and choose Activities > Reject. The Reject dialog box opens.
2. Select a Rejected By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to provide details to explain why the requirement was rejected. 5. Click OK.
207
The requirement status changes to Not Approved and the requirement is unlocked so it can be modified.
Closing implemented requirements

Close a requirement after it is implemented. 1. Select the requirement and choose Activities > Implemented. The Implemented dialog box opens.
2. Select an Implemented By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to provide information about the implementation, such as the release version. 5. Click OK. The requirement status changes to Implemented and the requirement is closed.
Closing obsolete requirements

You can close an obsolete requirement if it is no longer needed. For example, a requirement is obsolete if it was dropped from a release. 1. Select the requirement and choose Activities > Obsolete. The Obsolete dialog box opens.
2. Select an Obsolete By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to explain why the requirement is obsolete.
208
5. Select a Reason for closing the requirement. 6. Click OK. The requirement status changes to Obsolete and the requirement is closed.
Reopening requirements
You can reopen obsolete requirements if you want to use them again. 1. Select the requirement and choose Activities > Re-Open. The Re-Open dialog box opens.
2. Select a Re-Open By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to explain why you are reopening the requirement. 5. Click OK. The requirement is reopened and the status changes to Draft.
Adding comments to requirements

You can add comments to a requirement to clarify information or add notes for other users. 1. Select the requirement and choose Activities > Comment. The Comment dialog box opens.
2. Select a Comment By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the comments in the Notes field. 5. Click OK. The comments are added to the requirement workflow history.
209
Vie win g r e q u ir e me n t wor kfl ow h ist or y
Note: To view requirement comments, view or edit the requirement and then click the Workflow tab. All comments are displayed on the Workflow tab.
Viewing requirement workflow history

You can view where a requirement is in the workflow, requirement assignments, and any comments or additional information entered about a requirement. You can also view time tracking information and a workflow history diagram. 1. Click the Workflow tab when you are viewing or editing a requirement. The events added to the requirement are displayed.
Note: Select Show System Comments to display events added by automation rules. 2. Click Work Items to view events with time tracking information, including the estimated, actual, and remaining work for the requirement. See Viewing work items, page 44. 3. Click Diagram to view a diagram of the workflow states the requirement was previously in, the events used to move the requirement between states, and next available states. See Viewing item workflow history diagrams, page 43. 4. Select an event to view the event notes. 5. Select an event and choose Edit > View Event to view the event details. See Viewing workflow event details, page 41. 6. Select an event and choose Edit > Edit Event to edit the event details. See Editing workflow event details, page 42. 7. Select an event and choose Edit > Delete Event to delete it. See Deleting workflow events from items, page 42. 8. Click OK to save the changes.
210
Wor kin g wit h Re q u ir e me n t Docu me n t s
Working with Requirement Documents

You may perform activities on a requirement document, such as submitting it for review, reviewing it, and approving it. TestTrack RM guides you through the requirement management process and maintains a complete history of all activities performed on requirement documents. When a requirement document is assigned to you, open the document and review the assignment notes. When you complete the assigned work, add information to the requirement document about the work you completed and move the document to the next step in the process. This changes the requirement document status and may assign the document to another user to keep the process moving. Note: TestTrack RM includes a default requirement documents workflow that your organization may use as is or customize for your organization. See About the default requirement documents workflow, page 211.
About the default requirement documents workflow

The default requirement documents workflow consists of the states, events, and transitions that define the path a requirement document takes from initial entry to implementation. To move a requirement document from state to state, the document is assigned to users who perform the event assigned to them. TestTrack RM's requirement documents workflow can be used out of the box or customized to support your business processes. See Customizing Workflows, page 414. The default requirement documents workflow includes the following events: Assign, Estimate, Enter Work, Ready for Review, No Changes Needed, Ready for Approval, Approve, Reject, Needs Change, Implemented, Obsolete, Re-Open, and Comment. The steps you follow and available requirement document events may differ depending on your organization's workflow.
Assigning requirement documents

To move a requirement document through your document development, review, and approval process, you need to assign it to a user. For example, you may want to assign a requirement document to another user who can estimate the time it will take to implement it. 1. Select the requirement document and choose Activities > Assign. The Assign dialog box opens.
211
Ab ou t t h e d e fau l t r e q u ir e me n t d ocu me n t s wor kfl ow
2. Select an Assign By user. This field defaults to the logged in user. 3. Select an Assign To user. Click the Find button to search for a user. See Finding users and customers, page 39. 4. The Date defaults to the current date and time. You can enter another date and time. 5. Enter any Notes about the assignment. It is helpful to provide additional information about the assignment. For example, you can let the user know why you are assigning the requirement document to them and the work you want them to complete. 6. Select Due Date to set a due date. This field defaults to the current date. You can enter another date. 7. Click OK. Note: When a requirement document is assigned to you, open the document and click the Workflow tab to review the assignment notes. The user who assigned the document should let you know what work you are responsible for and provide detailed information. If you need more information, email the person who assigned the document. See Emailing from TestTrack, page 73.
Estimating requirement document time

You can estimate the effort needed to work on a requirement document. For example, you may want to enter the estimated effort to complete development of a requirement document. After the estimate information is entered, you can track and view the time it takes to complete the requirement document. 1. Select the requirement document and choose Activities > Estimate. The Estimate dialog box opens.
2. Select an Estimate By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the Estimated Time in hours to work on the requirement document. 5. Enter any Notes. It is helpful to include details about the activities included in the estimate. 6. Select Completion Date to set the date you expect to complete the work. This field defaults to the current date. You can enter another date. 7. Click OK.
212
Entering work on requirement documents

As you work on requirement documents, you can enter the work completed and the work remaining to complete the document. This can keep the project manager informed about your progress. 1. Select the requirement document and choose Activities > Enter Work. The Enter Work dialog box opens.
2. Select an Enter Work By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the Actual Effort in hours to work on the document. This information can help with future planning and metrics. 5. Enter any Notes. It is helpful to provide information about the work you completed so far. 6. Enter the Remaining Time in hours to complete the requirement document. 7. Click OK.
Submitting requirement documents for review

A requirement document needs to be reviewed after you complete a draft or make changes. For example, you may want a stakeholder to review a requirement document to make sure it is accurate and complete. 1. Select the requirement document and choose Activities > Ready for Review. The Ready for Review dialog box opens.
213
2. Select a Ready for Review By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to provide information about why you want the user to review the requirement document or what changed since the last review. 5. Select Due Date to set a due date. This field defaults to the current date. You can enter another date. 6. Click OK. The requirement document status changes to Awaiting Review.
Requesting requirement document changes

Changes may be needed after a requirement document is reviewed. For example, you may indicate a requirement document needs changes after a review cycle is complete. 1. Select the requirement document and choose Activities > Needs Change. The Needs Change dialog box opens.
2. Select a Needs Change By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to provide details about the changes needed. 5. Optionally attach any files that a user needs to make the changes. See Attaching Files, page 54. 6. Click OK. The requirement document status changes to Change Needed.
Accepting requirement documents after review

If you review a requirement document and accept it, you can indicate that changes are not needed.
214
1. Select the requirement document and choose Activities > No Changes Needed. The No Changes Needed dialog box opens.
2. Select a No Changes Needed By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. 5. Click OK. The requirement document status changes to Reviewed.
Submitting requirement documents for approval

When a requirement document is complete, you can submit it for approval. For example, you may submit a requirement document to a project stakeholder for final sign off before implementation. 1. Select the requirement document and choose Activities > Ready for Approval. The Ready for Approval dialog box opens.
2. Select a Ready for Approval By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes.It is helpful to provide information about any changes made to the requirement document after it was reviewed. 5. Select Due Date to set a due date. This field defaults to the current date. You can enter another date. 6. Click OK. The requirement document status changes to Awaiting Approval and the document is locked to prevent changes.
215
Approving requirement documents

Approve requirement documents to indicate they are complete and ready for the next step in your process. For example, you may approve a requirement document to indicate all requirements are addressed and the document is ready to be used for implementation. 1. Select the requirement document and choose Activities > Approve. The Approve dialog box opens.
2. Select an Approve By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to provide information about the next steps after the approval. 5. Click OK. The requirement document status changes to Approved and the document is locked to prevent changes.
Rejecting requirement documents

You can reject a requirement document if it is not complete or approved. For example, you may reject a requirement document that will not be included in an upcoming release. 1. Select the requirement document and choose Activities > Reject. The Reject dialog box opens.
2. Select a Rejected By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to provide details to explain why the requirement document was rejected. 5. Click OK.
216
The requirement document status changes to Not Approved and the document is unlocked so it can be modified.
Closing implemented requirement documents

Close a requirement document after it is implemented. 1. Select the requirement document and choose Activities > Implemented. The Implemented dialog box opens.
2. Select an Implemented By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to provide information about the implementation, such as the release version. 5. Click OK. The requirement document status changes to Implemented and the document is closed.
Closing obsolete requirement documents

You can close an obsolete requirement document if it is no longer needed. For example, a requirement document is obsolete if it was dropped from a release. 1. Select the requirement document and choose Activities > Obsolete. The Obsolete dialog box opens.
2. Select an Obsolete By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to explain why the requirement document is obsolete.
217
5. Select a Reason for closing the requirement document. 6. Click OK. The requirement document status changes to Obsolete and the document is closed.
Reopening requirement documents

You can reopen obsolete requirement documents if you want to use them again. 1. Select the requirement document and choose Activities > Re-Open. The Re-Open dialog box opens.
2. Select a Re-Open By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to explain why you are reopening the document. 5. Click OK. The requirement document is reopened and the status changes to Draft.
Adding comments to requirement documents

You can add comments to a requirement document to clarify information or add notes for other users. 1. Select the requirement document and choose Activities > Comment. The Comment dialog box opens.
2. Select a Comment By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the comments in the Notes field. 5. Click OK. The comments are added to the requirement document workflow history.
218
Vie win g r e q u ir e me n t d ocu me n t wor kfl ow h ist or y
Note: To view requirement document comments, select the document, click View or Edit, and then click the Workflow tab. All comments are displayed on the Workflow tab.
Viewing requirement document workflow history

You can view where a requirement document is in the workflow, document assignments, and any comments or additional information entered about a document. You can also view time tracking information and a workflow history diagram. 1. Click the Workflow tab when you are viewing or editing a requirement document. The events added to the requirement document are displayed. The Snapshot column displays the historical snapshot number the event was performed on.
Note: Select Show System Comments to display events added by automation rules. 2. Click Work Items to view events with time tracking information, including the estimated, actual, and remaining work for the requirement document. See Viewing work items, page 44. 3. Click Diagram to view a diagram of the workflow states the requirement document was previously in, the events used to move the document between states, and next available states. See Viewing item workflow history diagrams, page 43. 4. Select an event to view the event notes. 5. Select an event and choose Edit > View Event to view the event details. See Viewing workflow event details, page 41. 6. Select an event and choose Edit > Edit Event to edit the event details. See Editing workflow event details, page 42. 7. Select an event and choose Edit > Delete Event to delete it. See Deleting workflow events from items, page 42. 8. Click OK to save the changes.
219
Lockin g Re q u ir e me n t s an d Re q u ir e me n t Docu me n t s
Locking Requirements and Requirement Documents

Requirements and requirement documents may be locked based on their workflow state. Locked items cannot be edited and actions you can perform on them are limited depending on your security permissions. For example, a requirement document may be locked when it is in an Awaiting Approval state to maintain the integrity of the completed draft. If a requirement document is locked, all requirements in the document are also locked. Items are only unlocked when they move to a state that removes the lock. If a requirement or requirement document is locked, you can view the status of the locked item when you are viewing or editing the item. See Viewing lock information, page 221. Note: If you have administrative privileges, you can configure workflow states to lock requirements and requirement documents. See Adding states, page 416.
Locked requirement actions

Allowed Entering workflow events Adding and removing requirements in requirement documents Adding, editing, and viewing links Viewing, sending, and replying to email Adding and removing requirements in folders Generating test cases Printing requirements Not allowed Editing fields Adding and removing file and source control attachments Bulk requirement field changes Assigning requirement numbers Renumbering requirements
Locked requirement document actions

Allowed Entering workflow events Adding, editing, and viewing links Viewing, sending, and replying to email Not allowed Editing fields Adding and removing file and source control attachments Adding, reordering, and removing requirements in requirement documents Bulk field changes
Adding and removing requirement documents in folders Creating snapshots Printing requirement documents
Assigning requirement numbers Renumbering requirements
220
Re vie win g Re q u ir e me n t s an d Re q u ir e me n t Docu me n t s
Viewing lock information

You can view information about locked items to find out why they are locked. Depending on your security permissions, you may not be able to edit locked requirements or requirement documents. 1. Click the lock when you are editing or viewing a requirement or requirement document or working in the Specification Document window. The View Lock Information dialog box opens.
2. Click OKwhen you are finished.
Reviewing Requirements and Requirement Documents

You may be asked to review requirement documents and provide feedback. You can view requirement documents in Review Mode View in the Specification Document window and add notes to requirements and documents. See Using Review Mode View, page 190. 1. Select the requirement document you want to review on the Requirement Documents list window and click Open Specification Document. 2. Select Review Mode View from the view list in the header area. Note: Depending on your security permissions, you may be able to switch to Document View to modify the requirement documents and requirements. See Modifying Requirement Documents, page 191. 3. To view a snapshot of the requirement document, select the snapshot from the version list in the header area. The window changes to gray to indicate you are viewing a snapshot. Select <Current Version> to view the current requirement document. 4. Optionally select a Filter to display specific requirements. For example, you may want to only view the requirements you own. You can also filter the columns in the details area. See Filtering list window columns, page 24. Note: You cannot apply filters to snapshots. 5. Click Add Note in the Document Notes area to add a review note or comment to the requirement document. See Adding requirement document review notes, page 222 and Adding comments to requirement documents, page 218.
221
Ad d in g r e q u ir e me n t d ocu me n t r e vie w n ot e s
6. Select a requirement and click Add Note in the toolbar to add a review note or comment to the requirement. See Adding requirement review notes, page 223 and Adding comments to requirements, page 209. Note: Indicators, such as locks and flags, are displayed to point out additional information. See About requirement and requirement document indicators, page 188.
Adding requirement document review notes

When you review a requirement document, you can add review notes to provide feedback. For example, add a requirement document review note if a change affects multiple requirements in the document or the structure of the document. Note: You can also add review notes on specific requirements in a requirement document. See Adding requirement review notes, page 223. 1. Open the requirement document in the Specification Document window. Make sure Review Mode View is selected. 2. Click Add Note in the Document Notes area and select Review Note. The Review Note dialog box opens.
3. Select a Review Note By user. This field defaults to the logged in user. 4. The Date defaults to the current date and time. You can enter another date and time. 5. Enter any Notes. It is helpful to provide details about changes needed, questions, or other feedback. 6. Select a Note Type to indicate the purpose of the review note. 7. Optionally attach any files that a user needs to make changes to the requirement document. See Attaching Files, page 54.
222
Ad d in g r e q u ir e me n t r e vie w n ot e s
8. Click OK. The note is added to the requirement document and displayed in the Document Notes area.
Adding requirement review notes

When you review a requirement, you can add review notes to provide feedback. For example, add a requirement review note if a specific requirement needs changes or if you have a question about the requirement. Note: You can also add review notes on a requirement document. See Adding requirement document review notes, page 222. 1. Select the requirement you want to add a review note to in the Specification Document window. Make sure that Review Mode View is selected. 2. Click Add Note and then select Review Note. The Review Note dialog box opens.
223
Ed it in g r e vie w n ot e s
3. Select a Review Note By user. This field defaults to the logged in user. 4. The Date defaults to the current date and time. You can enter another date and time. 5. Enter any Notes. It is helpful to provide details about changes needed, questions, or other feedback. 6. Select a Note Type to indicate the purpose of the review note. 7. Optionally attach any files that a user needs to make changes to the requirement. See Attaching Files, page 54.
8. Click OK. The note is added to the requirement and displayed under the corresponding requirement.
Editing review notes

Depending on your security permissions, you can edit requirement and requirement document review notes to add information or correct mistakes. 1. To edit a requirement review note, double-click the requirement that contains the review note in the Specification Document window. To edit a requirement document review note, select the requirement document on the Requirement Document list window and choose Activities > Edit Requirement Document. The requirement or requirement document opens. 2. If you are editing a requirement, click Edit in the View Requirement dialog box.
224
Vie win g Re q u ir e me n t Docu me n t s
The Edit Requirement dialog box opens. 3. Click the Workflow tab. 4. Right-click the review note you entered and choose Edit Event. 5. Make any changes. 6. Click OK to save the review note changes. 7. Click OK to save the requirementchanges.
Viewing Requirement Documents

You can view read-only requirement document information. You can also send email and perform document activities when viewing requirement documents. 1. Select the requirement document on the Requirements Documents list window or the Specification Document window. 2. Choose Edit > View Requirement Document. The View Requirement Document dialog box opens. 3. The Status field displays the requirement document workflow state and assignment information.
n
A lock is displayed if the requirement document is locked by the requirement or requirement document workflow. Click the lock to view lock information. See Viewing lock information, page 221. A flag is displayed if the requirement document is marked as suspect because a related item changed. Click the flag to view the dependencies. See Investigating suspect dependencies, page 83.
4. Click Open Specification Document to view a hierarchical list of requirements in the requirement document. See Using the Specification Document Window, page 186. 5. Click Send Email to email users about the requirement document. See Emailing from TestTrack, page 73. 6. Click Edit to edit the requirement document. See Editing Requirement Documents, page 225. 7. Click OK to close the View Requirement Document dialog box.
Editing Requirement Documents

You can edit a requirement document to add additional information or make changes based on review comments or changes to related items. The following information applies to editing requirement document information. If you want to edit requirements in a requirement document, open the specification document. See Using the Specification Document Window, page 186. Tip: If you need to update field values for multiple requirement documents, use bulk field changes. This allows you to quickly update multiple records simultaneously. See Updating Multiple Items, page 84.
225
Du p l icat in g r e q u ir e me n t d ocu me n t s
1. Select the requirement document on the Requirement Documents list window or the Specification Document window. 2. Choose Edit > Edit Requirement Document. The Edit Requirement Document dialog box opens. Note: If another user is editing the requirement document, a read-only icon is displayed next to the OK button. When the user closes the requirement document, it is updated and becomes available for editing. 3. Make any changes.
n
A lock is displayed next to the Status field if the requirement document is locked. Depending on your security permissions, you may not be able to edit locked requirement documents. Click the lock to view more information. See Viewing lock information, page 221. A flag is displayed next to the Status field if the requirement document is marked as suspect because a related item changed. Click the flag to view the dependencies. See Investigating suspect dependencies, page 83.
4. Click Open Specification Document to open the Specification Document window and work with requirements in the requirement document. See Using the Specification Document Window, page 186. 5. Click Send Email to email a user or customer. See Emailing from TestTrack, page 73. Click the Email tab to view, reply to, or delete tracked email. See Viewing tracked email, page 75 and Replying to tracked email, page 76. 6. Click OK to save the changes. Note: If the changes impact linked or related items, you may want to mark the items as suspect. This adds a flag to the items to indicate they should be reviewed. See Marking Items as Suspect, page 82.
Duplicating requirement documents

If you add requirement documents with the same basic information, you can save time by duplicating and editing an existing document. When you duplicate a requirement document, you can copy all requirements from the original document to the new document, share requirements between the documents, or create the new document without any requirements. 1. Select the requirement document on the Requirement Documents list window. 2. Choose Edit > Duplicate Requirement Document. The Duplicate Requirement Document wizard opens.
226
Du p l icat in g r e q u ir e me n t d ocu me n t s
3. Select any Requirement Document Options.

n
Select Link duplicated document with original to link the new requirement document with the original document. Select a Link definition and enter a Link comment. The Link definitions list includes all requirement document link definitions. The link comment is displayed on the requirement document Links tab and in the link diagram. Select Identify original document in system comment to add a system comment to the Workflow tab on the new requirement document that indicates the original document number and name. Select the information to copy from the original requirement document. File attachments copies file attachments from the Files tab. SCC attachments copies source control attachments from the Files tab. Email messages copies emails from the Email tab. Folder information copies the new document to the same folder as the original document. Requirement documents can only be copied to folders you have access to.
4. Click Next. 5. Select Content Options to indicate how requirements should be copied to the new requirement document.
n
Copy requirements and add copies to the new document copies all requirements from the original requirement document to the new document. The requirement organization matches in the original and new documents. Share requirements between documents adds requirements to the new requirement document and create a share between the requirements. If a shared requirement is modified, the changes are made in all documents the requirement is included in. Do not include any requirements in the new document creates the new requirement document without requirements.
6. If you are not copying requirements to the new document, skip to step 8. If you are copying requirements to the new document, click Next. 7. Select any Requirement Options.
227
Assign in g r e q u ir e me n t d ocu me n t n u mb e r s
Select Link duplicated requirement with original to link the new requirement with the original requirement. Select a Link definition and enter a Link comment. The Link definitions list includes all peer link definitions for requirements. The link comment is displayed on the requirement Traceability tab and in the link diagram. Select Identify original requirement in system comment to add a system comment to the Workflow tab on the new requirement that indicates the original requirement number and summary. Select the information to copy from the original requirement. File attachments copies file attachments from the Files tab. SCC attachments copies source control attachments from the Files tab. Email messages copies emails from the Email tab. Folder information copies the new requirements to the same folder as the original requirements. Requirements can only be copied to folders you have access to.
8. Click Finish. The requirement document is duplicated.
Assigning requirement document numbers

After you review deferred requirement documents, you can assign numbers to them. 1. Select the unnumbered requirement document on the Requirement Documents list window. 2. Choose Activities > Assign Requirement Document Numbers. The requirement document is assigned the next available document number.
Renumbering requirement documents

You can renumber requirement documents at any time. For example, deleting requirement documents may leave gaps in document numbers and you may want to renumber the documents. 1. Select the requirement document you want to renumber. 2. Choose Activities > Renumber Requirement Documents. The Renumber Requirement Documents dialog box opens. The starting number is set to the next number.
3. Enter a new document number and click OK. The Renumber Requirements Documents dialog box closes and the requirement document is renumbered.
n
If the renumbered requirement document number is higher than the next available document number, the next available document number is set to one higher than the renumbered document.
228
De l e t in g r e q u ir e me n t d ocu me n t s
If you renumber the entire requirement document list, the next available requirement document number must be set to one greater than the highest document number.
Deleting requirement documents

Deleting requirement documents also deletes any historical snapshots created from the documents. 1. Select a requirement document on the Requirement Documents list window. You can select more than one requirement document to delete. 2. Choose Edit > Delete Requirement Document. You are prompted to delete the requirements included in the selected requirement documents. Requirements cannot be deleted if:
n n n
They are locked for editing by another user They are included in current versions of other requirement documents (shared) Historical versions of the requirements are included in snapshots created from other requirement documents
3. Click Delete all if you want to delete the selected requirement document, requirements included in the document, and snapshots or click Delete documents if you want to only delete the selected document and snapshots. The requirement document is deleted. Note: If any of the included requirements cannot be deleted, a dialog box opens and displays the requirement tag number and reason it cannot be deleted. Click OK to close the dialog box.
Managing Requirement and Requirement Document Email

If email tracking is enabled, you can work with email sent from requirements and requirement documents. You can view, reply to, and delete tracked email. 1. Click the Email tab when you are editing or viewing a requirement or requirement document.
2. Select an email and click View to view it. Viewing tracked email, page 75. 3. Select an email and click Reply To to reply to it. See Replying to tracked email, page 76. 4. Select an email and click Delete to delete it. See Deleting tracked email, page 76. You can only delete email when you are editing a requirement or document. 5. Click OK to save the changes.
229
M an agin g Re q u ir e me n t an d Re q u ir e me n t Docu me n t Fol d e r s
Managing Requirement and Requirement Document Folders

You can add requirements and requirement documents to folders to group them with other items. For example, you may use Current Release, Next Release, and Future Release folders to group software functional requirements based on the expected release the requirement is addressed in. See Organizing Data with Folders, page 56. 1. Click the Folders tab when you are viewing or editing a requirement or requirement document. Folder paths are displayed if the requirement or requirement document is included in folders.
2. Select a folder and click Open Folder to open it. 3. Click Add to Folder to add the requirement or requirement document to a folder. See Adding items to folders, page 66. 4. Select a folder and click Move to Folder to move the requirement or requirement document to a folder. See Moving items to folders, page 66. 5. Select a folder and click Remove from Folder to remove the requirement or requirement document from the folder. See Removing items from folders, page 69. 6. Click OK to save the changes.
Creating Requirement Document Snapshots

A snapshot is a version of a requirement document captured at a specific point in time. Snapshots are used for comparing requirement document versions and viewing differences between them. Snapshots are typically created in conjunction with project milestones. For example, you may create a snapshot when the first draft of a requirement document is complete. If you need to refer to the original requirement document version later, you can view the differences between the snapshot and a newer version to see what changed. When you create a snapshot, current versions of all requirements included in the requirement document are saved in the snapshot. If a requirement in a snapshot changes, the old requirement is versioned and archived. See Viewing Historical Requirement Versions, page 236 for more information about requirement versions. After you create a snapshot, you can compare it to the current requirement document version or another snapshot to view the differences. See Viewing all requirement document differences, page 234. Tip: You can configure triggers and escalation rules to automatically create snapshots. See Create snapshot action, page 457.
230
Vie win g Re q u ir e me n t Docu me n t S n ap sh ot s
1. Select a requirement document on the Requirement Documents list window or the Specification Document window. 2. Choose Activities >Create Snapshot. The Create Snapshot dialog box opens.
3. Enter a snapshot Label to summarize the purpose of the snapshot or project milestone it corresponds to. 4. Enter a Comment to explain why you are creating the snapshot. 5. Click Create Snapshot. The snapshot is created. Note: You can view snapshots from the Snapshots tab in the Edit Requirement Document or View Requirement Document dialog boxes. See Viewing Requirement Document Snapshots, page 231. Snapshots are read-only and cannot be edited or deleted. They are deleted when you delete a requirement document.
Viewing Requirement Document Snapshots

You can view requirement document snapshots and compare a snapshot to the current requirement document version or another snapshot to view differences between them. Snapshots are read-only and you can only perform the following actions on them:
n
Entering requirement and requirement document review-based workflow events, such as Review Note and Comment. Requirement events are only available in the Specification Document window. Viewing, extracting, and opening file attachments Getting, viewing local copies, and viewing the history of source control file attachments Adding, editing, and viewing links Viewing, sending, and replying to email Printing snapshots
n n n n n
1. Click the Snapshots tab when you are editing or viewing a requirement document. The requirement document snapshots are displayed.
231
Vie win g Re q u ir e me n t Docu me n t S n ap sh ot s
2. Select a snapshot and click View to view the snapshot. The snapshot opens in a new View Requirement Document dialog box. All information in the requirement document at the time the snapshot was created is displayed. Information on the following tabs is limited for the snapshot:
n
Overview and Workflow tabsDisplays activities performed on the snapshot and previous snapshots only Folders tabNot displayed. Only the current requirement document version can be in a folder. History tabDisplays the requirement document history from the date the document was created to the date the snapshot was created only Note: Click Diff With Current to view the differences between the snapshot and the current requirement document version. Click View Snapshot Details to view detailed information about the snapshot. See Viewing Requirement Document Differences, page 233 and Viewing snapshot details, page 233.
n n
3. Select a snapshot and click Open Specification Document to view the snapshot in the Specification Document window. See Using the Specification Document Window, page 186 4. Select a snapshot and click View Snapshot Details to view detailed information about the snapshot. See Viewing snapshot details, page 233. 5. Select a snapshot and click View Differences to view changes to the requirement document and its hierarchy between the snapshot and the current requirement document version. You can also select two snapshots to compare them. See Viewing Requirement Document Differences, page 233.
232
Vie win g Re q u ir e me n t Docu me n t Diffe r e n ce s
6. Click View All Differences to view detailed requirement differences between the snapshot and the current requirement document version. You can also select two snapshots to compare them. See Viewing all requirement document differences, page 234. 7. Click Create Snapshot to create a requirement document snapshot. See Creating Requirement Document Snapshots, page 230. 8. Click OK to close the Edit Requirement Document or View Requirement Document dialog box.
Viewing snapshot details

You can view snapshot details to see the snapshot number and label, who created a snapshot, when it was created, and comments entered when the snapshot was created. 1. Click the Snapshots tab when you are editing or viewing a requirement document. 2. Select a snapshot and click View Snapshot Details. The View Snapshot Details dialog box opens. Note: You can also click Snapshot Details on the View Requirement Document dialog box when you are viewing a snapshot.
3. Click OKwhen you are finished.
Viewing Requirement Document Differences

You can compare a requirement document snapshot to another snapshot or the current document to view the differences between versions. This can help you determine requirements added, modified, moved, or removed in a requirement document during a specific time period. 1. Click the Snapshots tab when you are viewing or editing a requirement document. 2. Select a snapshot to compare it to the current requirement document version or Ctrl+click two snapshots to compare. 3. Click View Differences. The Document Differences window opens. The requirements included in each version are displayed. The Differences column displays the reason the requirements are different.
233
Vie win g al l r e q u ir e me n t d ocu me n t d iffe r e n ce s
4. Optionally expand the Document View Options area to select display options.
n
Select a View As option. Document Outline displays requirements in the requirement document hierarchy. Requirement List displays requirements as a list, excluding the requirement document hierarchy. Select or clear any Show options to limit the requirements displayed.
5. Click Expand All or Collapse All to expand or collapse the requirement hierarchy. 6. Select a requirement and click Find Match to locate the requirement in the other snapshot or current version. This can help you find requirements moved in the document between snapshots. 7. Right-click a requirement and choose View or Edit to view or edit the requirement. You cannot edit locked requirements or historical requirement versions. 8. Select a requirement and click View Differences to view the differences between the requirement versions. See Viewing Requirement Differences, page 238. You can also select the requirement document to view the requirement document differences. 9. Click View All Differences to display detailed content differences between the requirement document versions. See Viewing all requirement document differences, page 234. Note: You can also compare a snapshot to the current requirement document version when you are viewing a snapshot. Click Diff With Current in the View Requirement Document dialog box.
Viewing all requirement document differences

You can view detailed differences between requirement document snapshots. All content changes between versions are displayed for the requirement document and requirements included in the document. File and source code attachments are not included.
234
Vie win g al l r e q u ir e me n t d ocu me n t d iffe r e n ce s
Note: You can also compare snapshots side-by-side to view a summary of the differences. See Viewing Requirement Document Differences, page 233. 1. Click the Snapshots tab when you are viewing or editing a requirement document. 2. Select a snapshot to compare to the current requirement document version or Ctrl+click two snapshots to compare. 3. Click View All Differences. The differences report opens. Content added to the requirement document is displayed in bold green text and removed content is displayed in red strikethrough text. Inline image changes are displayed after the requirement differences. Note: You can change the added and removed text color and format in user options. See Setting differences display options, page 349.
4. Click a requirement or requirement document version link to view the requirement or document.
235
Vie win g Hist or ical Re q u ir e me n t Ve r sion s
5. Click Print to print the differences or click Preview to preview the differences before printing. 6. Click Close the differences report.
Viewing Historical Requirement Versions

A requirement is automatically versioned after a requirement document snapshot is created and a requirement is modified. For example, a requirement document named File Export includes a requirement named Image File Formats. When the first draft of the requirement document is complete, you create a snapshot named Before Initial Review that includes the current version of the Image File Formats requirement. After the review cycle is complete, you modify the Image File Formats requirement. When you save the changes, a version of the old requirement, which is identified in the snapshot as version 1, is created. You can view historical requirement versions, compare a historical version to the current version or another historical version, or roll back the current requirement version to a historical version. Requirement versions are read-only and you can only perform the following actions on them:
n n n n n n n
Enter requirement review-based activities, such as Review Note and Comment Viewing, extracting, and opening file attachments Getting, viewing local copies, and viewing the history of source control file attachments Adding, editing, and viewing links Viewing, sending, and replying to email Generating test cases Printing requirements
1. Click the Versions tab when you are editing or viewing a requirement. The historical requirement versions are displayed.
2. Select a version and click View to view it. The requirement version opens in a new View Requirement dialog box. All information in the requirement when the version was created is displayed. Information on the following tabs is limited for the version:
n
Overview and Workflow tabsDisplays activities performed on the historical version and previous versions only Requirement Relationships tab on the Traceability tabDisplays requirement relationships for the historical version only Folders tabNot displayed. Only the current requirement version can be in a folder.
236
Rol l in g b ack r e q u ir e me n t s
History tabDisplays requirement history from the date the requirement was created to the date the version was created only Note: Click Diff With Current to compare the historical requirement version with the current version. See Viewing Requirement Differences, page 238.
3. Select a version and click View Differences to compare it with the current version. You can also select two versions to compare them. See Viewing Requirement Differences, page 238. 4. Select a version and click Make Current to roll back the current version to the historical version. See Rolling back requirements, page 237.
Rolling back requirements

Roll back a requirement if you need to revert to a previous version. For example, you may need to roll back a requirement if you make changes to it and then find out the stakeholder does not want the changes. 1. Click the Versions tab when you are editing a requirement. 2. Select a requirement and click Make Current. You are prompted to confirm the rollback. 3. Click Make Current. The following field values in the Edit Requirement dialog box are replaced with values from the historical version.
n n n n
Summary Date Entered Entered By Priority
237
Vie win g Re q u ir e me n t Diffe r e n ce s
n n
Description All fields on the requirement Detail tab
4. Make any changes. 5. Click OK to save the changes.
Viewing Requirement Differences

You can compare a historical requirement version to another historical version or the current version to view the content differences between versions. File and source code attachments are not included. Note: You can also view differences between requirement document snapshots. See Viewing all requirement document differences, page 234. 1. Click the Versions tab when you are viewing or editing a requirement. 2. Select a version to compare to the current requirement version or Ctrl+click two historical versions to compare. 3. Click View Differences. The differences report opens. Added content is displayed in bold green text and removed content is displayed in red strikethrough text. Inline image changes are displayed after the requirement differences. Note: You can change the added and removed text color and format in user options. See Setting differences display options, page 349.
4. Click a requirement version link to view the requirement. 5. Click Print to print the differences or click Preview to preview the differences before printing.
238
M an agin g Re q u ir e me n t Docu me n t Lin ks
6. Click Close the differences report. Note: You can also compare the current requirement version when you are viewing a historical version. Click Diff With Current on the View Requirement dialog box.
Managing Requirement Document Links

You can link requirement documents to other items in the same project. Linking helps you establish relationships between items and manage changes to related items when requirement documents change. You can link items in a parent/child relationship or a peer relationship. Following are a few examples that illustrate the different uses for linking requirement documents:
n
The requirements for an upcoming release are grouped in separate requirement documents based on functional area. You can link all the requirement documents in a peer relationship to indicate they are all part of the same release and make it easier for users to access the related documents. A customer submits a feature request, which is added to the project as an issue. The product manager decides to address the feature request in the next release. She creates a requirement document that includes requirements to fulfill feature request and links the issue to the requirement document in a peer relationship to track the document and its source together. A stakeholder approves a requirement document that includes business and functional requirements for an upcoming release. The development team lead is notified when the requirement document is approved. As the development team creates technical specification documents based on the business and functional requirement document, the team lead links the documents in a parent/child relationship to make it clearer where the technical specifications came from. This also makes it easier for the development team to make sure specifications exist for all functional requirements.
1. Click the Links tab when you are adding or editing a requirement document.
2. Click Add Link to create a link. See Adding links, page 77. 3. Select a link and click View Link to view it. See Viewing links, page 80. 4. Select a link and click Edit Link to change it. See Editing links, page 81.
239
M an agin g Re q u ir e me n t Lin ks
5. Select a link and click Diagram Links to generate a link diagram. See Diagramming links, page 79. 6. Select a link, click an item in the Link Details area, and click View Item to view the linked item. 7. Select a link, select an item in the Link Details area, and click Edit Item to edit the linked item. 8. Select a link, select an item marked as suspect in the Link Details area, and click Investigate to view the suspect dependencies. See Investigating suspect dependencies, page 83. 9. Select a link, select an item marked as suspect in the Link Details area, and click Clear Suspect to clear the suspect. See Clearing suspect items, page 84. 10. Select a link, select an item in the Link Details area, and click Mark Suspect to mark the item as suspect. See Marking Items as Suspect, page 82. 11. Select a link and click Delete Link to delete it. See Deleting links, page 81. 12. Click Add or OK to save the changes.
Managing Requirement Links

You can link requirements to other items in the same project. Linking helps you establish relationships between items and manage changes to related items when requirements change. You can link items in a parent/child relationship or a peer relationship. Following are a few examples that illustrate the different uses for linking requirements:
n
The QA team lead generates six test cases from a requirement to validate the requirement is implemented and tested. She links the test cases to the requirement in a parent/child relationship, then assigns the test cases to a tester to write the steps. The tester can view the requirement to make sure the correct steps are included in the test case. A customer submits a feature request, which is added to the project as an issue. The product manager decides to address the feature request in the next release and creates a requirement based on it. She links the issue to the requirement in a peer relationship to track the requirement and its source together. A stakeholder approves functional requirements for a portion of an upcoming development project. The development team lead is notified when the requirements are approved and creates technical requirements, which are added to a separate requirement document. He then links the functional requirements to the technical requirements in a peer relationship and assigns the technical requirements to a software architect who writes them. The architect can view the functional requirements to make sure the related technical requirements are complete and accurate.
1. Click the Traceability tab and then click the Links tab when you are adding or editing a requirement.
240
Ge n e r at in g Te st Case s fr om Re q u ir e me n t s
2. Click Add Link to create a link. See Adding links, page 77. 3. Select a link and click View Link to view it. See Viewing links, page 80. 4. Select a link and click Edit Link to change it. See Editing links, page 81. 5. Select a link and click Diagram Links to generate a link diagram. See Diagramming links, page 79. 6. Select a link, click an item in the Link Details area, and click View Item to view the linked item. 7. Select a link, select an item in the Link Details area, and click Edit Item to edit the linked item. 8. Select a link, select an item marked as suspect in the Link Details area, and click Investigate to view the suspect dependencies. See Investigating suspect dependencies, page 83. 9. Select a link, select an item marked as suspect in the Link Details area, and click Clear Suspect to clear the suspect. See Clearing suspect items, page 84. 10. Select a link, select an item in the Link Details area, and click Mark Suspect to mark the item as suspect. See Marking Items as Suspect, page 82. 11. Select a link and click Delete Link to delete it. See Deleting links, page 81. 12. Click Add or OK to save the changes.
Generating Test Cases from Requirements

If you use TestTrack TCM, you can generate test cases from approved requirements. Testers can use these test cases to perform tests that validate each requirement is implemented correctly. Test cases generated from requirements are populated with the following information by default:
n
SummaryThe requirement summary is copied to the test case Summary field, prepended with the requirement number. File attachmentsRequirement file attachments are copied to the Attachments tab on the test case Files tab. Requirement source file attachments are copied to the Source Code tab on the test case Files tab.
241
Ge n e r at in g Te st Case s fr om Re q u ir e me n t s
Detail tab fieldsField values from the requirement Detail tab are copied to the test case Detail tab if the requirement and test case fields have matching names and field types.
Note: Depending on the item mapping rules configured for the project, additional information may be copied from the requirement. See Configuring Item Mapping Rules, page 460. When you create a test case from a requirement, you can create a link between the requirement and the test case. This is recommended because it can help you verify that each requirement has adequate test coverage, view relationships between related requirement and test cases, and analyze the impact of requirement changes on related test cases. Note: It may take several minutes to generate test cases from multiple requirements. 1. Select a requirement on the Requirements list window or in the Specification Document window. The requirement must be in a state that allows test case generation. For example, test cases can only be generated from requirements in the Approved or Implemented states in the default requirements workflow. 2. Choose Activities > Generate Test Cases. The Generate Test Cases dialog box opens. Note: Depending on your security permissions, you may be prompted to generate test cases without selecting folder or link options. Click Generate to generate the test cases.
3. Select a folder option. You can add test cases to folders to group them with related items. For example, you may want to add test cases to folders based on functional area or type. You must create the folders before generating test cases. See Adding folders, page 61.
n n
Select Do not add a folder if you do not want to add the test cases to a folder. Select Add to the selected folder to add the test cases to a folder. Click Browse. Select a folder and click OK.
4. Select a link option.
242
Cr e at in g Issu e s fr om Re q u ir e me n t s
n n
Select Do not link if you do not want to link the test cases to the requirement. Select Use the following link definition to link the test cases to the requirement. Select a Link definition and enter a Link comment. The Link definitions list includes all definitions that allow requirements and test cases. The link comment is displayed on the Links tab on the requirement Traceability tab, the test case Links tab, and the link diagram.
5. Click Generate. The test cases are created. To work with test cases, choose View > Test Cases to open the Test Cases list window. See Viewing Test Cases, page 319. Note: You can view linked requirements and test cases on the Links tab on the Traceability tab in the View Requirement dialog box or the Links tab in the View Test Case dialog box. You can also use the traceability matrix to view relationships between items. See Using the Traceability Matrix, page 246.
Creating Issues from Requirements

If you use TestTrack Pro, you can create issues from requirements. The requirement information is copied to the issue so users can review the requirement details when working on the issue. 1. Click Create Issue in the Edit Requirement dialog box. The Add Issue dialog box opens. It is populated with the following requirement information by default:
n n n n
Summary fieldIncludes the requirement number and summary. Description fieldIncludes the requirement summary. Files mini tab on the Detail tabIncludes requirement file attachments. Source Code tabIncludes requirement source code attachments. Note: Depending on the item mapping rules configured for the project, additional information may be copied from the requirement. See Configuring Item Mapping Rules, page 460.
2. Make any changes. 3. Click Add when you finish entering the issue information.
243
Vie win g Re q u ir e me n t Re l at ion sh ip s
You may be prompted to link the issue with the related requirement. Click Add Link if you want to create a link or click Do Not Link if you do not want to create a link. See Linking Items, page 77. The issue is saved and added to the project.
Viewing Requirement Relationships

Requirements in a requirement document have a hierarchical relationship to other requirements in the document. You can view the parent and child requirements related to a specific requirement across all requirement documents. 1. Click the Traceability tab and then click the Requirement Relationships tab when you viewing or editing a requirement.
2. Select a requirement and click View Item to view it. See Viewing Requirements, page 197. 3. Select a requirement and click Edit Item to edit it. See Editing Requirements, page 198. 4. Select a requirement marked as suspect and click Investigate to view the dependencies to related items causing the requirement to be suspect. See Investigating suspect dependencies, page 83. 5. Click OK to close the Edit Requirement or View Requirement dialog box.
Performing Impact Analysis

You can perform an impact analysis to view items related to requirements, which can help you understand the impact of a requirement change before you make it. 1. Click the Traceability tab and click Impact Analysis when you are viewing or editing a requirement. The forward impact is displayed, which shows items directly and indirectly impacted if the requirement changes.
244
Ab ou t ch an ge imp act an al ysis
Tip: Arrows in the Relation column can help you determine how items are related. A solid arrow indicates the items are linked. Linked items are only displayed if the link definition allows dependent items to be marked as suspect. A dashed arrow indicates the items are related in a requirement document. 2. Select Backward Impact to display how changes to related items may affect the requirement. 3. Select an item and click View Item to view it. 4. Select an item and click Edit Item to edit it. 5. Click OK to close the Edit Requirement or View Requirement dialog box. Tip: If you determine that changes impact items related to the requirement, you may want to mark the items as suspect. This adds a flag to the items to indicate they should be reviewed. See Marking Items as Suspect, page 82.
About change impact analysis

Before you make changes to a requirement, you may want to know how the changes impact related items. You can perform an impact analysis to view the related items, assess the risk of making changes, and identify the items that need to be reviewed based on the changes. See Performing Impact Analysis, page 244. You can perform forward and backward impact analysis.
n
Forward impact analysis identifies downstream dependencies, which are items that may be affected if the requirement changes. Backward impact analysis identifies upstream dependencies, which are how changes to related items may affect a requirement.
Items affected directly and indirectly are displayed when you perform an impact analysis. The following items are displayed depending on the type of impact analysis you perform:
245
U sin g t h e Tr ace ab il it y M at r ix
Impact analysis Forward impact
Impact type Displays the following items: Direct

n
Child requirements one level down in the requirement document Items with peer or child links to the requirement All child requirements of all directly impacted requirements Items with peer or child links to all directly impacted items Parent requirements one level up in the requirement document Items with parent or peer links to the requirement All parent requirements of all directly impacted requirements All items with peer or parent links to all directly impacted items
Indirect
n n
Backward impact
Direct
Indirect
n n
Tip: There are also ways to perform impact analysis for multiple requirements. You can use the traceability matrix to dynamically explore all the relationships in a project and see which items are related and how they are related. See Using the Traceability Matrix, page 246. You can also use the requirement document impact analysis detail report to see which requirements have downstream dependencies in a table format or the requirement forward traceability report to see a hierarchical outline of requirements and dependent items. See Traceability reports, page 121.
Using the Traceability Matrix

You can use the traceability matrix to view the relationships and links between items in a TestTrack project. See About the traceability matrix, page 247. 1. Choose Activities >Traceability Matrix. The Traceability Matrix dialog box opens. 2. Select the Row/Column Settings.
n
Select the item types to be displayed in the rows from the Rows Contain list. Optionally select a rows filter for items to pass if you want to view specific items. Select the item types to be displayed in the columns from the Columns Contain list. The items with row dependencies filter, which only displays linked or related items, is automatically selected as the columns filter. Optionally select a columns filter for items to pass if you want to view specific items. ClickCreate Filter to create a new filter for items in the rows or columns. See Adding Filters, page 97.
3. Click Update Matrix if you make any changes to the row or column settings. 4. Click the Links, Relationships, and Rows/Columns buttons to specify what is displayed in the matrix.
246
Ab ou t t h e t r ace ab il it y mat r ix
5. To manage a link between two items, right-click in the cell that contains a link and select Manage Links. See Linking Items, page 77. 6. Click the Print Preview button in the matrix toolbar to preview the matrix. 7. Click the Print button in the matrix toolbar to print the matrix. 8. Click the Export button in the matrix toolbar to export the matrix to a Microsoft Excel file. See Exporting the traceability matrix to Microsoft Excel, page 248. Tip: You can also use the matrix to add a link between two items, investigate suspect dependencies, and clear suspect items.
About the traceability matrix

The traceability matrix allows you to perform coverage analysis by viewing the relationships between related items. For example, you may want to ensure that at least one test case has been generated for each approved requirement in a project. You can use the traceability matrix to compare requirements against test cases to see which requirements have test cases linked to them.
The traceability matrix displays items in rows and columns for comparison. Each item is listed by its item type tag and number, and the number in parentheses indicates the number of links or relationships. Relationships and links between two items are indicated by icons in the cells.
Traceability matrix icons

The following icons are used in the traceability matrix. The arrows show the direction of the link or relationship between items.
247
Exp or t in g t h e t r ace ab il it y mat r ix t o M icr osoft Exce l
Icon
Description Parent/child linkOne is the parent or child to the other item. Peer linkThe items are peers. Parent/child relationshipThe arrow points to the parent item. Only requirements, test cases, and test runs display relationships in the traceability matrix. Peer relationshipThe requirements share two relationships that point in opposite directions. This icon is unique to requirements that are used in multiple requirement documents but with different relationships in each document. Suspect itemOne of the items has been marked as suspect.
Note: If there is more than one common link between row and column items, the total link count is also displayed in the cell.
Traceability matrix toolbar

The traceability matrix toolbar provides access to commands that allow you to show or hide content in the matrix. You can use the toolbar buttons to help you find the information you want more quickly. For example, you can click the Rows/Columns buttons to remove rows and columns that do not contain a link or relationship, which reduces the size of the matrix and the amount of information you have to sort through. Tip: Mouse over the toolbar buttons to view what each button shows and hides.
Exporting the traceability matrix to Microsoft Excel

You can export the traceability matrix to a Microsoft Excel file. For example, you may want to share information with users who do not have access to TestTrack RM or add information you already manage in Excel to the matrix. 1. Update the traceability matrix to display the links and relationships you want to export. See Using the Traceability Matrix, page 246. 2. Choose File >Export > Microsoft Excel Export. The Export Traceability Matrix dialog box opens.
248
Imp or t in g Re q u ir e me n t Docu me n t s fr om M icr osoft Wor d
3. Select a format for the matrix in the Excel file.

n n
Matrix displays one item type in rows and the other item type in columns. Two Column displays one item type in the left column and all linked items in the right column.
4. Select Open the file in the associated viewer after creation to open the file after it is exported. 5. Click Export. The Save As dialog box opens. 6. Select the file location, enter a file name, and click Save. The traceability matrix is exported. The file opens if you selected the option to open it when the export is complete.
Importing Requirement Documents from Microsoft Word

You can import requirement documents from Microsoft Word into TestTrack. Before importing a requirement document, you may want to create all your requirement types in TestTrack. This helps streamline the process of mapping outlined or styled paragraphs in the Microsoft Word document to TestTrack requirement types. See Adding requirement types, page 382. 1. Choose File >Import >Microsoft Word Import. The Microsoft Word Import Wizard starts.
249
2. Enter the File to Import path or click Browse to locate the file. 3. Optionally select an Import Template. Click Browse to locate the template. Import templates include the settings used during a previous import of a requirement document and are saved with an itm extension. 4. Click Next. 5. If you are using an import template, skip to step 11. If you are you are not using an import template, continue to select an interpretation method. 6. Select an Interpretation Method.
Select Styles if the Word document uses styles. You will be able to map the styles to requirement types in TestTrack.
250
Select Outline if the Word document uses outlines. The wizard will map individual paragraphs in the document as individual requirement summaries, using list levels.
n
Select Treat bulleted text as a separate requirement to create a new requirement for each bulleted item in the document. If you do not select this option, bulleted lists will be part of the requirement's description. Select a Default requirement type for each new requirement in the document.
7. Click Next. 8. Set the Style Mappings if you selected Styles as the interpretation method.
n n
Select Starts New Requirement for each Word style that starts a new requirement. Select a Requirement Type to map that style to. You must map at least one style to a requirement type. Click Next.
9. Select a section break range.

n n
Select All sections to import all sections from the Word document. Select Selected sections and set the starting and ending sections to import only the selected sections.
10. Click Next. 11. Preview the requirement document and make any changes.
251
n n n n
Select a requirement in the Requirements list to preview it. Click the Delete button to remove the selected requirement from the document. Click the arrow buttons to rearrange the order of the requirements. Select a requirement type from the Change requirement type list to change a requirement's type. Click Save Import Template to save the import settings as a template. The import template will include the interpretation method and any additional options set during this import, which can be helpful if you use the same structure for all your existing requirement documents. For example, if your organization uses the same Word template for all requirement documents, you may want to save the style mappings you have assigned as an import template to ensure consistency among imported requirements.
12. Click Next. 13. Select a Requirements Destination.
252
Exp or t in g Re q u ir e me n t Docu me n t s t o M icr osoft Wor d an d Ad ob e P DF For mat
Select Create a new requirement document to import the requirements into a new requirement document. Name the requirement document and optionally select a folder to add the document to. Select Add to an existing requirement document to import the requirements into an existing requirement document. Click Browse to locate the existing requirement document in the project.
14. Click Finish. The Importing Requirements dialog box opens and displays the status of the import. When the import process is complete, the Microsoft Word Import Warnings and Errors dialog displays the status of the import. You can save the import log and use it to troubleshoot any errors encountered during the import. If the import completed successfully, the requirement document and its requirements are added to the TestTrack project.
Exporting Requirement Documents to Microsoft Word and Adobe PDF Format

You can export requirement documents to Microsoft Word to share requirements with stakeholders who do not have access to TestTrack RM. You can also save the exported file as an Adobe PDF file. Tip: You may want to create a Specification Document View for exporting requirement documents. This helps match the appearance of exported Microsoft Word documents to the view in TestTrack. See Creating User-Defined Views, page 28. 1. Open the requirement document you want to export in the Specification Document Window. The summary, description, and tag fields are always exported if they are displayed. The summary is used as the document title. To export other fields, insert a column in the Specification Document window, right-click the new column, and select the field to display. Note: To export a snapshot, the snapshot must be displayed. 2. Choose File >Export > Microsoft Word Export. The Microsoft Word Export dialog box opens. 3. Click Browse to locate the Microsoft Word template you want to use. The following templates are installed in the C:\Program Files\Seapine\TestTrack\templates directory by default.
n
BasicIndented.docMulti-page template that indents requirements to display up to nine levels of hierarchy. Includes a cover page, table of contents, and footer with page numbering. BasicIndentedColor.docMulti-page template that indents requirements to display up to nine levels of hierarchy and uses blue for the requirement headings. Includes a cover page, table of contents, and footer with page numbering. BasicLeftAligned.docMulti-page template that left-aligns all exported content. Includes a cover page, table of contents, and footer with page numbering. Plain.docOne-page template that left aligns all exported content. Matches the views displayed in the Specification Document Window.
253
Exp or t in g Re q u ir e me n t Docu me n t s t o M icr osoft Wor d an d Ad ob e P DF For mat
Tip: The requirements Word styles in the installed templates are mapped to hierarchy levels in the Specification Document window. You can make changes to one of the installed templates and save the file as a new document to easily create a custom template. If you create a template, it must include a bookmark named MICROSOFT_WORD_EXPORT_TEST_TRACK_RM. This bookmark is used during the export to populate the template with requirements from TestTrack RM. 4. Click Export. The Save As dialog box opens. 5. Select the file location, enter a file name, and click Save. Note: To export the requirement document to PDF format, enter a file name with the .pdf extension. The requirement document is exported.
254
Using TestTrack TCM

This guide includes information for working with the test cases and test runs you track and manage with TestTrack TCM.
Adding Test Cases

You can add a test case when you need to define the conditions, steps, and expected results for testing a product component. Each test case should focus on one component. Your testing may require more than one test case per component. A test case is a set of conditions, actions, expected results, and other criteria used to determine if a product component is working correctly and meets its specified requirements. Note: The information you enter may be different depending on your companys use of TestTrack TCM. 1. Choose Create > Test Case. The Add Test Case dialog box opens with the Detail tab selected.
2. Enter a test case Summary. You can enter up to 255 characters. 3. Status displays the test case workflow state and assignment information. 4. Select a test case Type. 5. Select Automated Test if the test case will be performed using an automated script. See Managing Automated Tests, page 302.
255
En t e r in g t e st case d e t ail s
6. Enter details about the test case on the Detail tab. See Entering test case details, page 256. 7. Click the Steps tab and enter the steps to perform the test and the expected results. See Entering test case steps, page 257. 8. Click the Variants tab and select the test variants to include or exclude when test runs are generated for the test case. See Managing Test Variants, page 266. 9. Click the Files tab to manage automated scripts, source code, or other test case file attachments. See Attaching Files, page 54. 10. Click Add when you finish entering the test case information. The test case is saved and added to the project.
Entering test case details

Test case details provide general information such as the test description, the scope, the conditions that must be met before performing the test, and the overall expected test results. It may be helpful to enter test case details during the test planning process. For example, the QA team lead may enter the test case details and then assign the test case to a team member to enter additional information. Note: Test case details should not include step-by-step instructions for performing a manual test. Enter steps and expected results on the Steps tab. See Entering test case steps, page 257. 1. Click the Detail tab when you are adding or editing a test case.
2. Enter the Estimated run time required to perform the test case. 3. Enter any Custom Fields information. The information you enter may be different depending on your organization's use of TestTrack TCM.
256
En t e r in g t e st case st e p s
Test case custom field values are only copied to test runs if they are mapped to test run fields. See Configuring Item Mapping Rules, page 460.
n n
Description describes the purpose of the test case to differentiate it from similar test cases. Scope describes the components the test case applies to. For example, you may want to enter the operating systems the test case applies to. Pre-Conditions describe any setup or other requirements that must be in place before the test is performed. For example, you may want to enter information about setting up the test environment. Expected Results describe the expected outcome after performing the test. Tip: You can use test variant field codes in text fields. When you generate test runs, field codes are replaced with the variant values. For example, if you have an Operating System variant with a %Z_OSVARIANT% field code and the Windows value is used to generate test runs, the field code is replaced with Windows in the test run. See Custom field codes, page 550.
4. Click Add or Apply to save the changes, or click another tab to enter additional test case information.
Entering test case steps

Test case steps define the actions that the tester performs in the application in sequential order. Expected results describe the outcome of performing the corresponding step. Testers use the expected results to determine if a test passes or fails. You can also add comments and attachments to provide additional information about a step or result. When test runs are generated for a test case, the steps, expected results, comments, and attachments are automatically included in the test runs so testers can perform each step and enter information if the expected results are not observed. It is important to provide complete steps and expected results to avoid ambiguity during testing. Each step should include only one action. Note: If you use QA Wizard Pro, you can record actions you perform in an application to automatically add steps to a new test case. See Recording test case steps with QA Wizard Pro, page 262. You can enter test case steps and expected results in the grid or free form view.
n
In the grid view, you enter steps and related information in rows and columns. See Entering steps in the grid view, page 260. In the free form view, you enter text and use mark up codes to indicate the type of information on each line (e.g., step or expected result). You may want to use free form view after you become more familiar with adding test case steps. See Entering steps as free form text, page 257.
Entering steps as free form text

Use the free form view to enter test case steps as text. Mark up codes indicate the type of text you enter on each line. 1. Click the Steps tab when you are adding or editing a test case. 2. Click the Free Form tab.
257
3. Select a Display test runs generated for this test case option to indicate how test case steps are displayed in test runs. Note: This option may not be available depending on the test run compliance settings.
n
Grid View displays steps in the grid view in test runs. See Entering test results in the grid view, page 285. Detail Grid View displays steps in the detail grid view in test runs. This view guides users stepby-step through the test run and allows them to enter results (Pass, Fail, Undetermined) on each step. See Entering test results in the detail grid view, page 286. Free Form Text View displays steps as text in test runs. See Entering test results in free form view, page 289.
4. Enter the mark up code to indicate the type of line you are entering. See Test case mark up codes, page 259. Mark up codes must be at the beginning of a text line. 5. Enter steps, expected, results, comments, or other information after mark up code. You can use test variant field codes in the text. When you generate test runs, field codes are replaced with the variant values. For example, if you have an Operating System variant with a %Z_ OSVARIANT% field code and the Windows value is used to generate test runs, the field code is replaced with Windows in the test run. Note: If you do not know the available test variant field codes, ask an administrative user for help. If you have administrative privileges to create custom fields, see Custom field codes, page 550. 6. Click Insert Shared Steps to insert steps from another test case. See Inserting shared steps from other test cases, page 264. All steps from the shared test case are included when test runs are generated.
258
7. Click the Screen Capture button to capture and attach a screenshot. See Capturing Screenshots, page 55. 8. Click the Insert Attachment button to insert a file or SCC attachment to provide additional information for the test. See Inserting attachments in test case steps, page 263. 9. If the test case has syntax errors, which are displayed in red, manually fix the errors or click Correct Steps to automatically fix them. See Correcting test case step errors, page 265. You cannot generate test runs in detail grid view from test cases with errors. 10. Click Add or OK to save the changes, or click another tab to enter additional test case information.
Test case mark up codes

Following are mark up codes to use to indicate the line type when you are entering test case steps as text. See Entering steps as free form text, page 257. Mark up codes must be at the beginning of each text line. Code Indicates: * + Step Expected result Expected result attachment Example *Start the application. +The application opens. Must follow a step, expected result, or step note. Notes
^123 [LoginDialog.jpg] ^123s [mainline::mainline/test/log.txt]
Must follow a step or expected result. A step or expected result can only have one attachment line. Separate multiple attachments in a line with a semicolon. The file attachment record ID follows the code and the attachment filename is in brackets. SCC file attachment IDs are appended with an 's' (e.g., 8s). A hyperlink to the attachment is automatically created. You can mouse over hyperlinks to view additional file information. Must precede or follow a step.
Comment
#The list should not include inactive projects. @23 [TC-15]
Shared test case
The number following the code is the test case record ID and the text in the brackets is the test case number. A hyperlink to the test case is automatically created. Must follow a step. Step notes are only included in test runs generated in detail grid view. If test runs are generated in grid or free form text view, step notes are converted to comments.
##
Step note
##The password is admin.
259
Tip: You can manually insert attachments and shared test case steps on the Free Form tab, but it is easier to click the Insert Attachment or Insert Shared Steps button because the record ID is automatically inserted. If you want to manually enter attachments that are already attached to test cases, the record ID is displayed in the ID column on the Attachments or Source Code tab on the test case Files tab.
Example
@42 [TC-39] *Run the attached batch file. +Verify that the script file runs and updates the status correctly. ^8 [failure.txt];9 [script.qawscript];8s [sccfile.txt] #The batch file returns a failure.
Test run codes

The following codes are displayed in test runs viewed in the audit trail, list window columns, or through SOAP. They are not used when entering test run results. Code Indicates: ~ Step result Example ~2;1;2011-03-10T10:07:34-00:00 The first parameter (2) indicates the step result - 0: Not Yet Run, 1: Passed, 2: Failed, 3: Undetermined. The second parameter (1) indicates the record ID for the user who entered the step result. The third parameter (2011-03-10T10:07:3400:00) indicates the date/time the step result was set. ? Actual result Actual result attachment Problem statement ?The login dialog box did not open.
%123 [LoginDialog.jpg]
!An error was displayed instead of the login dialog box.
Entering steps in the grid view

Use the grid view to enter test case steps, expected results, and comments in rows and columns. 1. Click the Steps tab when you are adding or editing a test case. 2. Click the Grid tab.
260
3. Select a Display test runs generated for this test case option to indicate how test case steps are displayed in test runs. Note: This option may not be available depending on the test run compliance settings.
n
Grid View displays steps in the grid view in test runs. See Entering test results in the grid view, page 285. Detail Grid View displays steps in the detail grid view in test runs. This view guides users stepby-step through the test run and allows them to enter results (Pass, Fail, Undetermined) on each step. See Entering test results in the detail grid view, page 286. Free Form Text View displays steps as text in test runs. See Entering test results in free form view, page 289.
4. Click a cell in the Step column and enter instructions for performing the action. You can use test variant field codes in steps. When you generate test runs, field codes are replaced with the variant values. For example, if you have an Operating System variant with a %Z_ OSVARIANT% field code and the Windows value is used to generate test runs, the field code is replaced with Windows in the test run. Note: If you do not know the available test variant field codes, ask an administrative user for help. If you have administrative privileges to create custom fields, see Custom field codes, page 550. 5. Click a cell in the Expected Result column and enter the expected results for the corresponding step. To insert additional expected result lines in a step, select it and click Insert Expected Result. You may want to enter each result on a separate line if the step has more than one expected result. If an issue occurs during the test, problem statements can be entered for each expected result. 6. Optionally insert attachments in the Attachments column to provide additional information about the step, such as screenshots. See Inserting attachments in test case steps, page 263.
261
7. Click the next row to enter additional steps. Tip: You can copy and move steps and comments. To copy a step or comment, select it and drag it to the new location. To move a step or comment, select it, press Shift, and drag it to the new location. 8. Select a row and click Insert Comment to insert a comment that provides additional information about a step. If detail grid view is used to generate test runs, you can also insert step notes, which are notes associated with a specific step. To insert a step note, select a step, click Insert Comment, and then select Insert Step Note. Note: You can convert comments to step notes and vice versa. To convert a comment, right-click it and choose Convert to Step Note. To convert a step note, right-click it and choose Convert to Comment. 9. Select a row and click Insert Shared Steps to insert steps from another test case. See Inserting shared steps from other test cases, page 264. All steps from the shared test case are included when test runs are generated from the test case. 10. Select a step and click Insert Step to insert a step in the row below the selected step. 11. Select a row and click Delete to delete it. 12. Click Add or OK to save the changes, or click another tab to enter additional test case information.
Recording test case steps with QA Wizard Pro

If you use QA Wizard Pro, you can record test case steps instead of manually entering them. To record steps, you interact with applications the same as when you record scripts from QA Wizard Pro. The actions are automatically entered as steps in a new test case in TestTrack TCM. Recording steps saves time when you need to document longer tests and reduces the possibility of incorrect or incomplete test cases.. Note: QA Wizard Pro 2012.0 or later must be installed on the computer running the TestTrack Client. 1. Choose Create >Test Case from QA Wizard Pro. QA Wizard Pro starts and the Record New Test Case dialog box opens.
262
2. Select the application you want to record against or click New to add an application. Select Connect to running application to record against an instance of a Windows application running on the test computer. 3. Click Record. The application starts and the Recording New Test Case toolbar opens. 4. Navigate through the application, performing the actions you want to record. 5. Click the Stop Recording toolbar button. The Add Test Case dialog box opens and the recorded steps are displayed. A screenshot is attached to each step.
6. Enter the test case Summary, Type, and any additional information, including expected results. You can modify the steps before saving the test case. See Adding Test Cases, page 255. 7. Click Add when you finish entering the test case information. The test case is saved and added to the project.
Inserting attachments in test case steps

You can insert attachments in test case steps and expected results to provide additional information for users performing test runs. Attachments are copied to generated test runs. 1. Click the Steps tab when you are adding or editing a test case. 2. If you are entering steps in the grid view, select the step or expected result you want to add the attachment to. If you are entering steps as free form text, select the line where you want to insert the attachment. 3. Click the Insert Attachment button and select an option.
n
New file attachment attaches a file that is not yet attached to the test case. The Attach Files dialog box opens. Browse to locate the file and click Open.
263
Existing file attachment attaches an existing file from the test case Attachments tab. The Select Attachments dialog box opens. Select the attachment and click OK. New SCC attachment attaches a source code file. See Attaching source code files, page 499.
The attachment is added to the Attachments column in grid view or the selected line in free form view, and the test case Files tab. 4. Click the Screen Capture button to capture and attach a screenshot. See Capturing Screenshots, page 55. To paste an image from the clipboard, right-click and choose Paste from Clipboard. 5. Double-click an attachment to view it. 6. Select an attachment and click Delete Attachment to delete it.
Inserting shared steps from other test cases

You can share steps between test cases, making it easy to use a set of steps in multiple tests and reducing maintenance effort when steps change. When you insert shared steps, a hyperlink to the shared test case is added to the test case. When test runs are generated, all steps from the shared test case and any attachments are included in the test runs. By default, a link is created between the test cases when you insert shared steps. The link is displayed on the test case Links tab. If you remove shared steps from a test case, the link is also removed. Linking options are configured in the item mapping rules. See Configuring Item Mapping Rules, page 460. 1. Click the Steps tab when you are adding or editing a test case. 2. Select the line where you want to insert the test case steps and click Insert Shared Steps. The Insert Shared Steps from Test Cases dialog box opens.
Note: This dialog box includes many of the same functions as the Test Cases list window. For example, you can filter the test cases or search for specific test cases. 3. Select the test case you want to insert.
264
4. Select a Link Definition to use to link the test cases. This option may not be available depending on the item mapping rules for shared test cases. 5. Click Insert. A hyperlink to the selected test case is added to the test case steps. Click the hyperlink to view the test case.
Correcting test case step errors

If test case steps contain errors, test runs cannot be generated in detail grid view. Errors generally occur if incorrect syntax is used in free form view or references to test case steps or attachments are not found. You must correct any errors before generating test runs. 1. Review any errors on the test case Steps tab. In free form view, errors are displayed in red. You can mouse over the text for more information about the error.
In grid view, an error is displayed and the line that contains the error is highlighted.
265
M an agin g Te st Var ian t s
2. Click Correct Steps to automatically correct errors. The steps are corrected. Note: If TestTrack cannot correct the steps, you must correct them manually.
Managing Test Variants

Test variants are attributes of the tested application used to generate test runs. A test run is created for each unique combination of test variant values selected when generating test runs. For example, you are testing an application that is supported on the Windows, Mac, Linux, and Solaris operating systems. You want the test to be performed on the Windows and Mac operating systems only. The TestTrack project includes a test variant named Operating System that includes values for each of the four supported operating systems. When you generate test runs, you can select the Windows and Mac test variant values so test runs are only generated for those operating systems. Each test run includes identical information except for the test variant value, which indicates the operating system that the test run is performed on. Within a test case, you can select test variant values that are always included or excluded when test runs are generated.
n
Included test variant values are the only values used when test runs are generated. Other values added to the same test variant later cannot be used to generate test runs. Excluded test variant values are never used to generate test runs. Other values added to the same test variant later are always used to generate test runs.
Note: The TestTrack administrator or another high-level user is generally responsible for creating test variants. See Adding test variant custom fields, page 386. 1. Click the Variants tab when you are adding or editing a test case. This tab is used to manage the variants that are included or excluded when generating test runs.
266
M an agin g In cl u d e d Te st Var ian t s
2. Add or make changes to the Included Test Variant Values. Included test variants are always used to generate test runs. See Managing Included Test Variants, page 267.
n
Click Add Variant to add included variant values. See Adding included test variants, page 268. Select a variant and click Edit Variant to change the values. See Editing included test variants, page 268. Select a variant and click Remove Variant to remove it. See Removing included test variants, page 269.
3. Add or make changes to the Excluded Test Variant Values. Excluded test variants are never used to generate test runs. See Managing Excluded Test Variants, page 269.
n
Click Add Variant to add excluded variant values. See Adding excluded test variants, page 269. Select a variant and click Edit Variant to change the values. See Editing excluded test variants, page 270. Select a variant and click Remove Variant to remove it. See Removing excluded test variants, page 270.
4. Click Add or OK to save the changes, or click another tab to enter additional test case information.
Managing Included Test Variants

You can add included test variant values in a test case to specify the values that are always used to generate test runs. If you add included test variant values, no other values in the test variant are used to generate test runs.
267
M an agin g In cl u d e d Te st Var ian t s
For example, the application component you are testing is only supported on Windows. The TestTrack project includes a test variant named Operating System that includes other operating system values. You may want to add Windows as an included test variant value so test runs are only generated for Windows, and not other operating systems. If a value is added to the test variant in the future, test runs are not generated for the value unless it is added as an included test variant value. See Adding included test variants, page 268. Note: The TestTrack administrator or another high-level user is generally responsible for creating test variants. See Adding test variant custom fields, page 386.
Adding included test variants

Add included test variants to a test case to specify the values that are always used to generate test runs. No other values in the test variant are used to generate test runs. 1. Click the Variants tab when you are editing a test case. 2. Click Add Variant in the Included Test Variant Values area. The Add Included Test Variant Values dialog box opens.
3. Select a Variant. The corresponding variant values are displayed. 4. Select the variant Values to include when generating test runs. 5. Click OK. The selected values are added to the Included Test Variant Values area. Note: If a test variant is added to the Included Test Variant Values list, it cannot be added as an excluded test variant. See Managing Excluded Test Variants, page 269.
Editing included test variants

You can change the test variant values that are excluded when generating test runs. 1. Click the Variants tab when you are editing a test case. 2. Select a test variant in the Included Test Variant Values area. 3. Click Edit Variant. The Edit Included Test Variant Values dialog box opens.
268
M an agin g Excl u d e d Te st Var ian t s
4. Make any changes. 5. Click OK to save the changes.
Removing included test variants

Remove included test variants if you no longer want to include them when test runs are generated. 1. Click the Variants tab when you are editing a test case. 2. Click the Variants tab. 3. Select a variant in the Included Test Variant Values area. 4. Click Remove Variant. You are prompted to confirm the removal. 5. Click Yes. The variant is removed. 6. Click OK to save the changes.
Managing Excluded Test Variants

You can add excluded test variant values to a test case to specify the values that are never used to generate test runs. If you add excluded test variant values, all values in the test variant except the excluded value are used to generate test runs. For example, the component you are testing is supported on Windows and Mac, but not supported on Linux. The TestTrack project includes a test variant named Operating System that includes Windows, Mac, and Linux values. You can add the Linux test variant value as an excluded value to test runs are always generated for the other operating systems, but not Linux. If a value is added to an excluded test variant in the future, test runs are generated for the new value. You must exclude the new value if you do not want to include it in test runs. See Adding excluded test variants, page 269. Note: The TestTrack administrator or another high-level user is generally responsible for creating test variants. See Adding test variant custom fields, page 386.
Adding excluded test variants

Add excluded test variants to a test case to specify the values that are never used to generate test runs. All other values in the test variant are used to generate test runs. 1. Click the Variants tab when you are editing a test case. 2. Click Add Variant in the Excluded Test Variant Values area. The Add Excluded Test Variant Values dialog box opens.
269
M an agin g Excl u d e d Te st Var ian t s
3. Select a Variant. The corresponding variant values are displayed. 4. Select the variant Values to exclude when generating test runs. 5. Click OK. The selected values are added to the Excluded Test Variant Values area. Note: If a test variant is added to the Excluded Test Variant Values list, it cannot be added as an included test variant. See Managing Included Test Variants, page 267.
Editing excluded test variants

You can change the test variant values that are excluded when generating test runs. 1. Click the Variants tab when you are editing a test case. 2. Select a variant in the Excluded Test Variant Values area. 3. Click Edit Variant. The Edit Excluded Variant Values dialog box opens. 4. Make any changes. 5. Click OK to save the changes.
Removing excluded test variants

Remove excluded variants if you no longer want to exclude them when test runs are generated. 1. Click the Variants tab when you are editing a test case. 2. Select a variant in the Excluded Test Variant Values area. 3. Click Remove Variant. You are prompted to confirm the removal. 4. Click Yes. The variant is removed. 5. Click OK to save the changes.
270
Wor kin g wit h Te st Case s
Working with Test Cases

TestTrack TCM helps you manage test cases throughout the testing cycle. The test cases workflow consists of states, events, and transitions that define the path a test case takes from start to close. To move a test case through the workflow, it is assigned to users who perform the event assigned to them. The default test cases workflow can be used out of the box or customized to support your testing process. See About the default test cases workflow, page 271 and Customizing Workflows, page 414.
About the default test cases workflow

The default test case workflow includes the following events: Assign, Estimate, Enter Work, Ready, Ready for Review, Needs Change, Reviewed, Hold, Resume, Obsolete, Re-Open, and Comment. The workflow can be used out of the box or customized to support your testing process. See Customizing Workflows, page 414.
Assigning test cases

To move a test case through the workflow, you need to assign it to a user. For example, you may want to assign a test case that needs changes to a tester. 1. Select the test case and choose Activities > Assign. The Assign dialog box opens.
2. Select an Assign By user. This field defaults to the logged in user. 3. Select an Assign To user. Click the Find button to search for a user. See Finding users and customers, page 39. 4. The Date defaults to the current date and time. You can enter another date and time. 5. Enter any Notes about the assignment. For example, you can let the user know what action you want them to perform or who to contact for additional information. 6. Select a Priority. 7. The Due Date defaults to the current date. You can also enter another date.
271
Ab ou t t h e d e fau l t t e st case s wor kfl ow
8. Click OK. Note: When a test case is assigned to you, open the test case and click the Workflow tab to review the assignment notes. The user who assigned the test case should let you know what work you are responsible for and provide detailed information. If you need more information, email the user who assigned the test case. See Emailing from TestTrack, page 73.
Estimating test case development time

You may want to enter the estimated effort required to complete work on the test case. In most organizations, a project manager or team lead is responsible for entering the estimated effort. After the estimate information is entered, you can track and view the time a task should take. 1. Select the test case and choose Activities > Estimate. The Estimate dialog box opens.
2. Select an Estimate By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the Estimated Time in hours to work on the test case. 5. Enter any Notes. 6. The Completion Date defaults to the current date. You can also enter another date. 7. Click OK.
Entering work on test cases

As you work on test cases, you can enter the work you have completed to keep the project manager or QA team lead informed about your progress. 1. Select the test case and choose Activities > Enter Work. The Enter Work dialog box opens.
272
2. Select an Enter Work By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the Actual Effort in hours to work on the test case. This information can help with future planning and metrics. 5. Enter any Notes. It is helpful to provide information about the work you completed so far. 6. Enter the Remaining Time in hours to complete the test case. 7. Click OK.
Marking test cases as ready

If a new test case does not require a review, you can move it to the Ready state to indicate that test runs can be generated for it. 1. Select the test case and choose Activities > Ready. The Ready dialog box opens.
2. Select a Ready By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the Actual Effort in hours to work on the test case. This information can help with future planning and metrics. 5. Enter any Notes. 6. Click OK. The test case status changes to Ready.
273
Submitting test cases for review

After you create or change a test case, you should submit it to a QA team member or manager for review. 1. Select the test case and choose Activities > Ready for Review. The Ready for Review dialog box opens.
2. Select a Ready for Review By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the Actual Effort in hours to work on the test case. This information can help with future planning and metrics. 5. Enter any Notes. It is helpful to include information about what changed in the test case. 6. Click OK. The test case status changes to Ready for Review.
Reviewing test cases

After a test case is reviewed, you can indicate that it is ready for test runs to be generated for it or you can indicate that it needs changes. 1. Select the test case and choose Activities > Reviewed. The Reviewed dialog box opens.
2. Select a Reviewed By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Select the Resulting State. The resulting state indicates the workflow state that the test case moves to next.
274
n n
Change Needed indicates the test case needs to be changed. Ready indicates the test case is complete and test runs can be generated for it.
5. Enter the Actual Effort in hours to review the test case. This information can help with future planning and metrics. 6. Enter any Notes. If changes are needed, explain the revisions needed. 7. Click OK. The test case status changes to the resulting state you selected.
Requesting test case changes

A test case may require revisions if the tested application changes. 1. Select the test case and choose Activities > Needs Change. The Needs Change dialog box opens.
2. Select a By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to include information about what needs to be changed. 5. Select the Reason the test case needs to be changed. 6. Click OK. The test case status changes to Change Needed.
Placing test cases on hold

You can place a test case on hold so test runs cannot be generated from it. 1. Select the test case and choose Activities > Hold. The Hold dialog box opens.
275
2. Select a Hold By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to include an explanation for placing the test case on hold. 5. Select the Reason for placing the test case on hold. 6. Click OK. The test case status changes to On Hold.
Resuming on hold test cases

You can resume test cases that are on hold so test runs can be generated for them. 1. Select the test case and choose Activities > Resume. The Resume dialog box opens.
2. Select a Resume By user. The field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to include the reason for resuming the on hold test case. 5. Click OK. The test case status changes to Ready.
Closing obsolete test cases

You can close an obsolete test case if it is no longer used. 1. Select the test case and choose Activities > Obsolete. The Obsolete dialog box opens.
276
2. Select an Obsolete By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to provide information about why the test case is obsolete. 5. Select a Reason for closing the test case. 6. Click OK. The test case status changes to Obsolete.
Reopening test cases

You can reopen obsolete test cases if you want use them again. 1. Select the test case and choose Activities > Re-Open. The Re-Open dialog box opens.
2. Select a Re-Open By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to include the reason for reopening the test case. 5. Click OK. The test case status changes to Ready.
Adding comments to test cases

You can add comments to a test case to clarify information or add notes for another user. 1. Select the test case and choose Activities > Comment. The Comment dialog box opens.
277
Vie win g t e st case wor kfl ow h ist or y
2. Select a Comment By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the comments in the Notes field. 5. Click OK. The comments are added to the test case workflow history. Note: To view test case comments, select the test case, click View or Edit, and then click the Workflow tab. All comments are displayed on the Workflow tab.
Viewing test case workflow history

You can view where a test case is in the workflow, test case assignments, and any comments or additional information entered about a test case. You can also view time tracking information and a workflow history diagram. 1. Click the Workflow tab when you are viewing or editing a test case. The events added to the test case are displayed.
Note: Select Show System Comments to display events added by automation rules. 2. Click Work Items to view events with time tracking information, including the estimated, actual, and remaining work for the test case. See Viewing work items, page 44. 3. Click Diagram to view a diagram of the workflow states the test case was previously in, the events used to move the test case between states, and potential next states. See Viewing item workflow history diagrams, page 43. 4. Select an event to view the event notes.
278
Cr e at in g Te st Ru n S e t s
5. Select an event and choose Edit > View Event to view the event details. See Viewing workflow event details, page 41. 6. Select an event and choose Edit > Edit Event to edit the event details. See Editing workflow event details, page 42. 7. Select an event and choose Edit > Delete Event to delete it. See Deleting workflow events from items, page 42. 8. Click OK to save the changes.
Creating Test Run Sets

A test run set is a group of related test runs. When you generate test runs, you can add the new test runs to a test run set. When testing multiple builds in parallel, test run sets allow you to report on each test initiative and determine the current status. Tip: While test run sets are similar to folders, the advantage is that the test run set is displayed in the main area of the Edit Test Run and View Test Run windows. Users must click the Folders tab to view the folders a test run is stored in. When deciding on the test run sets to create, it is important to consider how you want to view information in test run reports to monitor progress. Think about the information you will need at the end of each phase to determine if you are ready to move on to the next phase. Refer to the schedule in the test plan and create a test run set for each milestone and then create any additional sets that are needed. 1. Choose Tools > Configure List Values > Test Run Set Values. The Setup Test Run Set Names dialog box opens. Note: You can also click the Configure button in the Generate Test Runs dialog box to create test run sets.
2. Click Add. The Add Test Run Set dialog box opens. 3. Enter a test run set name. 4. Click OK. You return to the Setup Test Run Names dialog box.
279
Ge n e r at in g Te st Ru n s
5. Select a list value and click Top, Move Up, Move Down, or Bottom to change the display order. You may want to move the most frequently used test run sets to the top of the list. 6. Click OK to save the changes.
Generating Test Runs

Test runs are instances of test cases that are generated at a milestone in the testing cycle, such as when a build is provided by the development team. A test run contains all information from the related test case, but also includes the results of a specific instance of the test. A single test case can have one or more related test runs depending on the test variants selected when test runs are generated. For example, an application supports multiple languages, but a test case only applies to the English, French, and Spanish versions. You can select these versions when you generate test runs, which creates a test run for each selected version. The test runs include identical information except for the test variant value, which indicates the language to use for testing. Test runs are assigned to testers to perform the test and document the results. A tester can pass or fail a test run and indicate the actual results if they are different from the expected results specified in the test case. Keep the following in mind:
n
Test cases are reused for future testing efforts. Test runs are only used once during the testing cycle they are generated for. Test runs are modified to indicate the test results. Test cases generally remain static unless they need to be modified because of an application change or incorrect information. Test case custom field values are only copied to test runs if they are mapped to test run fields. See Configuring Item Mapping Rules, page 460.
1. Select a test case in the Ready state. A test case must be in the Ready state before test runs can be generated for it. See Marking test cases as ready, page 273 and Reviewing test cases, page 274. 2. Choose Activities > Generate Test Runs. The Generate Test Runs dialog box opens.
280
Ge n e r at in g Te st Ru n s
3. Select the Test Run Set you want to associate the new test runs with. A test run set is a group of related test runs. For example, you may want to include all test runs generated for alpha testing in a set and include all test runs generated for beta testing in another set. Note: The TestTrack administrator or another high-level user is generally responsible for creating test run sets. See Creating Test Run Sets, page 279. 4. Select a folder option for the new test runs. You must create the folders before generating the test runs. See Adding folders, page 61. You can add test runs to folders to group them with related items. For example, you may want to group test runs in folders based on functional area or test type.
n n
Select Do not add to a folder if you do not want to add the test runs to a folder. Select Add to the selected folder to add the test runs to a folder. Click Browse. Select a folder and click OK.
5. Optionally select the Test Variants you want to use to generate test runs. A test run is created for each unique combination of test variant values that you select. If you are generating test runs for multiple test cases, the available values are a combination of included and excluded test variants for the selected test cases. Tip: Review the number of test runs that will be generated, which is displayed at the bottom of the Generate Test Runs dialog box. If you select multiple test variant values, the number of generated test runs can multiply quickly, which may impact performance. 6. Click OK. The test runs are generated. To work with test runs, choose View > Test Runs to open the Test Runs list window. See Running Tests, page 284.
281
Re ge n e r at in g Te st Ru n s
Note: If test runs cannot be generated, an error dialog box opens. You may need to modify test cases you are generating test runs from to fix any errors. See Resolving test run generation errors, page 282.
Resolving test run generation errors

Errors are displayed if test runs cannot be generated or regenerated. Errors may occur if the test case is open for editing, the test case syntax is incorrect, file attachments cannot be found, the test case is not in a workflow state that allows test runs to be generated, and other reasons. You must correct any errors in the test cases before generating test runs. 1. The Test Run Generation Failures dialog box opens when generating or regenerating test runs. The test case number that test runs could not be generated for and the problem are displayed.
2. Select a problem and click Copy to Clipboard to copy the problem text to the clipboard. 3. Select a problem and click Correct and Retry to automatically fix the test case errors or click Edit Items to manually fix them. You must manually correct errors if TestTrack cannot automatically correct them. Generate test runs again after correcting the test case. See Generating Test Runs, page 280. 4. Click Close to close the dialog box.
Regenerating Test Runs

If you need to rerun a failed or unclear test run, you can regenerate the test run instead of changing the results. Regenerated test runs include the same test variants, folders, and test run sets as the original test runs. Actual results, step results (e.g., Pass, Fail, Undetermined), and step notes are not copied from existing test runs. For example, your organizations business rules state that a product with failed test runs cannot be released. After the issue that caused a test run to fail is fixed, you can regenerate the related test run and use it to verify the fix and enter the results. This allows you to maintain an accurate history of test run failures. 1. Select the test runs you want to regenerate on the Test Runs list window. 2. Choose Activities > Regenerate Test Runs. The Regenerate Test Runs dialog box opens.
282
Re ge n e r at in g Te st Ru n s
3. Select Update the test runs using information from the parent test case to copy the information from the related test cases. The regenerated test runs will include any updates made to the related test case since the original test runs were generated. If this option is not selected, the updated test case information is not used and the original test run information is copied to the regenerated test run. 4. Select Add event to the original test runs to add a workflow event to the original test runs. Select an event. The list includes valid events for all selected test runs with no more than one resulting state. This option can help you differentiate regenerated failed or unclear test runs from test runs that have not been regenerated. For example, the default test runs workflow includes an Ignore Result event with a closed resulting state named Closed (Ignored). Select this option to add the event to the original failed test runs and move them to the Closed (Ignored) state. These test runs are excluded when you view failed test runs in filters, reports, and other areas. Note: Test run compliance rules may prevent adding the event to the original test run and regenerating the test runs. For example, if all steps in the original test run do not have a Pass result, compliance rules may prevent you from adding the Pass event to the original test run. An error is displayed if test runs cannot be regenerated. 5. Select Link the regenerated test runs with the original test runs to link the new test runs with the original test runs.
n n
Select a Link definition. The list includes all peer link definitions allowed for test runs. Enter a Link comment. The comment is displayed on the test run Links tab and on the link diagram.
6. Click OK. The test runs are regenerated. Note: If test runs cannot be regenerated, an error dialog box opens. You may need to modify the original test cases the test runs were generated from to fix any errors. See Resolving test run generation errors, page 282.
283
Vie win g Te st Ru n s
Viewing Test Runs

You can view read-only test run information. You can also create issues, view the related test case, send email, or enter test run events. See Running Tests, page 284 for information about performing test runs and entering results. 1. Select the test run on the Test Runs list window. 2. Choose Edit > View Test Run. The View Test Run dialog box opens. 3. Click Go To Test Case to view the related test case. See Viewing Test Cases, page 319. 4. Click Create Issue to add a TestTrack Pro issue. See Creating Issues From Test Runs, page 299. 5. Click Send Email to email a user about the test run. See Emailing from TestTrack, page 73. Note: Click the Email tab to view or reply to tracked email. See Viewing tracked email, page 75 and Replying to tracked email, page 76. 6. Click Edit to edit the test run. See Editing Test Runs, page 314. 7. Click OK to close the View Test Run dialog box.
Running Tests
Running a test generally involves the following steps. 1. Open the test run and review information about setting up the test. See Viewing Test Runs, page 284.
n
The Details tab displays general information about the related test case, such as the description, scope, conditions that must be met before performing the test, and the overall expected results. The Variants tab displays information about the variable elements of the application that need to be tested. This information can help you make sure you are using the correct environment to perform the test. You can also add additional variants used during the test. See Managing runtime test variants, page 290. The Files tab may include files or scripts to use when performing the test.
2. Review the test run steps on the Steps tab. Steps are displayed in one of the following views depending on test case setting for generating test runs or the test run compliance settings:
n
Grid view displays steps and expected results in rows and columns. See Entering test results in the grid view, page 285. Detail grid view displays an overview pane that provides a read-only view of the entire test run and a detail pane that guides you step-by-step through the test run. You can enter results (Pass, Fail, Undetermined) for each step in this view. See Entering test results in the detail grid view, page 286. Free form view displays steps as text. Mark up codes indicate the type of text on each line. See Entering test results in free form view, page 289.
3. Perform the steps in the test run. If the actual and expected results do not match, you can add problem statements and attachments to document the issues.
284
Ru n n in g Te st s
4. Enter the overall test result. See Entering Overall Test Run Results, page 297. If you find bugs during the test, you can create issues to report the issues. See Creating Issues From Test Runs, page 299. Tip: TestTrack TCM includes two default report stylesheets that are useful for manual testing. The TestRunStepsDetailReport.xslt stylesheet generates a report with test run steps and fields for handwritten information, including lines for results, problem statements, and signature. The TestRunReport.xslt stylesheet generates a report with test case detail and fields for handwritten information, including lines for results, problem statements, and signature. See Generating Reports, page 70.
Entering test results in the grid view

Test runs displayed in grid view include test steps, expected results, and attachments organized in rows and columns. If issues occur during the test, you can enter problem statements to indicate actual results are different from expected results. Problem statements, which are used when creating issues from test runs, should be specific so other users can reproduce the issue. For example, if you perform a step to log in to the tested application and the login fails, you can enter the error message that opens or other behavior that occurs. Tip: Review all information in the test run before running the test and entering results. See Running Tests, page 284. 1. Select a test run on the Test Runs list window and choose Edit > Edit Test Run. The Edit Test Run dialog box opens. 2. Click the Steps tab. The read-only test case steps are displayed.
3. Perform each step. Make sure the actual results match any expected results provided.
285
Ru n n in g Te st s
Note: The Attachments column may provide additional files you need to perform a step. Doubleclick an attachment to view it. 4. If an issue occurs when you perform a step, double-click the corresponding cell in the Problem Statement column and enter information to describe the issue. By default, problem statements are displayed on the same row as the related step. Select View problem statements on separate line to display problem statements in rows under the related steps. If this option is selected, select a step and click Insert Problem Statement to add a statement below the step. Note: You can also add attachments to help other users understand issues you encountered. See Attaching Files, page 54. 5. Select the check box in the step row when you complete the step. This can help you track your progress in the test run. 6. Click Create Issue to add an issue to report any issues found during testing. See Creating Issues From Test Runs, page 299. 7. Click Go To Test Case to view the related test case. See Viewing Test Cases, page 319. 8. Click Send Email to email a user about the test run. See Emailing from TestTrack, page 73. 9. Click OK to save the changes or click another tab to add more test run information. Note: If the test run is complete, make sure you enter the overall test result (e.g., Passed, Failed, or Undetermined). See Entering Overall Test Run Results, page 297.
Entering test results in the detail grid view

Test runs displayed in detail grid view include an overview pane that provides a read-only view of the entire test run and a detail pane that guides you step-by-step through the test run. You can enter results (e.g., Pass, Fail, Undetermined) for each step in this view. If issues occur during the test, you can enter problem statements to indicate actual results are different from expected results. Problem statements, which are used when creating issues from test runs, should be specific so other users can reproduce the issue. For example, if you perform a step to log in to the tested application and the login fails, you can enter the error message that opens or other behavior that occurs. Tip: Review all information in the test run before running the test and entering results. See Running Tests, page 284. 1. Select a test run on the Test Runs list window and choose Edit > Edit Test Run. The Edit Test Run dialog box opens. 2. Click the Steps tab. The read-only test case steps and details for step 1 are displayed. The step status is displayed in the step detail pane.
286
Ru n n in g Te st s
3. Perform step 1 or select the step you want to perform in the overview pane. 4. If the actual results do not match the expected results or you experience an issue, click Add Problem Statement below the step or in the Expected Results area to enter a statement. 5. If you want to add additional information to the step, click Add Step Note to add a note. 6. Enter the Actual Results observed when you perform the step. 7. To add attachments to support the actual results, click the Attachment button and select an option. See Inserting attachments in test run steps, page 288. 8. Click Pass, Fail, or Undetermined to specify the step result. The available step results depend on the project settings. The step status changes. Note: Choose Activities > Pass All Steps to pass all steps in the test run. 9. Click the right arrow button to navigate to the next step or select a step in the overview pane. Tip: You can set a local option to automatically move to the next step in the test run after entering a step result. See Setting TestTrack TCM options, page 347. 10. Repeat steps 4-9 until all steps are complete. 11. Click Create Issue to add an issue to report any issues found during testing. See Creating Issues From Test Runs, page 299. 12. Click Go To Test Case to view the related test case. See Viewing Test Cases, page 319. 13. Click Send Email to email a user about the test run. See Emailing from TestTrack, page 73. 14. Click OK to save the changes or click another tab to add more test run information.
287
Ru n n in g Te st s
Note: If the test run is complete, make sure you enter the overall test result (e.g., Passed, Failed, or Undetermined). See Entering Overall Test Run Results, page 297.
Step status icons

The following status icons are displayed next to each test run step. If an icon is not displayed, the step does not yet have a result. Icon Description Step result is Passed Step result is Failed Step result is Undetermined Comment Step is missing information required based on compliance rules, such as an actual result
Inserting attachments in test run steps

You can insert attachments in test run steps displayed in detail grid view to provide additional information about the actual test results. Note: See Attaching Files, page 54 for information about attaching files to test runs displayed in grid view or free form view. 1. Click the Steps tab when you are editing a test run. 2. Click the Insert Attachment button and select an option.
n
New file attachment attaches a file that is not yet attached to the test run. The Attach Files dialog box opens. Browse to locate the file and click Open. Existing file attachment attaches an existing file from the test run Attachments tab. The Select Attachments dialog box opens. Select the attachment and click OK. New SCC attachment attaches a source code file. See Attaching source code files, page 499.
The attachment is added to the Attachments field and the test run Files tab. 3. Click the Screen Capture button to capture and attach a screenshot. See Capturing Screenshots, page 55. To paste an image from the clipboard, right-click and choose Paste from Clipboard. 4. Double-click an attachment to view it. 5. Select an attachment and click Delete Attachment to delete it.
288
Ru n n in g Te st s
Entering test results in free form view

Test runs displayed in free form view include steps and expected results as text. Mark up codes indicate the type of text line. If issues occur during the test, you can enter problem statements to indicate actual results are different from expected results. Problem statements, which are used when creating issues from test runs, should be specific so other users can reproduce the issue. For example, if you perform a step to log in to the tested application and the login fails, you can enter the error message that opens or other behavior that occurs. Tip: Review all information in the test run before running the test and entering results. See Running Tests, page 284. 1. Select a test run on the Test Runs list window and choose Edit > Edit Test Run. The Edit Test Run dialog box opens. 2. Click the Steps tab. The read-only test case steps are displayed.
3. Perform each step in the test run. Make sure the actual results match any expected results provided. Mark up codes indicate the type of text in each line, such as steps and expected results. See Test case mark up codes, page 259 for information about the codes. Note: Attachments may be included in the steps to provide additional information you need to perform the test. Click an attachment hyperlink to view it. 4. If an issue occurs when you perform a step, enter a Problem Statement to describe the issue. Note: You can also add attachments to help other users understand issues you encountered. See Attaching Files, page 54. 5. Click Create Issue to add an issue to report any issues found during testing. See Creating Issues From Test Runs, page 299. 6. Click Go To Test Case to view the related test case. See Viewing Test Cases, page 319.
289
M an agin g r u n -t ime t e st var ian t s
7. Click Send Email to email a user about the test run. See Emailing from TestTrack, page 73. 8. Click OK to save the changes or click another tab to add more test run information. Note: If the test run is complete, make sure you enter the overall test result (e.g., Passed, Failed, or Undetermined). See Entering Overall Test Run Results, page 297.
Managing run-time test variants

Test variants are attributes of the tested application that are used to generate test runs. A test run is created for each unique combination of the test variant values selected by the user who generates the test runs. When you perform a test run, you may test an attribute that is covered by a test variant in the TestTrack project. You can also add additional variants to indicate areas that were covered during testing, but were not identified when the test runs were generated. For example, the application you are testing supports multiple languages. The project includes two test variants: Operating System and Language. A test run is generated based on the Windows value in the Operating System test variant. No values are selected for the Language test variant. You want to indicate that you only performed the test on the English version of the application so you add the English test variant value to the test run. Note: Additional test runs are not created when you add test variant values to a test run. 1. Click the Variants tab when you are editing a test run. The test variants used to generate the test run and any additional variants added to the test run are displayed.
2. Click Add Variant Info to add test variants to the test run. See Adding run-time test variant information, page 291. 3. Select a variant and click Edit Variant Info to change it. See Editing run-time test variant information, page 291. 4. Select a variant and click Delete Variant Info to delete it. See Deleting run-time test variant information, page 291. 5. Click OK to save the changes or click another tab to add more test run information.
290
M an agin g r u n -t ime t e st var ian t s
Adding run-time test variant information

You can add additional test variant values to a test run to indicate areas that were covered during testing, which were not indicated in the test run. 1. Click the Variants tab when you are editing a test run. 2. Click Add Variant Info. The Add Additional Variant dialog box opens.
3. Select a Variant. The corresponding variant values are displayed. 4. Select the variant Values to include. 5. Click OK. The selected values are added to the Additional Run-Time Test Variant Values area.
Editing run-time test variant information

You can change the additional test variant values selected in a test run. 1. Click the Variants tab when you are editing a test run. 2. Select a test variant in the Additional Run-Time Test Variant Values area and click Edit Variant Info. The Edit Additional Variant dialog box opens. The selected variant is read-only. 3. Make any changes. 4. Click OK. The changes are saved.
Deleting run-time test variant information

You can delete test variant values that you no longer want to include in a test run. 1. Click the Variants tab when you are editing a test run. 2. Select a test variant in the Additional Run-Time Test Variant Values area and click Delete Variant Info. The test variant is deleted.
291
Wor kin g wit h Te st Ru n s
Working with Test Runs

The test runs workflow consists of states, events, and transitions that define the path a test run takes from start to close. To move a test run through the workflow, it is assigned to users who perform the event assigned to them. The default test runs workflow can be used out of the box or customized to support your testing process. See About the default test runs workflow, page 292 and Customizing Workflows, page 414.
About the default test runs workflow

The default test runs workflow includes the following events: Assign, Estimate, Start, Enter Work, Enter Result, Pass, Fail, Unclear, Hold, Resume, Re-Open, Ignore Result, and Comment. The workflow can be used out of the box or customized to support your testing process. See Customizing Workflows, page 414.
Assigning test runs

To move a test run through the workflow, you need to assign it to a user. For example, you assign a test run to a user to perform the test. The tester may assign the test run to the QA manager if they experience any issues during the test. 1. Select the test run and choose Activities > Assign. The Assign dialog box opens.
2. Select an Assign By user. This field defaults to the logged in user. 3. Select an Assign To user. Click the Find button to search for a user. See Finding users and customers, page 39. 4. The Date defaults to the current date and time. You can enter another date and time. 5. Enter any Notes about the assignment. For example, you can let the user know what action you want them to perform or who to contact for help. 6. Select a Priority. 7. The Due Date defaults to the current date. You can also enter another date.
292
Ab ou t t h e d e fau l t t e st r u n s wor kfl ow
8. Click OK. Note: When a test run is assigned to you, open the test run and click the Workflow tab to review the assignment notes. The user who assigned the test run should let you know what work you are responsible for and provide detailed information. If you need more information, email the user who assigned the test run. See Emailing from TestTrack, page 73.
Estimating time to perform test runs

You may want to enter the estimated effort required to perform a test run. In most organizations, a project manager or QA team lead is responsible for entering the estimated effort before assigning the test run. After the estimate information is entered, you can track and view the time it should take to complete a task. 1. Select the test run and choose Activities > Estimate. The Estimate dialog box opens.
2. Select an Estimate By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the Estimated Time in hours to perform the test. 5. Enter any Notes. 6. The Completion Date defaults to the current date. You can also enter another date. 7. Click OK.
Starting test runs

Start test runs when they are ready for testing to move them to the In Progress state. 1. Select the test run and choose Activities > Start. The test run status changes to In Progress.
Entering work on test runs

As you perform tests, you can enter the work you have completed to keep the project manager or QA team lead informed about your progress. 1. Select the test run and choose Activities > Enter Work.
293
The Enter Work dialog box opens.
2. Select an Enter Work By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the Actual Effort in hours to work on the test run. This information can help with future planning and metrics. 5. Enter any Notes. It is helpful to provide information about the work you completed so far. 6. Enter the Remaining Time in hours to complete the test run. 7. Click OK.
Placing test runs on hold

You can place a test run on hold if additional work needs to be completed before the test run is performed. For example, you may want to put a test run on hold if the required test environment is not available. 1. Select the test run and choose Activities > Hold. The Hold dialog box opens.
2. Select a Hold By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to include an explanation for placing the test run on hold. 5. Select a Reason for placing the test run on hold. 6. Click OK.
294
The test run status changes to On Hold.
Resuming on hold test runs

You can resume on hold test runs to move them to the Not Started or In Progress state. 1. Select the test run and choose Activities > Resume. The Resume dialog box opens.
2. Select a Resume By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Select the Resulting State to indicate the workflow state that the test run moves to next.
n n
Not Started moves the test run to the Not Started state. In Progress moves the test run to the In Progress state.
5. Enter any Notes. It is helpful to include information about why you are resuming the test run. 6. Click OK. The test run status changes to the resulting state you selected.
Reopening test runs

You can reopen closed test runs if you need to make changes or rerun the test. For example, you fail a test run and then discover it failed because the test computer was not set up correctly. You can reopen the test run and perform the test again. Tip: You may want to regenerate failed or unclear test runs instead of reopening them if you need to rerun tests. Modifying existing test run results may lead to an inaccurate test history and make it difficult to determine which failed or unclear tests need to be rerun. See Regenerating Test Runs, page 282. 1. Select the test run and choose Activities > Re-Open. The Re-Open dialog box opens.
295
Vie win g t e st r u n wor kfl ow h ist or y
2. Select a Re-Open By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter any Notes. It is helpful to include the reason for reopening the test run. 5. Click OK. The test run status changes to In Progress.
Adding comments to test runs

You can add comments to a test run. You may want to clarify information or add notes for another user. 1. Select the test run and choose Activities > Comment. The Comment dialog box opens.
2. Select a Comment By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Enter the comments in the Notes field. 5. Click OK. The comments are added to the test run workflow history. Note: To view test run comments, select the test run, click View or Edit, and then click the Workflow tab. All comments are displayed on the Workflow tab.
Viewing test run workflow history

You can view where a test run is in the workflow, test run assignments, and any comments or additional information entered about a test run. You can also view time tracking information and a workflow history diagram. 1. Click the Workflow tab when you are viewing or editing a test run.
296
En t e r in g Ove r al l Te st Ru n Re su l t s
The events added to the test run are displayed.
Note: Select Show System Comments to display events added by automation rules. 2. Click Work Items to view events with time tracking information, including the estimated, actual, and remaining work for the test run. See Viewing work items, page 44. 3. Click Diagram to view a diagram of the workflow states the test run was previously in, the events used to move the test run between states, and next available states. See Viewing item workflow history diagrams, page 43. 4. Select an event to view the event notes. 5. Select an event and choose Edit > View Event to view the event details. See Viewing workflow event details, page 41. 6. Select an event and choose Edit > Edit Event to edit the event details. See Editing workflow event details, page 42. 7. Select an event and choose Edit > Delete Event to delete it. See Deleting workflow events from items, page 42. 8. Click OK to save the changes.
Entering Overall Test Run Results

After you perform a test run, you can indicate if the test passed, failed, or if the results were unclear. Passed and failed test runs are closed. Unclear test runs remain open for further review. A test run may need to meet compliance rules before you can set the overall result. For example, if all steps in the test run do not have a Pass result, compliance rules may prevent you from passing the test run. Tip: You can enter test run results without opening an event dialog box, which is helpful when you do not have any result information to add. See Passing test runs, page 298, Failing test runs, page 298, and Indicating unclear test run results, page 299. 1. Select the test run and choose Activities > Enter Result. The Enter Result dialog box opens.
297
En t e r in g Ove r al l Te st Ru n Re su l t s
2. Select an Enter Result By user. This field defaults to the logged in user. 3. The Date defaults to the current date and time. You can enter another date and time. 4. Select the Resulting State to indicate which workflow state the test run moves to next.
n n n
Select Passed if the expected results and actual results match and the test run passes. Select Failed if the expected results and actual results do not match and the test run fails. Select Result Unclear (Needs Review) if you are not sure if the test run passed or failed based on the expected and actual results. This indicates that the results need further review.
5. Enter the Actual Effort in hours to perform the test. This information can help with future planning and metrics. 6. Enter any Notes. It is helpful to provide more information about the testing results. 7. Click OK. The test run status changes to the resulting state you selected.
Passing test runs

After you perform a test run, you can enter the Pass event to pass and close the test run without entering additional results information. Note: If you want to enter additional results, use the Enter Results event. See Entering Overall Test Run Results, page 297. 1. Select the test run and choose Activities > Pass. The test run status changes to Passed and the test run is closed.
Failing test runs

After you perform a test run, you can enter the Fail event to fail and close the test run without entering additional results information. Note: If you want to enter additional results, use the Enter Results event. See Entering Overall Test Run Results, page 297. 1. Select the test run and choose Activities > Fail. The test run status changes to Failed and test run is closed.
298
Cr e at in g Issu e s Fr om Te st Ru n s
Indicating unclear test run results

After you perform a test run, you can enter the Unclear event to indicate the test results are not clear without entering additional results information. Note: If you want to enter additional results, use the Enter Results event. See Entering Overall Test Run Results, page 297. 1. Select the test run and choose Activities > Unclear. The test run status changes to Result Unclear (Needs Review).
Ignoring test run results

You can ignore results for Passed, Failed, or Unclear test runs and move test runs to the Closed (Ignored) state. This event allows you to exclude test runs when you view results based on workflow state in filters, reports, and other areas. For example, after you regenerate failed test runs, enter this event to move the original test runs from the Failed state to the Closed (Ignored) state. This allows you to maintain a more accurate history of failed test results and helps you determine which failed test runs need to be retested. 1. Select the test run and choose Activities > Ignore Result. The test run status changes to Closed (Ignored) and the test run is closed.
Creating Issues From Test Runs

If you use TestTrack Pro, you can create issues from test runs to report issues found during a test. The test run information is copied to the issue so other users can review the details when fixing and verifying it. 1. Click Create Issue in the Edit Test Run dialog box. The Add Issue dialog box opens. It is populated with the following test run information by default:
n n
Summary fieldIncludes the test run number, test run summary, and problem statements. Description fieldIncludes the test run number, problem statements, a note to view the Steps to Reproduce tab, and an optional note to view the Attachments tab. Steps to Reproduce tabIncludes the steps from the test run including problem statements, step notes, actual results, and references to actual result attachments. Files tabIncludes test run result and step actual result attachments. Note: Depending on the item mapping rules configured for the project, additional information may be copied from the test run. See Configuring Item Mapping Rules, page 460.
299
Vie win g Te st Ru n S t at u s
2. Make any changes. 3. Click Add when you finish entering the issue information. You are prompted to link the issue with the related test run and test case. Linking can help you view relationships between related items and manage changes to dependent items. See Linking Items, page 77. 4. Click Add Link if you want to create a link or click Do Not Link if you do not want to create a link. The issue is saved and added to the project.
Viewing Test Run Status

After test runs are generated, you can check the progress of a test run to see if it is waiting, in progress, or completed, or run scripts attached to the test run. 1. Click the Test Runs tab when you are editing a test case. The Waiting tab displays a list of generated test runs that have not been started, which are in the initial state. For example, if you use the default workflow, this tab includes test runs in the Not Started state.
300
Vie win g Te st Ru n S t at u s
2. Click the In Progress tab. This tab includes a list of in progress test runs, which are not in the initial state or in a closed state. For example, if you use the default workflow, this tab includes test runs in the In Progress or On Hold states.
3. Click the Completed tab. This tab includes a list of the completed test runs, which are in a closed state. For example, if you use the default workflow, this tab includes test runs in the Passed, Failed, Undetermined, and Failed and Regenerated states.
301
M an agin g Au t omat e d Te st s
4. Select a Filter to filter the test runs list. 5. Select a test run and click View to view it. See Viewing Test Runs, page 284. 6. Select a test run and click Edit to modify it. See Editing Test Runs, page 314. 7. Select a test run and click Delete to delete it. See Deleting test runs, page 316. 8. Select a test run and click Run Scripts to run the attached automated tests. See Running multiple automated tests, page 309. Note: You cannot run automated tests for test runs on the Completed tab. 9. Click OK to save the changes.
Managing Automated Tests

TestTrack TCM integrates seamlessly with QA Wizard Pro to support your automated testing efforts. You may also be able to integrate with other tools using the TestTrack TCM script agent. See IntegratingTestTrack TCM with Automated Testing and Scripting Tools (http://labs.seapine.com/TCMScriptAgent.php) for information. Note: To help determine test cases you may want to automate, see the Seven Questions to Ask Before Creating Automated Tests knowledgebase article (www.seapine.com/kb/questions/1103). Following are common tasks you perform to automate tests. 1. Make sure the test case is accurate and complete. 2. Create scripts based on the test case. Create scripts in QA Wizard Pro oranother scripting tool. If you use QA Wizard Pro andneed to create new scripts, you can create them from the related test case. See Creating scripts from test cases, page 303. Add scripts you want to run from TestTrack TCM toa batch file in QA Wizard Pro. 3. Attach automated tests to the test case and make sure they work.
302
Cr e at in g scr ip t s fr om t e st case s
Before you can run automated tests, you need to attach them to test cases. See Attaching automated tests to test cases, page 305. After the automated test is attached, you may want to run it from the test case to make sure it works as expected. See Confirming automated tests work, page 307. 4. Generate test runs from the test case. When test runs are generated, automated tests attached to the related test cases are automatically copied to the test runs. See Generating Test Runs, page 280. 5. Run the automated tests. To perform tests, run the automated test file from test runs. You can manually run individual or multiple automated tests or schedule them to run unattended. See Running individual automated tests from test runs, page 308. 6. View test results and attach them to test runs. Automated test status can be checked at any time. See Checking automated test status, page 311. After tests are complete, view the results and optionally attach the results report to the related test runs. See Viewing automated test results, page 312 and Attaching automated test results to test runs, page 313.
Creating scripts from test cases

If you use QA Wizard Pro, you can create scripts from steps in existing test cases. This helps save time when creating scripts and links test cases and scripts. You can use one of the following methods to create a script from a test case:
n
Follow the test case steps and record actions in the application to include in the script. The test case steps and expected results are displayed as you record the script to help you perform the correct actions. Create a basic script that only includes the steps and expected results copied from the test case. This is helpful if you want to perform other tasks in QA Wizard Pro before recording, such as deleting unnecessary script steps or populating the application repository.
Note: QA Wizard Pro 2012.0 or later must be installed on the computer running the TestTrack Client. 1. Open the test case you want to create a script from. 2. Click the Steps tab. 3. Click Create Script. QA Wizard Pro starts if it is not already running. You are prompted to open a workspace if one is not already open. The Create Automated Test Case dialog box opens.
303
Cr e at in g scr ip t s fr om t e st case s
4. Enter a Script name. The default name is Automated Test Case followed by the test case number. 5. Select a script creation method.
n
Create script from test case stepscreates a basic script with test case steps and expected results without recording. Click Create to add the script to the workspace. Record script from test case steps records a script as you perform the displayed test case steps Continue with step 6 to record the script.
6. Select the application you want to record the steps against or click New to add an application. Select Connect to running application to record against an instance of a Windows application running on the test computer. 7. If you are recording a web script, select a Browser. 8. Click Record. The applications starts. The Recording Automated Test Case toolbar opens. The test case steps and expected results are displayed.
9. Perform the steps in the application. 10. Click Done after completing each step to add the actions to the script. If you do not click Done after each step, all the recorded actions are added to the end of the script. 11. Click the Stop Recording toolbar button when you complete all the steps. The Repository Changes dialog box opens.
304
At t ach in g au t omat e d t e st s t o t e st case s
12. Click Save. The repository changes are saved and the script is created.The test case steps, recorded actions, and a hyperlink to the test case are included in the script. Test case steps are added to the script as TestCaseStep statements.
Attaching automated tests to test cases

You can attach QA Wizard Pro batch files or scripts from other tools, to test cases so they are automatically copied to test runs. You can add an existing attachment or browse for files to attach as scripts, including source code files. Note: You can attach any file as a script, but TestTrack TCM can only run scripts from QA Wizard Pro batch files. 1. Click the Files tab in the test case you want to attach the automated test to. 2. Click the Scripts tab.
305
Note: To attach files from the clipboard, copy the file you want to attach and click Paste to attach it to the test case. 3. Click Select Scripts. The Select Scripts dialog box opens. Any files already attached to the test case are displayed.
4. Attach a test if it is not already attached.

n n
Click Attach Files to locate the file. Browse for the file and click Open. Click Attach Source Code to attach a file from source control. Select the project from the SCC Projects list. Select the files you want to attach and click Add. Click OK.
5. Select the check box in the Scripts column for each file you want to add. 6. Click OK. The files are attached.
306
Tip: You can also view attached automated tests on the Attachments tab. Automated tests under source control are also displayed on the Source Code tab. 7. Click OK to save the changes.
Confirming automated tests work

You can run a QA Wizard Pro batch file from a test case to make sure it runs correctly without attaching the results. For example, you may want to run a test to make sure it passes before generating test runs for the test case. Note: Running an automated test from a test case does not generate a test run or save any test results. 1. Click the Files tab in the test case that contains the automated test. 2. Click the Scripts tab. 3. Select a file and click Run Script. You are prompted to confirm that you want to run the test. If run results exist for the test, you are prompted to delete them before the test runs. 4. Click Yes. The Script File Status dialog box opens. Information about the file and the run status is displayed. See Checking automated test status, page 311.
5. Select a test and click View Results to view the results. Tip: If the tests are not complete, the status is Undetermined and you cannot view results. 6. Select a test and click Delete to delete the results. You are prompted to confirm the deletion. 7. Click OK to close the Script File Status dialog box. Results that you viewed are automatically deleted from the Script File Status dialog box. Results are not saved with test cases. Note: You can view results for running automated tests after you close the Script File Status dialog box. See Checking automated test status, page 311.
307
Ru n n in g au t omat e d t e st s fr om t e st r u n s
Running automated tests from test runs

To perform automated tests, run test files from test runs. You can use one of the following methods to run tests:
n
Run individual automated tests and manually attach test results to test runs. See Running individual automated tests from test runs, page 308. Run multiple automated tests and automatically attach test results to test runs. See Running multiple automated tests, page 309. Schedule automated tests to run unattended. See Scheduling automated tests to run, page 310.
Running individual automated tests from test runs

You can run a single automated test attached to a test run and then manually attach the results to the test run. Note: You can also run all from one or more test runs and automatically attach the results. See Running multiple automated tests, page 309. 1. Click the Files tab in the test run that contains the automated test. 2. Click the Scripts tab. 3. Select a file and click Run Script. You are prompted to confirm that you want to run the test. If run results exist for the test, you are prompted to delete them before the test runs. 4. Click Yes. The Script File Status dialog box opens. See Checking automated test status, page 311.
5. Select a file and click View Results to view the run results. See Viewing automated test results, page 312. 6. Select a file and click Attach Results to attach the test results to the test run. See Attaching automated test results to test runs, page 313. 7. Select a file and click Delete to delete the test results. 8. Click OK to close the Script File Status dialog box. 9. Click OK save the changes.
308
Running multiple automated tests

A test run may have more than one automated test attached to it. You can run all tests attached to one or more test runs and automatically attach the results to the corresponding test runs. TestTrack TCM can automatically move the test runs to a new status based on the test results. For example, if all tests attached to a test run pass, TestTrack TCM can automatically enter the Pass event on the test run to change the status to Passed and close the test run. Note: You cannot perform other tasks while automated tests run. Only use this method to run tests unattended or in the background. 1. Select the test runs you want to run automated tests for on the Test Runs list window. 2. Choose Activities > Run Scripts. The Run Scripts dialog box opens. Tests run in the order displayed in the list.
Tip: You can also run multiple automated tests attached to a single test run from a test case. Click the Test Runs tab in the Edit Test Case dialog box. Select the test run that contains the automated tests you want to run and click Run Scripts. 3. Select Add workflow events on script result to automatically enter an event and move the test runs to a new state based on the test result. Only valid events that do not open an event dialog box are available in the lists. The Do not show the dialog box when entering this event option must be selected for the event. See Adding events, page 418.
309
4. Select Add System Comment event with the following text to add a system comment to the test run. System comments provide information about actions performed by TestTrack and are displayed on the test run Workflow tab. The default text includes the logged in user, date, and time. You can change the default text. 5. Select Stop running scripts if an error or script failure occurs to stop all tests from running if an error or failure occurs. 6. Select Lock all test runs immediately to lock the test runs when you click Run to start the tests. Each test run is automatically locked when the attached tests start running. If another user is editing the test run, the tests cannot run and an error is displayed in the Run Scripts - Results dialog box. 7. Click Run. A progress indicator opens. Click Stop to stop playback. Note: You cannot perform other tasks in TestTrack while tests are running. The Run Scripts - Results dialog box opens when the scripts finish running. The results for each test are displayed. If a test attached to a test run fails, the test run result is failed even if other tests pass.
Note: You can view the results in the related test run. See Viewing automated test results, page 312. 8. Optionally select a result from the Filter by list to filter the test runs. 9. Select a test run and click View to view it. See Viewing Test Runs, page 284. 10. Select a test run and click Edit to edit it. See Editing Test Runs, page 314.
Scheduling automated tests to run

You can schedule tests to run automatically. For example, schedule test to run at night. When you get to work in the morning, you can view the results and attach them to test runs. 1. Click the Files tab in the test run that contains the automated test. 2. Click the Scripts tab. 3. Select a test and click Schedule. The Schedule Task dialog box opens.
310
Ch e ckin g au t omat e d t e st st at u s
4. The Start date defaults to the current date. You can enter another date. 5. The Start time defaults to the current time. You can enter another time. The start time must be at least five minutes later than the current time. 6. Select Stop the task if it runs for to stop the automated test if it runs longer than the specified time. Enter the hours and minutes to run the test before the task is stopped. 7. Enter your Windows Username and Password. The username and password is required to start the task to run the tests. 8. Click OK. The task is added to the Windows Scheduled Tasks. Use the Windows Task Scheduler to view or edit the task.
Checking automated test status

You can view the status of running automated tests to check the progress or view results. For example, if you schedule tests to run at night, you can check the status in the morning. Tip: You can view the status of all automated tests run from test cases or test runs. Choose Activities > Check Automated Script Status. 1. Click the Files tab in the test case or test run that contains the automated test. 2. Click the Scripts tab. 3. Select a test and click Check Status. The Script File Status dialog box opens. Results you have not viewed for tests run from test cases or have not attached for tests run from test runs are displayed. The following information is displayed:
n n
IDTest case number the automated test is running for. Script FileAutomated test filename.
311
Vie win g au t omat e d t e st r e su l t s
n n n
StatusAutomated test run status. See Understanding automated test status, page 312. StartedDate and time the automated test started running. CompletedDate and time the automated test completed.
Note: The Result File, Script Type, Script ID, and Path columns display information required by TestTrack TCM to run automated tests. 4. Select a test and click View Results to view the results. 5. If you are checking results for a test run, select a test and click Attach Results to attach the results to the test run. See Attaching automated test results to test runs, page 313. 6. Select a test and click Delete to delete the results. You are prompted to confirm the deletion. 7. Click OK to close the Script File Status dialog box. 8. Click OK to save the changes.
Understanding automated test status

TestTrack TCM displays the automated test status before, during, and after execution. Automated tests can have the following status:
n
ScheduledTests are scheduled to start at a later time. See Scheduling automated tests to run, page 310. StartedTests are currently running. PassedTests finished running and all of them passed. FailedTests finished running but one or more tests failed. UndeterminedTests did not finish running. For example, a problem may exist with the tested application. You cannot view results for tests in an Undetermined status.
n n n n
Note: To view the status of running automated tests, choose Activities > Check Automated Script Status. See Checking automated test status, page 311.
Viewing automated test results

Automated test results are displayed in a QA Wizard Pro report that provides detailed information about each script. 1. Click the Files tab in the test run that contains the automated test.
312
At t ach in g au t omat e d t e st r e su l t s t o t e st r u n s
2. Click the Scripts tab. 3. Select the test you want to view results for. 4. Click View Results. The results report opens. 5. Click OK to close the Edit Test Run dialog box.
Attaching automated test results to test runs

After a single automated test runs, you may need to attach the results to the test run. Test results files are zipped and added to the Attachments tab in the Edit Test Run dialog box. The test result (passed, failed, or undetermined) and the results file name are also displayed in the Status column on the Scripts tab. Note: You may need to enter a workflow event to indicate the result of the test run. Individual automated tests do not automatically enter an event to change the test run workflow state. See Entering Overall Test Run Results, page 297. 1. Click the Files tab in the test run that contains the automated test. 2. Click the Scripts tab. 3. Select the test you want to attach the results for. 4. Click Check Status. The Script File Status dialog box opens. 5. Select a test. 6. Click Attach Results. The results are attached to the test run. Note: To view attached results, select the test on the Scripts tab and click View Results. You can also open the results on the Attachments tab.
Managing Test Run Links

You can link test runs to other items in the same project. Linking helps you establish relationships between items and manage changes to related items when test runs change. You can link items in a parent/child or peer relationship. Following are a few examples that illustrate the different uses for linking test runs:
n
A test case requires testing on multiple operating systems. Test runs are generated for each operating system. You can link all of the test runs together in a peer relationship so testers can view the related test runs and all of the test runs can be tracked together. Several test runs are generated for a test case. You can link the test runs to the test case in a parent/child relationship. You can select the test case as the parent and the test runs as children. This can be helpful for tracking and reporting purposes.
313
Ed it in g Te st Ru n s
The development team makes a functional design change, which is added as an issue in the TestTrack Pro project. The QA team lead is notified about the change and creates a test case to make sure the change is tested. The team lead then generates test runs and links the test runs, test case, and issue in a peer relationship. When the test runs are assigned, the tester can view the related test case and issue.
1. Click the Links tab when you are viewing or editing a test run.
2. Click Add Link to create a link. See Adding links, page 77. 3. Select a link and click View Link to view it. See Viewing links, page 80. 4. Select a link and click Edit Link to change it. See Editing links, page 81. 5. Select a link and click Diagram Links to generate a link diagram. See Diagramming links, page 79. 6. Select a link, click an item in the Link Details area, and click View Item to view the linked item. 7. Select a link, select an item in the Link Details area, and click Edit Item to edit the linked item. 8. Select a link, select an item marked as suspect in the Link Details area, and click Investigate to view the suspect dependencies. See Investigating suspect dependencies, page 83. 9. Select a link, select an item marked as suspect in the Link Details area, and click Clear Suspect to clear the suspect. See Clearing suspect items, page 84. 10. Select a link, select an item in the Link Details area, and click Mark Suspect to mark the item as suspect. See Marking Items as Suspect, page 82. 11. Select a link and click Delete Link to delete it. See Deleting links, page 81. 12. Click OK to save the changes.
Editing Test Runs

You can edit a test run to enter test results or change the information in it. See Running Tests, page 284 for information about running tests and entering results.
314
Du p l icat in g t e st r u n s
Tip: If you need to update field values for multiple test runs, use bulk field changes to quickly update multiple records simultaneously. See Updating Multiple Items, page 84. 1. Select the test run on the Test Runs list window. 2. Choose Edit > Edit Test Run. The Edit Test Run dialog box opens. Note: If another user is editing a test run, a read-only icon is displayed next to the OK button. When the user closes the test run, it is updated and becomes available for editing. 3. Click Go To Test Case to view the related test case. See Viewing Test Cases, page 319. 4. Click Create Issue to add an issue to report issues found during testing. See Creating Issues From Test Runs, page 299. 5. Click Send Email to email a user about the test case. See Emailing from TestTrack, page 73. Note: Click the Email tab to view, reply to, or delete tracked email. See Viewing tracked email, page 75, Replying to tracked email, page 76, or Deleting tracked email, page 76. 6. Click OK to save the changes. Note: If the changes impact linked or related items, you may want to mark the items as suspect. This adds a flag to the items to indicate they should be reviewed. See Marking Items as Suspect, page 82.
Duplicating test runs

If you add test runs with the same basic information, you can save time by duplicating and editing an existing test run. For example, you may want to duplicate a test run if one was not generated for testing on a supported operating system. 1. Select the test run on the Test Runs list window. 2. Choose Edit > Duplicate Test Run. The Duplicate Test Run Options dialog box opens.
315
De l e t in g t e st r u n s
3. Select Link duplicated test run with original to link the new test run with the original test run.
n n
Select a Link definition. The list includes all test run link definitions. Enter a Link comment. The comment is displayed on the test run Links tab and in link diagram.
4. Select Identify original test run in system comment to add a system comment to the Workflow tab of the new test run that indicates the original test run number and summary. 5. Select the information to copy from the original test run.
n n
Select History information to copy information from the History tab. Select File attachments to copy attachments from the Scripts and Attachments tabs. Expected result and actual result attachments are always included in duplicated test runs, even if this option is not selected. Select SCC attachments to copy attachments from the Source Code tab. Expected result and actual result attachments are always included in duplicated test runs, even if this option is not selected. 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 test run to the same folder as the original test run. Test runs are only copied to the folders you have security permissions to add test runs to.
n n n
6. Click OK. The test run is duplicated and assigned the next available test run number. 7. Modify the test run and save the changes.
Deleting test runs

1. Select the test run on the Test Runs list window. You can select more than one test run to delete. 2. Choose Edit > Delete Test Run.
316
M an agin g Te st Case an d Te st Ru n Fol d e r s
You are prompted to confirm the deletion. 3. Click Yes. The test run is deleted.
Managing Test Case and Test Run Folders

You can add test cases and test runs to folders to group them with other items. See Organizing Data with Folders, page 56. 1. Click the Folders tab when you are viewing or editing a test case or test run. Folder paths are displayed if the test case or test run is included in folders.
2. Select a folder and click Open Folder to open the folder. 3. Click Add to Folder to add the test case or test run to a folder. See Adding items to folders, page 66. 4. Select a folder and click Move to Folder to move the test case or test run to a folder. See Moving items to folders, page 66. 5. Select a folder and click Remove from Folder to remove the test case or test run from the folder. See Removing items from folders, page 69. 6. Click OK to save the changes.
Managing Test Case and Test Run Email

If email tracking is enabled, you can work with email sent from test cases and test runs. You can view, reply to, and delete tracked email. 1. Click the Email tab when you are editing or viewing a test case or test run. 2. Select an email and click View to view it. See Viewing tracked email, page 75. 3. Select an email and click Reply To to reply to it. See Replying to tracked email, page 76. 4. Select an email and click Delete to delete it. See Deleting tracked email, page 76. You can only delete email when you are editing a test case or test run. 5. Click OK to save the changes.
317
M an agin g Te st Case Lin ks
Managing Test Case Links

You can link test cases to other items in the same project. Linking helps you establish relationships between items and manage changes to related items when test cases change. You can link items in a parent/child or peer relationship. Following are a few examples that illustrate the different uses for linking test cases:
n
Six test cases are created to test a new software feature. You can link all the test cases in a peer relationship so testers can view the related test cases and all of the test cases can be tracked together. A problem is found that affects a products native client and web client. The QA team lead creates a test case that includes overview information about the change and required testing. She assigns the test case to a team member so he can add the test case details required to test each client. He creates two new test cases and then links all three test cases in a parent/child relationship. He selects the initial test case created by the QA team lead as the parent and the test cases that contain the specific testing steps as the child test cases. The development team makes a functional design change, which they add as an issue in the TestTrack Pro project. The QA team lead is notified about the design change and creates a test case to make sure the change is tested. The team lead links the issue and test case in a peer relationship and assigns the test case to a team member to write the test case steps. The team member can view information about the change in the linked issue so the steps for testing the change are complete and accurate.
1. Click the Links tab when you are viewing or editing a test case.
2. Click Add Link to create a link. See Adding links, page 77. 3. Select a link and click View Link to view it. See Viewing links, page 80. 4. Select a link and click Edit Link to change it. See Editing links, page 81. 5. Select a link and click Diagram Links to generate a link diagram. See Diagramming links, page 79. 6. Select a link, click an item in the Link Details area, and click View Item to view the linked item.
318
Vie win g Te st Case s
7. Select a link, select an item in the Link Details area, and click Edit Item to edit the linked item. 8. Select a link, select an item marked as suspect in the Link Details area, and click Investigate to view the suspect dependencies. See Investigating suspect dependencies, page 83. 9. Select a link, select an item marked as suspect in the Link Details area, and click Clear Suspect to clear the suspect. See Clearing suspect items, page 84. 10. Select a link, select an item in the Link Details area, and click Mark Suspect to mark the item as suspect. See Marking Items as Suspect, page 82. 11. Select a link and click Delete Link to delete it. See Deleting links, page 81. 12. Click Add or OK to save the changes.
Viewing Test Cases

You can view read-only test case information. You can also generate test runs, send email, and enter test case events when viewing test cases. 1. Select the test case on the Test Cases list window. 2. Choose Edit > View Test Case. The View Test Case dialog box opens. 3. Click Generate Test Runs to generate test runs. See Generating Test Runs, page 280. 4. Click Send Email to email a user about the test case. See Emailing from TestTrack, page 73. Note: Click the Email tab to view or reply to tracked email. See Viewing tracked email, page 75 and Replying to tracked email, page 76. 5. Click Edit to edit the test case. See Editing Test Cases, page 319. 6. Click OK to close the View Test Case dialog box.
Editing Test Cases

When you edit a test case, related test runs are not updated to reflect the changes. You must generate new test runs or regenerate test runs if you want to use the updated test case. Tip: If you need to update field values for multiple test cases, use bulk field changes. This allows you to quickly update multiple records simultaneously. See Updating Multiple Items, page 84. 1. Select the test case on the Test Cases list window. 2. Choose Edit > Edit Test Case. The Edit Test Case dialog box opens. Note: If another user is editing a test case, a read-only icon is displayed next to the OK button. When the user closes the test case, it is updated and becomes available for editing. 3. Make any changes. 4. Click Generate Test Runs to generate test runs for the test case. See Generating Test Runs, page 280. 5. Click Send Email to email a user about the test case. See Emailing from TestTrack, page 73.
319
Du p l icat in g t e st case s
Note: Click the Email tab to view, reply to, or delete tracked email. See Viewing tracked email, page 75, Replying to tracked email, page 76, or Deleting tracked email, page 76. 6. Click OK. Note: If the changes impact linked or related items, you may want to mark the items as suspect. This adds a flag to the items to indicate they should be reviewed. See Marking Items as Suspect, page 82.
Duplicating test cases

If you add test cases with the same basic information, you can save time by duplicating and editing an existing test case. 1. Select the test case on the Test Cases list window. 2. Choose Edit > Duplicate Test Case. The Duplicate Test Case Options dialog box opens.
3. Select Link duplicated test case with original to link the new test case with the original test case.
n n
Select a Link definition. The list includes all test case link definitions. Enter a Link comment. The comment is displayed on the test case Links tab and the link diagram.
4. Select Identify original test case in system comment to add a system comment to the Workflow tab of the new test case that indicates the original test case number and summary. 5. Select the information to copy from the original test case.
320
Assign in g t e st case n u mb e r s
n n
Select History information to copy information from the History tab. Select File attachments to copy attachments from the Scripts and Attachments tabs. Expected result attachments are always included in duplicated test cases, even if this option is not selected. Select SCC attachments to copy attachments from the Source Code tab. Expected result attachments are always included in duplicated test cases, even if this option is not selected. 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 test case to the same folder as the original test case. Test cases are only copied to the folders you have security permissions to add test cases to.
n n n
6. Click OK. The test case is duplicated and assigned the next available test case number. 7. Modify the duplicated test case and save the changes.
Assigning test case numbers

After you review deferred test cases, you can assign test case numbers to them. 1. Select the unnumbered test case on the Test Case list window. 2. Choose Activities > Assign Test Case Numbers. The test case is assigned the next available test case number.
Renumbering test cases

You can renumber test cases at any time. For example, deleting test cases may leave gaps in the test case numbers and you may want to renumber the test cases. 1. Select the test case you want to renumber. 2. Choose Activities > Renumber Test Cases. The Renumber Test Cases dialog box opens. The starting number is set to the next available number.
3. Enter a new test case number and click OK. The Renumber Test Cases dialog box closes and the test case is renumbered.
n
If the renumbered test case number is higher than the next available test case number, the next available test case number is set to one higher than the renumbered test case.
321
De l e t in g t e st case s
If you renumber the entire test case list, the next available test case number must be set to one greater than the highest test case number.
Deleting test cases

You can delete test cases that are no longer used or needed for historical purposes. Related test runs can also be deleted when you delete a test case. Note: If the test case you are deleting is shared with another test case, the link between the test cases is broken. You need to manually remove the reference to the deleted test case in the test case it is shared with. 1. Select the test case on the Test Cases list window. You can select more than one test case to delete. 2. Choose Edit > Delete Test Case. You are prompted to confirm the deletion. Note: If the test case has related test runs, you are prompted to confirm if you want to delete the related test runs or only delete the test case. 3. Click Yes. The test case is deleted.
322
Managing Security
Security groups control security and the TestTrack commands users in the group can access. Protect your data integrity and security by creating groups for all security levels. You can configure projects to provide as much or as little access as needed. TestTrack includes the following security options:
n n n n n n
Passwords limit access to projects. Command security limits the commands a group of users can perform. Field security limits who can enter or edit field data. Record security limits the records that are visible to each security group. Advanced logging tracks who changed fields and states and when changes are made. Server logging records unusual activity, critical, and non-critical system issues.
Managing Security Groups

A security group is a collection of users who share responsibilities and perform similar tasks. Access to TestTrack functions, such as adding a test case or using SCC integration, is controlled by group security. Users must be assigned to a security group before they can work with TestTrack projects. When you set up a project, create the security groups first. This lets you create a security structure for users. You can create an unlimited number of security groups and levels. Security determines what projects users can access, what their view and edit rights are (on a per-field level), and what they can do at each stage of the workflow. See Adding security groups, page 324. Before you start creating security groups, you may find it helpful to list the types of users in the project and their security restrictions. You can add an unlimited number of security groups and make their security levels as general or as command-specific as you need. The following example provides security based on group levels: Group Name Level 1 Level 2 Level 3 Level 4 Security Level Low Medium High Highest Commands View View, Add View, Add, Edit View, Add, Edit, Delete
Or, use the same structure to name the security groups according to job description: Group Technical Writer Engineer QA Tester Manager Security Level Low Medium High Highest Commands View View, Add View, Add, Edit View, Add, Edit, Delete
323
Ad d in g se cu r it y gr ou p s
Note: You do not need to create security groups if you want all users to have access to all commands. An Administration group is automatically created when a project is created. This security group has access to every command. Simply add the users to this default security group.
Command security
Command security limits the commands users can access. Most of the command security options are intuitive. For example, the Add Customer command determines if a user can add customers. See Security Commands, page 565 for the available command security options and the commands they provide access to. Note: Edit Security Groups and See Security Tabs security must be enabled for at least one security group. You cannot remove yourself as a user from a security group with these commands enabled because it could result in no users with permissions to perform administrative tasks.
Field security
Field security affects records and events and restricts users ability to view, add, and edit data. Three types of field security can be assigned: Read/Write, Read Only, and Hidden. Users with read/write access can enter and edit information. Users with read only access can only view the information. Users with hidden access cannot view the fields or any information. You can also set field security for add and edit scenarios. For example, you can assign a restricted security group read/write Add privileges for the Type field, but assign this group read only Edit privileges for the Type field. Users can enter information in the Type field when they add records but cannot make any changes if they edit records. Security can be assigned to the following field categories: General, issue Found By fields, event fields, link fields, email fields, system comment fields, and custom fields.
n
Field security cannot be applied to the following areas: email templates, SoloSubmit, SoloBug, XML import/export, and text file import/export. System-generated fields cannot be assigned read/write security. This includes the following fields: record number, record status, has attachments, has workaround, date created, created by, creation method, date last modified, last modified by, found by group, found by company, how many, and has release notes. A field can be represented by an edit box, check box, radio button, or a list box. Remember, setting field security affects all field types.
Adding security groups

1. Click Add on the Security Groups list window. The Add Security Group dialog box opens with the Users in Group category selected.
324
Ad d in g se cu r it y gr ou p s
2. Enter a Name and Description. These fields are required. 3. Select any display options to limit the users and customers in the Available Users list. 4. Select the users you want to add from the Available Users list. 5. Click Add to add the selected users to the security group. Note: Click Find User to search for users or customers to add to the group. See Finding users and customers, page 39. 6. Optionally select Include users in pop-up menus or Include customers in pop-up menus to display the selected users or customers in pop-up menu fields. This option is intended to limit pop-up fields that represent an action, such as entering an issue or generating a test run. However, all user and customer names are displayed in the Found By/Reported By field even if this option is not enabled. For example, if a customer calls and reports a bug, the customer is included in the Found By list. 7. Set Command Security for each category. All commands are enabled by default. Make sure you set security for each category.
n
When you set Issues, Requirements, Requirement Documents, Test Cases, or Test Runs security, you can also configure the group to only work with records that pass a filter and to only work with records they created. By default, security for requirements is the same for all requirement types. You can override the default setting and set different security for each requirement type. Select a requirement type from the list, clear the Use values from <All Requirement Types>, and set the command security for the type. An asterisk indicates the requirement types that do not use the default settings. Security for requirement events applies to all requirement types.
8. Set Field Security for each category.
325
Vie win g se cu r it y gr ou p s
Field security defaults to full security when a new security group or project is created. By default, users can view or edit every issue, requirement, requirement document, test case, and test run field. Make sure you set Add and Edit privileges for all field categories. By default, security for requirements is the same for all requirement types. You can override the default setting and set different security for each requirement type. Select a requirement type from the list, clear the Use values from <All Requirement Types> option, and set field security for the type. An asterisk indicates the requirement types that do not use the default settings. Security for requirement events applies to all requirement types.
9. Select the Notes category and enter any information about the security group. You may want to enter information about why the group was created or the types of users in the group. 10. Click Add. The security group is created.
Viewing security groups

1. Select the security group on the Security Groups list window. 2. Choose Edit > View Security Group or click View on the Security Groups list window. The read-only View Security Group dialog box opens. 3. Click Edit to edit the security group. See Editing security groups, page 326. 4. Click OK when you are finished.
Editing security groups

1. Select the security group on the Security Groups list window.
326
Cr e at in g se cu r it y gr ou p comp ar ison r e p or t s
2. Choose Edit > Edit Security Group. The Edit Security Group dialog box opens. 3. Make any changes and click OK. The changes are saved. Note: At least one security group must have the Edit Security Groups and See Security Tabs commands enabled. You cannot remove yourself from a security group with these commands enabled.
Creating security group comparison reports

Security group comparison reports include detailed information about command and field security permissions for groups. These reports are helpful for comparing permissions between multiple groups and identifying any changes. For example, if a user in the QA Interns security group cannot modify the issue Product field, you can run comparison report, review the permissions for other groups that can change the field, and then make the appropriate changes to provide access to edit the field. 1. Choose Create > Report. The Select Report Type dialog box opens. 2. Select Detail and click OK. The Add Detail Report dialog box opens. 3. Enter a Name and Title. The title appears at the top of the report when it is viewed or printed. 4. Select a Share option.
n n n n n
5. On the Report On tab, select Security Groups from the Report contains list.
327
Cr e at in g se cu r it y gr ou p comp ar ison r e p or t s
6. Select the security groups to include in the report.

n n
All Security Groups includes all security groups. Selected Security Groups includes only the selected security groups.
7. Click the Options tab and select report display options.

n n
Select SecurityGroupComparisonReport.xslt from the Stylesheet list. Optionally select Print items on separate pages to print each item in the report on a separate page.
9. Click Apply to save the report and then click the Preview button. A progress indicator opens. Click Cancel if you want to cancel the report generation. 10. The report opens in a new browser window and displays information in the following areas.
328
Hid in g fie l d s
Command Security displays security commands a security group can and cannot access. See Security Commands, page 565 for a list of security commands. Field Security displays permissions for viewing, adding, and editing fields. Tip: To collapse the Command Security or Field Security areas, click Collapse Section.
11. Optionally customize the report content.

n n n n
Click the arrow next to a section name to expand or collapse the section. Click and drag column headings to rearrange them. Right-click a column heading and select the heading name to display or hide. Click a row to select it. To select more than one row, press and hold Ctrl and click each row. To select a range of rows, click the first row, press and hold Shift, and then click the last row. Double-click a cell in a security group column to add a flag. Double-click a cell with a flag to add a checkmark. Double-click a cell with a checkmark to clear the icon. In the Field Security sections, click the following links to highlight specific permissions.
n n n n
H = Hidden highlights hidden fields. RO = Read Only highlights read-only fields. R/W = Read/Write highlights read/write fields. * = Overridden highlights fields with permissions that override the default value. For example, the QAgroup has read-only permission for the Summary field for all requirement types. The group has read/write permission for the Summary field for business requirements. The read/write permission overrides the read-only permission and is displayed as Overridden in the report.
12. Depending on the browser, you can print the report, export the data, save the report to view later, or simply close the report after you view it.
Hiding fields
Fields may contain sensitive data that you do not want some users to see. You can set fields as hidden for a security group to prevent users in the group from viewing the field. You may also want to hide fields that you do not use. 1. Choose View > Security Groups. The Security Groups list window opens. 2. Select a security group and click Edit. The Edit Security Group dialog box opens. 3. Select a record type from the Field Security category. 4. Select the field you want to hide in the Add Privileges or Edit Privileges list. You can hide fields in Add dialog boxes, Edit dialog boxes, or both. 5. Click Hidden. The field is hidden.
329
Du p l icat in g se cu r it y gr ou p s
Duplicating security groups

If you are adding security groups with the same basic information, you can save time by duplicating and editing an existing group. 1. Select the security group on the Security Groups list window. 2. Choose Edit > Duplicate Security Group. The group is duplicated. A number is added to the end of the group name. 3. Modify the duplicated group and save the changes.
Deleting security groups

1. Select the security group on the Security Groups list window. 2. Choose Edit > Delete Security Group. You are prompted to confirm the deletion. 3. Click Yes. The security group is deleted.
Managing Users and Customers

TestTrack includes users and customers. Customers are generally the end-users of your products or services. Unlike users, customers usually do not have access to the project and are created for tracking purposes.
Adding users
Global users, which are created in the Seapine License Server or in TestTrack, have usernames and passwords and can generally access projects. Local users, which are created in TestTrack or when bugs are submitted via SoloSubmit or SoloBug, are usually created for tracking purposes. 1. Choose Create > User. The Add User dialog box opens with the Info tab selected.
330
Ad d in g u se r s
2. Select a User Type. Tip: Add the Type column to the Users list window to quickly view local and global users. 3. Enter the users First Name and Last Name. 4. Enter a Username if you are creating a global user. 5. Enter the information on the Info tab.
n n n n
Select a Security Group. Enter the user Phone Numbers. Select an email type and enter the user Email Address. Enter and confirm a user Password if you are creating a global user. Users can change their passwords when they log in.
6. Click the Notify tab to configure email notifications.

n n n
Click Add to create a notification rule. See Adding user notification rules, page 47. Select a rule and click Edit to change it. See Editing user notification rules, page 48. Select a rule and click Inactivate to inactivate it. See Inactivating user notification rules, page 49. Select a rule and click Delete to delete it. See Deleting user notification rules, page 49.
331
Ad d in g u se r s
7. Click the License tab and select a license for the global user. All fields are disabled if you are adding a local user. 8. Click the Address tab to enter the address and select the company, division, and department. If you have a large number of users, setting the Company, Division, and Department fields can help you group users. You can enter or select values in these fields. If you enter a value, it is saved and can be selected for other users and customers in the project. You can enter up to 64 characters. The Division field values are based on the selected Company value. The Department field values are based on the selected Division value.
Note: You can search and create filters based on the Company, Division, and Department fields. 9. Click the Notes tab and enter notes about the user. 10. Click the CPU tab to enter the CPU information. This information can help your support department troubleshoot any bugs the user reports. 11. Click the Peripherals tab to enter the peripherals information. This information can help your support department troubleshoot any bugs the user reports. 12. Click the Display Settings tab to limit the information displayed on list windows. Select a list window then add or remove columns. You can also select a filter for list windows. When the user opens the list window, it only includes records that pass the filter. This allows you to restrict the records users can access.
332
Ad d in g cu st ome r s
Tip: Select a column and click Top, Move Up, Move Down, or Bottom to change the order. 13. Skip the Statistics tab. This read-only tab contains user statistical information. 14. Click Add. The user is added.
Adding customers
Global customers, which are created in the Seapine License Server or in TestTrack, have usernames and passwords and can generally access projects. Local customers, which are created in TestTrack or when bugs are submitted via SoloSubmit or SoloBug, are usually created for tracking purposes. 1. Click Add on the Customers list window. The Add Customer dialog box opens.
333
2. Select a User Type. Tip: Add the Type column to the Customers list window to quickly view local and global customers. 3. Enter a First Name and Last Name. 4. Enter a Username if you are creating a global customer. 5. Enter the information on the Info tab.
n n n n
Select a Security Group for the customer. Enter the customer Phone Numbers. Select an email type and enter the customer Email Address. Enter and confirm a Password if you are creating a global customer. Customers can change their passwords when they log in.
6. Click the Notify tab to select email notification options.

n n n
Click Add to create a notification rule. See Adding user notification rules, page 47. Select a rule and click Edit to change it. See Editing user notification rules, page 48. Select a rule and click Inactivate to inactivate it. See Inactivating user notification rules, page 49. Select a rule and click Delete to delete it. See Deleting user notification rules, page 49.
334
7. Optionally click the License tab to select a license for the customer. All fields are disabled if you are adding a local customer. Only assign a license if you want the customer to have access to TestTrack projects. 8. Click the Address tab to enter the address and select the company, division, and department. If you have a large number of customers, setting the Company, Division, and Department fields can help you group customers. You can enter or select values in these fields. If you enter a value, it is saved and can be selected for other users and customers in the project. You can enter up to 64 characters. The Division field values are based on the selected Company value. The Department field values are based on the selected Division value.
Note: You can search and create filters based on the Company, Division, and Department fields. 9. Click the Notes tab and enter any notes about the customer. 10. Click the CPU tab to enter the CPU information. This information can help your support department troubleshoot bugs the customer reports. 11. Click the Peripherals tab to enter the peripherals information. This information can help your support department troubleshoot bugs the customer reports. 12. If you are creating a global customer, click the Display Settings tab to limit the information displayed on list windows. Select a list window then add or remove columns. You can also select a filter for list windows. When the customer opens the list window, it only includes records that pass the filter. This allows you to restrict the records customers can access.
335
Re t r ie vin g gl ob al u se r s
13. Skip the Statistics tab. This read-only tab contains statistical customer statistical information. 14. Skip the History tab. This read-only tab contains information about issues the customer reported. 15. Click Add. The customer is added.
Retrieving global users

Global users that are created using the Seapine License Server Admin Utility can be retrieved for use with TestTrack. If the user is assigned a named or floating license, they can also log in and work with TestTrack. 1. Click Retrieve Global on the Users list window. The Retrieve Global User dialog box opens.
2. Select the users you want to add to the current project. 3. Click Add. The global users are added to the project.
336
Re t r ie vin g gl ob al cu st ome r s
Retrieving global customers

Global customers that are created using the Seapine License Server Admin Utility can be retrieved for use with TestTrack. 1. Choose Edit > Retrieve Global Customer. The Retrieve Global Customer dialog box opens.
2. Select the customers you want to add to the project. 3. Click Add. The global customers are added to the project.
Promoting users
You can promote users to the Seapine License Server, which makes them available to all projects. The users demographic information is also moved to the Seapine License Server. 1. Select the user on the Users list window. 2. Choose Edit > Promote User or click Promote on the Users list window. The Promote to Global User dialog box opens.
3. Select a Promote As user.
337
P r omot in g cu st ome r s
You can create a global user or you can use an existing Seapine License Server user record. If the local users first and last name matches an existing global user, that user is selected as the Promote As user. For example, a global user named Joseph User is created. A local user named Joe User is also created. These are the same user with a different first name. Joe User can be promoted as Joseph User. The local user information is discarded and replaced with the global user information. 4. Enter a Username. 5. Click OK. The user is promoted.
Promoting customers
You can promote local customers to the Seapine License Server, which makes them available to all projects. The customers demographic information is also moved to the Seapine License Server. When you promote a customer, you can create a global customer or use an existing Seapine License Server customer record. 1. Select the customer on the Customers list window. 2. Choose Edit > Promote Customer or click Promote on the Customers list window. The Promote to Global Customer dialog box opens.
3. Select a Promote As customer. If the customers first and last names match an existing global customer, the matching customer is automatically selected as the Promote As customer. The customer can also be promoted as a new global customer. For example, a global customer named Anna Customer is created. A local customer named AnnaV Customer is also created. These are the same customer with a different first name. AnnaV Customer can be promoted as Anna Customer. The local customer information is discarded and replaced with the global customer information. 4. Enter a Username. 5. Click OK. The customer is promoted.
338
Vie win g u se r s
Viewing users
1. Select the user on the Users list window. 2. Choose Edit > View Users or click View on the Users list window. The read-only View User dialog box opens. Click the tabs to view the user information. 3. Click Edit to edit the user. See Editing users, page 339. 4. Click OK to close the View User dialog box.
Viewing customers
1. Select the customer on the Customers list window. 2. Choose Edit > View Customer or click View. The read-only View Customer dialog box opens. Click the tabs to view the customer information. 3. Click Edit to edit the customer. See Editing customers, page 339. 4. Click OK to close the View Customer dialog box.
Editing users
1. Select the user on the Users list window. Click Find to search for the user you want to edit. See Finding users and customers, page 39. 2. Choose Edit > Edit Users. The Edit User dialog box opens. 3. Make any changes. If you use LDAP, information on the Info and Address tabs cannot be edited in TestTrack. 4. Click OK. The changes are saved. Note: If your company requires electronic signatures, uses LDAP, and uses an alternative form of login (e.g., swipe cards), you must enter an electronic signature password for each user.
Editing customers
1. Select the customer on the Customers list window. Click Find to search for the customer you want to edit. See Finding users and customers, page 39. 2. Choose Edit > Edit Customer. The Edit Customer dialog box opens. 3. Make any changes. If you use LDAP, information on the Info and Address tabs cannot be edited in TestTrack.
339
Du p l icat in g u se r s
4. Click OK. The changes are saved. Note: If your company requires electronic signatures, uses LDAP, and uses an alternative form of login (e.g., swipe cards), you must enter an electronic signature password for each customer.
Duplicating users
If you are adding users with the same basic information, you can save time by duplicating and editing a user. 1. Select the user on the Users list window. 2. Choose Edit > Duplicate User. The user is duplicated and a number is added to the end of the users last name. For example, if you duplicate Jane User, a duplicate user is named Jane User1. 3. Edit the duplicated user and save the changes.
Duplicating customers
If you are adding customers with the same basic information, you can save time by duplicating an existing customer. 1. Select the customer on the Customers list window. 2. Choose Edit > Duplicate Customer. The customer is duplicated and a number is added to the users last name. 3. Edit the duplicated customer and save the changes.
Inactivating users
Instead of deleting a user, you can inactivate a user to save the historic information. Inactive users cannot log in, receive email via TestTrack, or be assigned records. Window and tab display settings for inactive users are deleted from the TestTrack Server. 1. Select the user on the Users list window. 2. Choose Edit > Inactivate User. You are prompted to confirm the inactivation. 3. Click Yes. The user is inactivated. Note: To activate an inactive user, select the user and click Activate.
340
In act ivat in g cu st ome r s
Inactivating customers
Inactivate a customer to save the historic information. Inactive customers cannot log in to TestTrack, receive email via TestTrack, or be assigned records. Window and tab display settings for inactive customers are deleted from the TestTrack Server. 1. Select the customer on the Customers list window. 2. Choose Edit > Inactivate Customer. You are prompted to confirm the inactivation. 3. Click Yes. The customer is inactivated. Note: To activate an inactive customer, select the customer and click Activate.
Making a user a customer

1. Select the user you want to convert to a customer on the Users list window. You can select more than one user at a time. 2. Choose Edit > Make User a Customer. The user is transferred to the customers list.
Making a customer a user

1. Select the customer on the Customers list window. 2. Choose Edit > Make Customer a User. The customer is transferred to the users list.
Deleting users
You can delete local TestTrack users. Historic information is deleted with the user record. Inactivate the user if you need to retain historic information. See Inactivating users, page 340. Note: Global users cannot be deleted from TestTrack. Global users can be disassociated from the current project, resulting in lost historic information. 1. Select the user on the Users list window. 2. Choose Edit > Delete User. You are prompted to confirm the deletion. 3. Click Yes. The user is deleted.
341
De l e t in g cu st ome r s
Deleting customers
You can delete local TestTrack customers. Historic information is deleted with the customer record. Inactivate the customer if you need to retain historic information. See Inactivating customers, page 341. 1. Select the customer on the Customers list window. 2. Choose Edit > Delete Customer. You are prompted to confirm the deletion. 3. Click Yes. The customer is deleted.
342
Configuring TestTrack
TestTrack includes local, user, and project options. Users can generally set their own local and user options. An administrator or another high-level user is usually responsible for setting the TestTrack project options.
Setting Local Options

You can set local options that apply to all the TestTrack projects you log in to. You can configure the following options: General, Stylesheets, Help and Browser Settings, View File, Formatting Text, Live Charts, and TestTrack TCM.
Setting general local options

1. Choose Tools > Local Options then select the General category.
2. Select Always login to this server with this username and password to automatically log in to the selected server. 3. Select Always login to this project to automatically log in to the selected project when TestTrack starts. 4. Select Allow multiple instances of this application to allow more than one instance of TestTrack to run on your computer. 5. Enter the TestTrack TCM Automated Scripts Directory path or click Browse to select it. Scripts are run from the ScheduledScripts directory in the TestTrack TCM application directory on Windows and the Seapine home directory on Unix by default. Change the directory if you do not have permission to modify these directories or you want to run scripts from a different location. 6. Enter the number of megabytes to Limit memory use to when importing and exporting TestTrack RM requirement documents to and from Microsoft Word, and opening TestTrack items in Microsoft Excel.
343
S e t t in g st yl e sh e e t op t ion s
This option controls the amount of memory the Java Virtual Machine (JVM) can use. You may need to increase the memory if Java errors occur when adding TestTrack items to Word or Excel format. The default is 512 MB. 7. Select Group workflow events in a sub-menu to group events in the Activities menu and shortcut menus in a Workflow Events sub-menu. You may want to select this option if your organization's workflows have a large number of events to make the menus more manageable. 8. Click OK to save the changes.
Setting stylesheet options

You can specify the default stylesheet you want to use when printing from list windows. See List window report stylesheets, page 562. 1. Choose Tools > Local Options then select the Stylesheets category.
2. Select a Report Type. Each report type corresponds to a list window. For example, the Filter View Detail Report prints a detail report for all filters in the project. 3. Select a Default Stylesheet for the selected report or click Browse to use a custom stylesheet. See List window report stylesheets, page 562. 4. Click OK to save the changes.
Setting local help and browser paths

If you are using the TestTrack Client on Linux, you must set both the browser and help directory paths. This category is not available if you are using TestTrack on Windows or Mac OS X. 1. Choose Tools > Local Options then select the Help and Browser Settings category.
344
S e t t in g vie w fil e op t ion s
2. Enter the Browser Path or click Browse to select it. 3. Enter the Help Directory path or click Browse to select it. 4. Click OK to save the changes.
Setting view file options

You can select the applications used to view files. You can also edit the default view settings or add settings for specific file types. 1. Choose Tools > Local Options then select the View File category.
2. Click Add. The View File Settings dialog box opens.
3. Enter the File extensions you want to associate with the application. The extension must start with an asterisk followed by a period (*.). Separate extensions with a semicolon. 4. Select an Open files with option.
n n n
Choose Internal viewer to use the internal viewer. Choose Associated application to launch the associated application. (Windows/Mac only) Choose Selected application then click Browse to select a specific application.
5. Click OK to save the changes. Note: To edit or delete view file options, select the file type and click Edit or Delete.
345
S e t t in g for mat t in g op t ion s
Setting formatting options

You can specify the behavior of the text formatting toolbar and the default width of the Specification Document window. 1. Choose Tools > Local Options then select the Formatting category.
2. Select a Formatting Toolbar option. See Formatting text, page 49.

n
Show formatting toolbar when text field is active only displays the formatting toolbar when the cursor is in a text field. Always show formatting toolbar in text fields always displays the formatting toolbar in text fields. Never show formatting toolbar in text fields always hides the formatting toolbar in text fields.
3. Enter the Specification Document Width Defaults.

n n
Enter the Page Width to display text in before it wraps to the next line. The default is 600 pixels. Enter the Left Margin to indent text relative to the first column in the detail area. The default is 0. Note: If the Specification Document window is open, you need to close and reopen the window before the defaults are applied.
Setting live chart options

You can specify the font used in live charts. See Viewing Live Charts, page 71. 1. Choose Tools > Local Options then select the Live Charts category.
2. Select a Chart font.
346
S e t t in g Te st Tr ack TCM op t ion s
Setting TestTrack TCM options

You can specify if the next step or comment is automatically displayed after you enter a result on a test run step. This category is only available if you are logged in using TestTrack TCM and you are using the test run detail grid view. 1. Choose Tools > Local Options then select the TestTrack TCM category.
2. Select Always move to the next step after entering a result to automatically move to the next step or comment after entering a step result. 3. Click OK to save the changes.
Setting User Options

You can configure the following user options to customize TestTrack.
n n
General options including application notifications and window behavior Window display options including text formats used as indicators of status or change and the visibility of the Overview tab List window views User notification rules Words included in the TestTrack dictionary Spell check settings and dictionary options
n n n n
Setting general user options

1. Choose Tools > User Options then select the General category.
347
S e t t in g d isp l ay op t ion s
2. Select any Notification options. TestTrack can play a sound or open a dialog box to notify you of assignments. 3. Select a Double-clicking on items option. This option is applied to records displayed in list windows. 4. Click OK to save the changes.
Setting add multiple items options

1. Choose Tools > User Options then select the Add category.
2. Select an Adding Multiple Records option for each TestTrack item type. These options affect how the Add Record dialog box behaves after you save a new record.
n
Select Set all fields to default values to reset the Add Record dialog box fields to the default values. Select Retain pop-up menu values but set other fields to their default values to retain the values you selected for pop-up menu fields and reset all other fields. Select Close the Add Item window to automatically close the Add Item window.
Setting display options

1. Choose Tools > User Options then select the Display category.
348
2. Select a Display names as option. Names can be displayed in First/Middle/Last or Last/First/Middle order. 3. Select a Status option. You can display the status only or the status and assignment information. 4. Select any Display options.
n
Select Gray out closed records if you want closed records to appear dimmed on list windows. Setting this option can help you quickly scan for closed records. Select Warn me when values are changed due to field relationship rules to display a warning if you change a value that affects field relationship rules. Select Always display tab bar on list windows to display tabs at the top of list windows.
5. Select a Client Issue Window Layout option. This option does not apply to TestTrack Web. This option determines how the Found by, Reproduce, Computer Config, and Attachments information is displayed in the TestTrack Client.
n n
Select Vertical tab view to display the information on individual mini tabs. Select Single page view to display all of the information on a single page without tabs.
Setting differences display options

You can specify how added and removed text is displayed in requirement and requirement document differences and change reports. 1. Choose Tools > User Options then select the Differences category.
349
2. Select any Added Text options to set the text color and format used to indicate added text. Select a color from the list or click the color button to choose a color. 3. Select any Removed Text options to set the text color and format used to indicate removed text. 4. Click OK to save the changes.
Setting overview tab options

1. Choose Tools > User Options then select the Overview Tab category.
2. Select an Overview Tab to hide it. For more information about the overview tabs, see Using the Overview tab, page 12. 3. Click OK to save the changes.
Setting search options

You can specify how text is displayed when type ahead search results are found and the color of filtered list window columns. 1. Choose Tools > User Options then select Search from the Display category.
350
S e t t in g l ist win d ow vie w op t ion s
2. Select any Type Ahead options to set the text color and format. Select a color from the list or click the color button to choose a color. 3. Select a Column Filters color. Column headers are displayed in the selected color when column filters are applied. 4. Click OK to save the changes.
Setting list window view options

You can edit or delete user-defined list window views. See Creating User-Defined Views, page 28. 1. Choose Tools > User Options then select the Views category.
2. Select a List Window. The views for the selected list window are displayed. 3. Select a view and click Edit to change it. See Editing user-defined views, page 29. 4. Select a view and click Delete to delete it. See Deleting user-defined views, page 29. 5. Click OK to save the changes.
Setting dictionary options

TestTrack includes a spelling checker. You can specify which main dictionary you want to use and add words to it. 1. Choose Tools > User Options then select the Dictionary category.
351
S e t t in g d ict ion ar y op t ion s
2. Select a Main Dictionary. The spelling checker includes American English, British English, and Canadian English dictionaries. Additional dictionaries can be downloaded from Seapines web site at: www.seapine.com/ttpresources.php#dictionary 3. Click Add to add a word to the dictionary. See Adding dictionary words, page 352. 4. Select a word and click Edit to change it. See Editing dictionary words, page 352. 5. Select a word and click Delete to delete it. See Deleting dictionary words, page 352. 6. Click OK to save the changes.
Adding dictionary words

You can add custom words to the dictionary, such as product names, acronyms, and other custom words that are not found in the main dictionary. 1. Choose Tools > User Options then select the Dictionary category. 2. Click Add to add a word to the dictionary. The Add Word dialog box opens. 3. Enter the word and click OK. The word is added. You can also add words to your user dictionary while you are checking spelling. See Using spell check, page 52. 4. Click OK to save the changes.
Editing dictionary words

1. Choose Tools > User Options then select the Dictionary category. 2. Select a word and click Edit to change it. 3. Enter the new spelling. 4. Click OK to save the changes.
Deleting dictionary words

1. Choose Tools > User Options then select the Dictionary category.
352
S e t t in g sp e l l ch e ck op t ion s
2. Select a word and click Delete. You are prompted to confirm the deletion. 3. Click Yes. The word is deleted.
Setting spell check options

You can select the options that are used when spell checking. 1. Choose Tools > User Options then select the Spell Check category.
2. Select the options you want the spelling checker to use. 3. Click OK to save the changes.
Changing your password

If you do not use single sign-on, you may be able to change your TestTrack password. Note: LDAP users cannot change their passwords in TestTrack. The password must be changed in LDAP. Ask your TestTrack administrator for help. 1. Choose Tools > Change Password. The Change Password dialog box opens.
2. Enter your current password and click OK.
353
Lockin g P r oje ct s
You are prompted to enter a new password. 3. Enter a new password and click OK. You are prompted to verify the new password. 4. Retype the password and click OK. The new password is saved.
Locking Projects
You can lock a project to perform maintenance or ensure users cannot log in while you make changes. 1. Choose Tools > Administration > Lock Project. The project is locked. If you need to log out users, see Logging out users, page 354. 2. To unlock a project, choose Tools > Administration > Unlock Project. The project is unlocked.
Viewing logged in users

You can view the users who are currently logged in to the project and information about the session activity. 1. Choose View > Show Logged In Users. The Logged In Users dialog box opens.
2. To log out a user to perform maintenance or other changes, select a user and click Log Out User. When you log out users, they are notified that their session was dropped by an administrator. See Logging out users, page 354. 3. Click Close to close the dialog box.
Logging out users

You can log out users to perform maintenance or make other changes that require users to be logged out. You can also lock the project for maintenance. See Locking Projects, page 354. 1. Choose View > Show Logged In Users. 2. Select the user you want to log out. To select more than one user, Ctrl+click each user.
354
Con figu r in g P r oje ct s
3. Click Log out users. The user is logged out and the dialog box closes. When you log out users, they are notified that their session was dropped by an administrator.
Configuring Projects
A TestTrack project contains all the information you track including issues, requirements, requirement documents, test cases, test runs, security groups, users, customers, filters, test configurations, and workbook tasks. After projects are created using the server admin utility, the administrator or another high-level user needs to configure project options.
Setting general project options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens with the General category selected.
2. Enter a Project name and Description. 3. Select any Login Options to give TestTrack Pro, TestTrack RM, and TestTrack TCM users access to the project. 4. Select any Workflow Options.
n
Select Show inactive states and events in reports, filters, list windows, etc. to display inactive states and events in the Add/Edit Report dialog box, the filter Restrictions dialog box, and
355
S e t t in g cl ie n t op t ion s
the list window column shortcut menu.

n
Select Only show active events in the activities menu and workflow toolbar to display active events in the activities menu and events toolbar. Only the events that can be entered for the current records are displayed. Select this option if there are a large number of events in your workflow or you want to decrease user confusion. This option also applies to the TestTrack Web workflow links. Select Generate system comments for automation rules to add system comments for automation rules to the TestTrack Server. Automated systems comments take up additional storage space on the server, which will result in slower performance. Disabling this option does not stop the generation of all system comments, such as comments for escalation rules marked to be applied once per item, but it will substantially decrease the number of comments saved to the server. Note: If this option is enabled, system comments are never generated for escalation rules that recalculate field values.
5. Select Enable stamping to allow users to insert stamps in multi-line text fields, such as the issue description. Stamps help users identify comments added to fields. See Inserting stamps, page 53. Enter the Stamp format. You can enter any value or use the following field codes:
n n n
%LGDT%Current date using the long date format defined in the operating system %SHDT%Current date using the short date format defined in the operating system %USNM%Users last name, first name, and middle initial defined in TestTrack Note: To insert a field code in the Stamp Format field, select a code from the Available field codes list and click Insert.
6. Click OK to save the project options.
Setting client options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select the Client Options category.
356
S e t t in g cl ie n t op t ion s
3. Select any TestTrack Web Options.

n
Select Hide navigation buttons if no security access to hide TestTrack Web navigation buttons for commands users do not have access to. If this option is not selected, buttons are visible but disabled. Select Replace graphics if field labels are renamed to automatically replace TestTrack Web field label images. Do not select this option if you use custom images for renamed fields. Select Disable spell checking to disable spell checking in TestTrack Web. Select a Populate user and customer selection lists each time web pages load option to control how 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.
n n
4. Select any Multiple Login Options to restrict the number of times floating license users can simultaneously log in to the project based on the TestTrack product and client type. Note: When multiple logins are enabled, users must log out of TestTrack Web before closing the browser. If they do not log out, the session remains active and the floating licenses are not available until the session times out or you log out users.
357
S e t t in g fil e at t ach me n t op t ion s
5. Select Show local users and customers in assignment filter and live chart restrictions if you assign records to local users or customers and want to include them in assignment filter restrictions and user/customer field value lists in live charts. Do not select this option if you do not assign records to local users or customers. 6. Select any Overview Tab options.
n
Select Limit description to limit the number of description characters displayed on the Overview tab. Enter the maximum number of characters. Select Limit email displays to limit the number of email characters displayed on the Overview tab. Enter the maximum number of characters.
Setting file attachment options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select the File Attachments category.
3. Select any RDBMS File Attachment options. These options are only available if you are currently logged into an RDBMS project.
n
Select Store file attachments as files to store attachments as files on the TestTrack Server instead of blob files in the database. Select Store file attachments in the database when size is < xx mb to specify the maximum file size that can be stored in the database. Any attachment larger than the specified size is stored as a file on the TestTrack Server. The maximum value is 25 mb. Select Convert existing file attachments when the server is restarted to change how attachments are stored.
4. Select any Image File Attachments options.

n
Select Create thumbnails for image file attachments to generate image file attachment thumbnails. Thumbnails can be created for GIF, JPG, BMP, and PNG files. This option does not automatically display thumbnails. Users must select an image file attachment and click Show Thumbnail to view the image. Select Automatically display thumbnails to always display image file thumbnails. Select a File type for pasted or captured images. In the TestTrack Client, you can save clipboard images and screen captures as record attachments. This option determines the attachment file type (e.g., BMP, GIF).
n n
358
S e t t in g e mail op t ion s
Setting email options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select the Email category.
3. Select Enable email tracking for this project to enable email tracking. Email is tracked with the record it is sent from. Tracked email includes a cookie that uniquely identifies the TestTrack project and the record it was sent from. When a reply is sent, the email is retrieved from the email tracking account by the TestTrack Server, attached to the corresponding record, and forwarded to the user who sent the original email. Note: Email tracking must also be enabled in the TestTrack Server Admin Utility. 4. Select Enable sending of mail for this project to enable email sending. If you do not select this option, users cannot send email from TestTrack or receive email notifications. Note: Sending of email must also be enabled in the TestTrack Server Admin Utility. 5. Select an Email Notifications Return Address option.
n n
Always use the notification email account for the return address is the default option. Only use notification account if no user is logged in uses the notification account information. In general, a user is not logged in during email import, automatic SoloBug import, or when SoloSubmit is used. The notification account is used in these scenarios. Only use notification account if the logged in users email address is blank ensures an email address is available if the logged in user did not provide an email address. Enter a Notification account name. The notification account name defaults to TestTrack. You will probably want to customize the account name for your company. Enter a Notification account email address. If you do not enter an email address, your email may be rejected because some Internet providers do not accept email without a return address.
359
S e t t in g h yp e r l in k op t ion s
Setting hyperlink options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select the Hyperlinks category.
3. Enter the TestTrack CGI URL. The CGI is required to open http hyperlinks with TestTrack Web. The URL consists of the web server static address or IP address and the path to the TestTrack CGI (ttweb.exe). The CGI is installed in the web servers default CGI directory by default. Click Test URL to validate the connection. 4. Select any Controlled Email Notification Hyperlinks options to control access to hyperlinks. You can add the %NURL% field code to email templates to add a controlled hyperlink to emails. When the email is sent, the field code is replaced with a hyperlink, which logs a user into TestTrack and displays the record that caused the notification to be sent. See Configuring Notification Hyperlinks, page 475.
n n
Select Enable controlled email notification hyperlinks to enable controlled hyperlinks. Select Require recipient to login to prompt users to enter their TestTrack username and password. If this option is not selected, users are automatically logged in when they click the hyperlink. Select Provide username at login to automatically enter the username in the TestTrack login dialog box. This option is only enabled if the Require recipient to login option is selected. Users must also enter their password for authentication. Select Hyperlink can only be used once to allow users to log in once from the link. If this option is not selected, users can use the link to log in multiple times. Select Disable email hyperlink access after to specify the number of hours, days, weeks, or months the email notification hyperlink remains active.
360
S e t t in g issu e op t ion s
Note: Controlled hyperlink options only apply to the %NURL% field code. They do not control hyperlinks generated for %TTSTUDIOURL% or %HTTPURL% field codes. 5. Select Enable RSS feeds to allow filters to be published for RSS feeds. Enter the TestTrack Published Data CGI URL. The CGI is required to generate the URL used to subscribe to RSS feeds. The URL consists of the web server static address or IP address and the path to the TestTrack Published Data CGI (ttpubdata.exe), which is installed in the web servers default CGI directory by default. Click Test URL to validate the connection. 6. Click OK to save the project options.
Setting issue options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select the Issues category.
3. Select any Defer Issue Numbering options. Select a check box to automatically assign issue numbers for the corresponding option. If you do not automatically assign issue numbers, you can manually assign numbers at a later time. 4. Select the Next Number options.
n n
Set the Next issue number to any value greater than the largest existing issue number. Set the Next sequence number to a value greater than the largest sequence number. The sequence number is used when issues are submitted using SoloSubmit. The number is entered in the issues Reference field and the %SEQN% field code can be used in the Email Acknowledgement email template to provide the reference number to the submitter.
Setting send mail options

1. Choose Tools > Administration > Project Options.
361
The Project Options dialog box opens. 2. Select Send Mail from the Issues category.
3. Select any Closed Issue Notification options. These options send notifications when an issue is closed.
n
Select Send mail to issues submitters if the issue moves to a Closed state to notify the submitters of the change. Select a submitter option from the list. If an issue has multiple found by entries, email is sent to each found by user. Select Dont send notification if issue is added in a closed state if you do not want to send notifications for issues added in a closed state. Select the Email template you want to use with this notification.
4. Select an Issue Notification List Template. This template is used when notifications are sent to users or customers listed on the Email tab in the Add/Edit Issue dialog box. 5. Click OK to save the project options.
Setting import mail options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select Import Mail from the Issues category.
362
3. Select Enable importing issues via email to enable email import and then enter the email account information. Note: TestTrack cannot determine which project an email should be imported into and cannot differentiate between personal and business email.
n n n
Select the email Protocol to use to receive tracked email. You can use POP or IMAP. Enter the Host IP address or domain name. Select the SSL protocol to use to encrypt communication between the mail server and TestTrack Server. You can use the SSL 3.0, TLS 1.0, Negotiate, or STARTTLS 1.0 protocols. Select <not set> if you do not want to use a secure protocol. Enter the Port number. The default POP port is 995 if you select an SSL protocol and 110 if you do not. The default IMAP port is 993 if you select an SSL protocol and 143 if you do not. Enter the Username and Password. Leave the password field empty if a password is not required. Do not use the same username as the return email account configured in the Send Mail category. TestTrack can get stuck in a loop if an email account uses an auto-reply and you configure TestTrack to send an acknowledgment after importing mail. Click Test Connection to validate the connection to the mail server. The Connection Test Results dialog box opens. If the test connection fails, you can copy and paste the text into an email or text file and send it to your system administrator for help. Click Close to close the dialog box.
4. Enter the Time to wait for initial connection response. This is the time the TestTrack Server waits for an initial response from the email server. 5. Enter the Time to wait for other connection responses. This is the time the TestTrack Server waits for connection responses from the email server. 6. Select a Look for new emails time interval.
363
You can override the selected interval at any time by choosing File > Import > Perform Server Import. 7. Select Email an acknowledgement to the submitter to automatically send an acknowledgement. Select the Email template you want to use. 8. Select Enter next sequence number in issues reference field to automatically enter the next issue number. 9. Click OK to save the project options.
Setting SoloBug options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select SoloBug from the Issues category.
3. Select a Look for new files every time interval. 4. Select an After importing option. 5. Select Email an acknowledgement to the submitter to automatically email an acknowledgement. Select the Email template you want to use. 6. Select Enter next sequence number in issues reference field to automatically enter the next available number in the reference field. 7. Click OK to save the project options.
Setting SoloSubmit options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select the SoloSubmit category.
364
3. Select Enable entering issues via the SoloSubmit web page to enable SoloSubmit. This option is project-specific. SoloSubmit must be enabled for each project. 4. The SoloSubmit HTML page field defaults to solosubmit.htm. If you use a customized SoloSubmit HTML page, enter the file name. Make sure the HTML file is in the correct TestTrack directory on your web server. 5. Select Email an acknowledgement to the submitter to automatically send an acknowledgement. Select the Email template you want to use. 6. Select Enter next sequence number in issues reference field to automatically enter the next number in the reference field. 7. Select Enforce required field validation to ensure that values are entered for all required fields. Tip: The required field validation is not enforced for the Entered By field because users do not log in to SoloSubmit. If Entered By is a required field, issues entered via SoloSubmit cannot pass the required field validation check. 8. Select Use default values to initially populate the SoloSubmit web page with default values. When an issue is submitted via SoloSubmit there is no associated user in the project. Therefore, there are no user options to check to determine which time zone to use. The current time and date of the computer the SoloSubmit CGI is running on when the SoloSubmit page is loaded is used as the default value for date/time custom fields. 9. Select fields you do not want JavaScript to handle field relationships for on the SoloSubmit web page. You would choose not to include the JavaScript for one of the following reasons:
n
The SoloSubmit web page includes hidden fields. For example, you comment out a field you do not want the customer to see. You can delete the HTML, but the field and its values are still displayed in the JavaScript if the customer chooses View Source on the SoloSubmit web page. Choosing not to include the JavaScript resolves this issue.
365
S e t t in g t e st case op t ion s
The SoloSubmit web page is customized and you do not want to overwrite the customization. For example, you hard code a list of field values in the HTML. If you include the JavaScript your customization is overwritten. By ignoring JavaScript for the field, the hard coded list values are used.
If neither reason applies and you select a field from the list, it can result in unexpected behavior. For example, you ignore JavaScript for Component, which is a child field of Product. When SoloSubmit is accessed, Product and Component are populated with the initial values. If the user chooses a different Product, the Component values are not changed. 10. Click OK to save the project options. Remember to provide users and customers with the SoloSubmit URL. To submit bug reports or feature requests, they simply open a browser and enter the SoloSubmit URL.
Setting test case options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select the Test Cases category.
3. Select any Defer Test Case Numbering options. Select a check box to automatically assign test case numbers for the corresponding option. If you do not automatically assign numbers, you can manually assign numbers at a later time. 4. Enter the Next test case number. The value must be greater than the largest existing test case number. 5. Click OK to save the project options.
Setting test run options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select the Test Runs category.
366
S e t t in g r e q u ir e me n t op t ion s
3. Enter the Next test run number. The value must be greater than the largest existing test run number. 4. Select any Test Run Status Reporting Fields options. Test run status reporting fields, which are retrieved from the projects workflow, are displayed on the Test Runs tab of the Add, Edit, and View Test Case windows and in reports. These options are used to track the progress of test runs generated for a test case.
n
Select a Start time field. The Start time field list includes any date/time fields from the test runs workflow. Select a Due date field. The Due date field list includes any date/time fields from the test runs workflow.
Setting requirement options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select the Requirements category.
3. Select any Defer Requirement Numbering options.
367
S e t t in g r e q u ir e me n t d ocu me n t op t ion s
Select a check box to automatically assign requirement numbers for the corresponding option. If you do not automatically assign numbers, you can manually assign numbers at a later time. 4. Enter the Next requirement number. The value must be greater than the largest existing requirement number. 5. Click OK to save the project options.
Setting requirement document options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select the Requirement Documents category.
3. Select any Defer Requirement Document Numbering options. Select a check box to automatically assign requirement document numbers for the corresponding option. If you do not automatically assign numbers, you can manually assign numbers at a later time. 4. Enter the Next requirement document number. The value must be greater than the largest existing requirement number. 5. Click OK to save the project options.
Setting compliance options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select the Compliance category.
368
S e t t in g comp l ian ce op t ion s
3. Select the Maximum number of attempts before logging user out. If a user exceeds this number, the changes are discarded and the user is automatically logged out. 4. Enter a Certification and testimony message to display in the Electronic Signature dialog box. If electronic signatures are enabled, users are required to enter an electronic signature and optional reason when an item is created, modified, or deleted. This read-only message is displayed to explain the purpose of the signature, which is required for FDA Part 11.100 Subpart C Paragraph 2 compliance. 5. Click OK to save the options.
Setting item compliance options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select an item type from the Compliance category.
3. Select Enable historical information logging to log historical information.
369
Historical logging records the fields that change when an item is modified. It does not record the values that change. Changes to folders, such as items added and removed in folders and folder location changes are also recorded. Users can view what changed in an item, who made the change, and when the change was made on the item's History tab. 4. Select Enable detailed audit trail logging to enable the audit trail. Audit trail logging records the information that is modified when an item is added, edited, or deleted or when a public folder or items in a public folder change. The log is stored in its own project table and contains changed values. See Managing Audit Trails, page 477. When audit trail logging is enabled for an existing project, a record is logged the first time an item is edited and saved. When this option is enabled, the date and time is stored and logged in the audit trail. TestTrack compares the last modification date to the date and time audit trail logging was enabled. The entire record is logged if the last modification date is earlier than the date and time that audit trail logging was enabled. Note: Historical information and audit trail logging must be enabled to view change reports on the item History tab. See Viewing change reports, page 45. 5. If audit trail logging is enabled, select a Log Changes option.
n
Select Only log changes to items to only add details about changes made to items to the audit trail. If this option is selected, exported audit trail records only contain information about the fields that changed after the record was created. Select Log all item record data in the audit trail to add the entire record to the audit trail when a change is made. If this option is selected, exported audit trail records contain all item fields with data. Selecting this option is useful if you need to view the entire item when a change was made, but it uses more server storage space.
6. If audit trail logging is enabled, select any Electronic Signature options.

n
Select Electronic signatures are required to require electronic signatures when changing an item. When an item is created, modified, or deleted, the user is prompted to enter an electronic signature and an optional reason. When the item is saved, the users name, ID, and change reason are stored with the item. Note: For most users, electronic signatures are validated by comparing the password with the username and password. For single sign-on users, the electronic signature is validated through the Seapine License Server and the LDAP server. LDAP users that use an alternative form of login, such as swipe cards, must have an electronic signature password stored in their user profile to validate electronic signatures.
Select a Signature Components option. You can require users to enter their password or their username and password. Select Signature meaning is required to require users to enter a reason for changing an item. Tip: To require electronic signatures only for specific workflow events, Enable detailed audit logging must be selected and Electronic signatures are required must be cleared.
7. If you are setting options for test runs, select any enhanced compliance options. See Setting test run enhanced compliance options, page 371.
370
8. Click OK to save the options.
Setting test run enhanced compliance options

Enabling enhanced compliance for test runs can help make sure that your organization's tests meet compliance requirements, such as 21 CFR 11, and that your organization's testing process is followed. If you enable enhanced test run compliance:
n
Test runs are always generated in detail grid view, which guides testers through each step of the test run and helps testers capture additional information that is not available in grid view or free form text view, such as entering actual test results on each step and indicating the result of each step (Pass, Fail, or Undetermined). See Entering test results in the detail grid view, page 286. Existing test runs generated in grid view or free form view are not changed to detail grid view. You can enforce rules that test runs must meet before an action is performed on them. For example, you can require that all steps in a test run must pass before the overall test run result is entered. Rules are only applied to test runs generated in detail grid view.
Note: The following information uses the default terminology for test runs, such as Pass, Fail, and Undetermined for test results. Your organization may use different terminology. 1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select Test Runs from the Compliance category.
371
3. Optionally select any logging or electronic signature options. See Setting item compliance options, page 369. 4. Select Enable enhanced compliance to require all test runs to be generated in detail grid view and apply any selected rules to test runs before they are saved. 5. Select any Rules. If a test run does not pass the selected rules when it is saved or a workflow event is entered to indicate the overall test result, an error is displayed that explains why an action cannot be performed on the test run.
n
All steps must have a step result before the test run can be passed or failed requires that all test run steps have a Pass, Fail, or Undetermined result before the overall test run can be passed or failed. All steps must pass before the test run can be passed requires that all test run steps have a Pass result before the overall test run result is set to Pass.
372
S e t t in g fie l d op t ion s
The test run cannot be passed if any steps fail requires that no test run steps have a Fail result before the overall test run result is set to Pass. It does not require that all steps have a result. A problem statement is required for each step that fails requires that steps with a Fail result have a problem statement added before the test run is saved. The actual results field is required for steps that have a step result of pass or fail requires that text or an attachment is added to the Actual Results field before the step result is set as Pass or Fail. An issue must be linked to the test run if the test run fails requires that the test run is linked to an issue before the overall test run result is set to failed. This option is only available if an item mapping rule for creating issues from a test run is configured. See Configuring Item Mapping Rules, page 460.
6. Select The step result field can be set to undetermined to allow a test run step result to be set to Undetermined in addition to Pass or Fail. Note: Clearing this option does not automatically remove the Underdetermined result from test run steps. Test runs must be manually updated. 7. Click OK to save the options.
Setting field options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select the Fields category.
3. Select Use the TestTrack Server local date/time if you want record or event date/time fields to use the local date/time of the TestTrack Server instead of the local date/time of the client as the default. 4. Select any Version Fields options. These options affect the version found field and any custom fields in issues, requirements, requirement document, test case or test run events (e.g., version fixed, version verified, version released).
373
S e t t in g fie l d op t ion s
n n
Select an option for version fields to accept text or to restrict version fields to pop-up menus. Select Use advanced logic when sorting on version fields to look for delimiters and sort the alphanumeric characters in that section. If this option is not selected, a string comparison is performed when sorting.
Setting required field options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select Required from the Fields category.
3. Select any Required Field Identification options to change the appearance of required field labels.
n
Select text properties for required TestTrack Client fields. Select a color from the list or click the color button to choose a color. Selecting a specific color may make fields difficult to read because of user color schemes. Select text properties for required TestTrack Pro Web Client fields.
4. Select Enforce required status even if field security prevents editing 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 issue 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 issues. 5. Click OK to save the project options.
374
S e t t in g t ime t r ackin g op t ion s
Setting field relationship options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select Relationships from the Fields category.
3. Select any Field Relationship Options for each record type. These options specify what happens if a parent field changes and invalidates the child field. For example, if Version Found is a child field, and users can add text entries, the value cannot be cleared because field relationship rules cannot be enforced.
n
Select Remove any invalid selected child field values on the add item page to enforce the field relationship and prevent adding data that does not make sense. Select Remove any invalid selected child field values on the edit Item page to enforce the field relationship and prevent data that does not make sense from being added. Do not select this option if you want to preserve the original record information in the child field. Select a default association option for parent/child fields. When list values are added to a child field, you can associate them with all or none of the parent menu values.
Setting time tracking options

Time tracking values are calculated using the values entered in workflow event fields. You can select the event fields you want to use to calculate actual, estimated, and remaining hours, and story point values. You can use one field or a combination of fields to calculate each value. If you select multiple fields, the sum of each field value is used as the total.
375
S e t t in g t ime t r ackin g op t ion s
You can select any integer or decimal number event custom fields as Actual Hours, Estimated Hours, and Remaining Hours values. You can also select any built-in time tracking fields configured for the event. You can select an integer custom field configured for an item type or events as the Story Points value. See Configuring Time Tracking, page 429. 1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select an item type from the Time Tracking category.
3. Select Hide Work Items Tab to hide the Work Items tab on the Workflow tab in the Edit and View item dialog boxes. The Work Items tab displays detailed time tracking information for each workflow event added to an item and a summary of the estimate, actual, and remaining hours for an item, and the variance between the estimated and actual hours. See Viewing work items, page 44. 4. Select the Actual Hours fields you want to use to calculate the actual hours spent working on an item. 5. Select the Estimated Hours fields you want to use to calculate the estimated hours to work on an item. Note: If you use TestTrack TCM, you can select the Estimated run time field value, which is displayed on the Edit and View Test Run dialog boxes.
376
S e t t in g r e p or t op t ion s
6. Select the Remaining Hours fields you want to use to calculate the remaining hours to work on an item. 7. Select the Story Points field you want to use to calculate the story points related to an item. 8. Click OK to save the project options.
Setting report options

1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select the Reports category.
3. Select a Stylesheets option. The TestTrack Server searches for new stylesheets every five minutes. You can select another time interval. 4. Select a Time Zone option. Detail reports display the creation and modified time at the bottom of the report. You can configure the report to use the servers time zone or GMT. 5. Select any Diagrams options to change the appearance and output of workflow diagrams.
377
S e t t in g d ict ion ar y op t ion s
n n
Select the Diagram Font to use for text in diagrams. Select the diagram Output Type.
6. Select a Chart Font to use for text in report charts. 7. Click OK to save the project options.
Setting dictionary options

You can specify the default dictionary and add words to it. Make sure the dictionary is available for all users. It is possible to select a dictionary using the TestTrack Client that is not available in TestTrack Web and vice versa. In this case, users will not be able to spell check. Tip: Users can also specify a different dictionary in user options (Tools > User Options). 1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Select the Dictionary category.
3. Select a Main Dictionary. TestTrack includes American English, British English, and Canadian English dictionaries. Go to www.seapine.com/ttaddons.html#dictionary to download additional dictionaries. 4. Click Add to add words to the dictionary. See Adding dictionary words, page 352.
378
Cu st omiz in g Fie l d s
5. Select a word and click Edit to change it. See Editing dictionary words, page 352. 6. Select a word and click Delete to delete it. See Deleting dictionary words, page 352. 7. Click OK to save the project options.
Customizing Fields
You can customize TestTrack fields to meet your companys requirements and make sure users provide the correct types of information. You can also rename field labels and change existing field data.
Modifying Value Lists

You can modify TestTrack's value lists to use specific terminology and capture specific information. TestTrack includes the following default value lists: type, priority, severity, product, component, disposition, reproduced, version, test item type, test run set, and requirement importance. Note: The examples in this section use priority names. You will follow the same steps for each value list type. 1. Choose Tools > Configure List Values then select Priority Values. The Setup List Items dialog box opens.
Note: The setup dialog box changes based on the field type. For example, if you add an item to a parent field you also need to configure field relationships for the new item. 2. Click Add to create a new list item. See Adding list items, page 380. 3. Select a list item and click Edit to change it. See Editing list items, page 380. 4. Select a list item and click Top, Move Up, Move Down, or Bottom to change the display order. List items are displayed in the corresponding list in the same order. You may want to move the most frequently used items to the top of the list. 5. Click Sort to sort all items in ascending or descending order. 6. Click OK to save the changes.
379
M od ifyin g Val u e List s
Adding list items

1. Choose Tools > Configure List Values then select Priority Values. The Setup List Items dialog box opens. 2. Click Add. The Add List Item dialog box opens.
3. Enter a list item name. 4. Click OK. You return to the Setup List Items dialog box. 5. Optionally select the association for the list item. Priority is a child field in this example. You can associate the child field with all or none of the parent field list items. Note: You can also manually configure the parent-child field relationship. See Configuring Field Relationships, page 407. 6. Click OK to save the changes.
Editing list items

1. Choose Tools > Configure List Values then select Priority Values. The Setup List Items dialog box opens. 2. Select the list item you want to edit and click Edit. The Edit List Item dialog box opens. 3. Make any changes. 4. Click OK. The list is updated with the new name.
Deleting list items

1. Choose Tools > Configure List Values then select Priority Values. The Setup List Items dialog box opens. 2. Select the item you want to delete and click Delete. You are prompted to confirm the deletion.
380
Con figu r in g Re q u ir e me n t Typ e s
Note: If the list item is used by a record, you are prompted to reassign it to an existing field. 3. Click Yes. The list item is deleted.
Configuring Requirement Types

You can configure the requirement types used in your organization. When users add requirements, they select a requirement type. This helps categorize requirements based on their purpose and helps users manage groups of requirements more effectively. TestTrack RM includes the following default requirement types: business requirement, functional requirement, and non-functional requirement. See About default requirement types, page 181. Note: It is important to add the requirement types you use to TestTrack before users start adding requirements. You cannot change a requirement's type after the requirement is added to TestTrack. 1. Choose Tools > Administration > Requirement Types. The Configure Requirement Types dialog box opens.
2. Click Add to create a new requirement type. See Adding requirement types, page 382. 3. Select a type and click Edit to change it. See Editing requirement types, page 383. 4. Select a type and click Top, Move Up, Move Down, or Bottom to change the display order. Requirement types are displayed in fields in the same order. You may want to move more frequently used requirement types to the top of the list. Note: Requirements are also displayed in this order in detail reports that use the RequirementDocumentForwardTraceabilityReport.xslt stylesheet. 5. Select a type and click Inactivate to inactivate it. See Inactivating requirement types, page 383. 6. Select a type and click Delete to delete it. See Deleting requirement types, page 383. 7. Click OK to save the changes.
381
Note: You can configure command- and field-level security for each requirement type. See Adding security groups, page 324. You can also configure required fields and default field values for each requirement type. See Defining Required Fields and Default Values, page 406.
Adding requirement types

You can create a requirement type for each type of requirement your organization uses. See Configuring Requirement Types, page 381. 1. Choose Tools > Administration > Requirement Types. The Configure Requirement Types dialog box opens. 2. Click Add. The Add Requirement Type dialog box opens.
3. Enter a requirement type Name. The name is displayed in requirement fields. 4. Enter a Description to explain the purpose of the requirement type. 5. Click Choose Icon to select an icon to associate with the requirement type. Icons are displayed in the Select Requirement Type dialog box that opens when you add requirements, in the Specification Document window, and in the Microsoft Word Import Wizard. Keep the following in mind if you use custom icons:
n n
Icons must be 16x16 pixels in BMP, GIF, or PNG formats. The pixel at 0,0 is used for the transparency color.
6. Optionally enter a Tag Prefix and Suffix. You can enter up to 5 characters in each field. The prefix is prepended to the requirement number and can help users easily identify requirement types in requirement documents, list windows, and reports. The suffix is appended to the requirement number. For example, if you enter BR- for the Tag Prefix and -Web for the Suffix, the tag for requirement number 100 is BR-100-Web. 7. Click Required Fields & Default Values to configure required fields and default values for the new requirement type.
382
By default, new requirement types use the required fields and default values configured for all requirement types. You can override the default setting and set different field options for each requirement type. See Defining Required Fields and Default Values, page 406. Note: You are prompted to save the requirement type changes. Click Yes to save the changes, close the Add Requirement Type dialog box, and open the Required Fields & Default Values dialog box. 8. Click OK to save the changes.
Editing requirement types

Note: You cannot edit requirement types if other users are logged in to TestTrack. 1. Choose Tools > Administration > Requirement Types. 2. Select the requirement type and click Edit. The Edit Requirement Type dialog box opens. 3. Make any changes and click OK. 4. Click OK to save the changes. Requirements that use the requirement type are updated.
Inactivating requirement types

You can inactivate a requirement type if it is not used. You can activate the type if you decide to use it again. 1. Choose Tools > Administration > Requirement Types. The Configure Requirement Types dialog box opens. 2. Select a type and click Inactivate. The type is inactivated. Note: To activate an inactive type, select the type and click Activate.
Deleting requirement types

You may want to delete requirement types that are no longer used. You cannot delete requirement types that are currently used on requirements. Note: If you want to prevent users from selecting a requirement type but do not want to delete it, you can inactivate it. See Inactivating requirement types, page 383. 1. Choose Tools > Administration > Requirement Types. 2. Select the requirement type and click Delete. You are prompted to confirm the deletion. 3. Click Yes.
383
Con figu r in g Cu st om Fie l d s
The requirement type is deleted. 4. Click OK to save the changes.
Configuring Custom Fields

You can add up to 100 custom fields to a project. Custom field types include single and multi-line text fields, date and time fields, check boxes, pop-up menus, integers, floats, hyperlinks, and calculated fields that display read-only values based on input to other fields. Note: Custom issue fields can be displayed on the Custom Fields tab or in the main area of the Add Issue, Edit Issue, or View Issue dialog boxes. Custom fields for other items are displayed on the Detail tab of the Add, Edit or View dialog boxes. 1. Choose Tools > Administration > Custom Fields. The Setup Custom Fields dialog box opens.
2. Select a record Type. The custom fields displayed depend on the selected record type. 3. Click Add in the Active Fields area to create a custom field. See Adding custom fields, page 385. Note: The TestTrack database must be locked to add active custom fields. See Locking Projects, page 354. To add a field without affecting existing items, click Add in the Draft Fields area. See Creating draft custom fields, page 387. 4. Select a custom field and click Edit to change it. See Editing custom fields, page 389. 5. Select a custom field and click Top, Move Up, Move Down, or Bottom to change the display order. 6. Click OK to save the changes.
384
Note: Depending on the changes, you may be prompted to recalculate field values in items. See Recalculating field values, page 404.
Adding custom fields

You follow similar steps for creating custom fields for all item types. If you are creating test variant custom fields, see Adding test variant custom fields, page 386. 1. Choose Tools > Administration > Custom Fields. The Setup Custom Fields dialog box opens. 2. Select a record Type. The custom fields displayed depend on the selected record type. 3. To add a field, click Add in the Active Fields area. The TestTrack database must be locked to add active custom fields. See Locking Projects, page 354. To add a field without affecting existing items, click Add in the Draft Fields area. See Creating draft custom fields, page 387. The Add Custom Fields dialog box opens.
4. Enter a Field name. 5. Enter the Long label. Long labels are displayed in drop-down lists and help users distinguish between the same fields in different events. 6. Enter the Field code. The field code automatically generates data and is used with email templates, reports, and SoloSubmit. 7. Select a Location if you are creating issue custom fields.
n
Select Main Issue Window to display the field on the Add Issue, Edit Issue, and View Issue dialog boxes. Select Custom Fields Tab to display the field on the Custom Fields tab.
385
8. Select a Field type and any Field Properties. The available options depend on the selected field type.
n
Text Field allows users to enter a value. After choosing this field type, select Single line or Multi-line and configure any available options. Date/Time creates a date/time field. Users can change the date and time. Check Box creates a check box field. Pop-Up Menu allows users to select values from a menu. Select this field type if you add a field used in a relationship with other fields. Click Setup List Items to add values to the menu. See Configuring custom value lists, page 388. Calculated creates a read-only field with a value calculated from other field values. See Configuring Calculated Custom Fields, page 390.
n n n
Adding test variant custom fields

Test variants are attributes of a tested application that are used to generate test runs. For example, you may test an application on multiple operating systems. You can create a test variant named Operating System that includes values for each of the supported operating systems. Before you can use test variants, you need to add them as custom fields. Test variant fields are displayed on the Variants tab of the Add Test Case, Edit Test Case, and View Test Case dialog boxes and in the Generate Test Runs dialog box. See Managing Test Variants, page 266. Tip: You can use test variant custom field codes in test case text fields. When you generate test runs, the field code is replaced with the variant value used to generate the test run. Field codes in test case custom fields are only replaced in test run custom fields if the fields are mapped. See Configuring Item Mapping Rules, page 460. 1. Choose Tools > Administration > Custom Fields. 2. Select Test Variant as the record Type. Test variant custom fields are displayed. 3. Click Add. The Add Custom Fields dialog box opens. 4. Enter a Field name. 5. Enter the Long label. Long labels are displayed in drop-down lists and help users distinguish between the same fields in different events. 6. Enter the Field code. The field code automatically generates data and is used with email templates and reports. 7. Select an existing Value list or click Setup List Items to add a custom value list to the pop-up menu. See Configuring custom value lists, page 388. 8. Click OK to save the changes.
386
Creating draft custom fields

You can use draft fields to set up or edit custom fields without locking the TestTrack project or affecting existing items. Draft fields are not active in the project when changes are saved. Keep the following in mind:
n
You can copy existing active fields to create new draft fields similar to existing fields or to edit existing fields without immediately updating items in the project. You can create multiple draft fields with the same name, but a draft field name must be unique before it is made active. Draft calculated fields that use other draft fields as input values cannot be tested. If a draft calculated field formula uses the Item.mappedValue function to query a draft pop-up menu field, input mappings cannot be configured for the draft pop-up menu field. When configuring draft pop-up menu fields, changes to an existing value list also affect active fields that share the list. New value lists can be added for draft pop-up menu fields, but the value list cannot be shared with other custom fields. If you use an existing value list in a draft field and then delete all active fields that share the list, the list is deleted and you must reconfigure the draft field before making it active.
n n
1. Choose Tools >Administration >Custom Fields. The Setup Custom Fields dialog box opens. 2. Select a record Type.The custom fields displayed depend on the selected record type. 3. To create a new draft field, click Add in the Draft Fields area. See Adding custom fields, page 385 or Adding calculated custom fields, page 391. 4. To create a draft field based on an active field, select an active field and click Copy to Draft to create a copy. 5. Select a draft field and click Edit to make any changes. See Editing custom fields, page 389. 6. Select a draft field and click Delete to delete it. 7. Click OK to save the changes. When you are ready to make a draft field available in the project, you can promote it to active or replace an existing active field. See Promoting draft custom fields, page 387 or Replacing custom fields with drafts, page 388.
Promoting draft custom fields

You can promote draft custom fields to make them available in the project. You can also replace an active custom field if you created a draft from it. See Replacing custom fields with drafts, page 388. 1. Choose Tools >Administration >Custom Fields. The Set Up Custom Fields dialog box opens. 2. Select the draft custom field you want to make active and click Promote to Active.
387
The field is moved to the active fields list. 3. Click OK to save the changes. Items in the project are updated with the new field. If you promoted a calculated field, you may be prompted to recalculate field values. See Recalculating field values, page 404.
Replacing custom fields with drafts

If you copied an active custom field to create a draft field, you can replace the existing field with the draft when you finish configuring it. Note: You may not be able to replace an active field depending on the properties. If an error is displayed, you need to delete the existing active field and then promote the draft to active to make the changes available. See Promoting draft custom fields, page 387. 1. Lock the project. See Locking Projects, page 354. 2. Choose Tools >Administration >Custom Fields. The Set Up Custom Fields dialog box opens. 3. Select the draft custom field you want to replace an active field with and click Replace Active. The field is moved to the active fields list. 4. Click OK to save the changes. Items in the project are updated with the new field. If a calculated field replaces an active field, you may be prompted to recalculate field values. See Recalculating field values, page 404.
Configuring custom value lists

You can create custom value lists for pop-up menu fields or calculated list item fields. If you delete all active fields that use a value list, the list is deleted. Note: New value lists can be added for draft pop-up menu fields, but the lists cannot be shared with other custom fields. 1. Choose Tools > Administration > Custom Fields. 2. Select a record Type. The custom fields displayed depend on the selected record type. 3. Click Add. The Add Custom Field dialog box opens. 4. Select Pop-Up Menu or Calculated from the Field type list. If you are configuring a value list for a calculated field, select List Item from the Output type list. Note: Pop-up menu fields are the only custom fields available for test variants. 5. Select Supports multiple selection if you want users to be able to select more than one value from the list. 6. Click Setup List Items to add custom values to the list. The Setup List Items dialog box opens.
388
7. Enter a Name. 8. Click Add. The Add List Item dialog box opens 9. Enter a unique name. 10. Click OK. The list item is added. 11. Repeat steps 8-10 for each list item you want to add. 12. Click OK when you are finished. The value list is saved when the custom field using it is saved.
Editing custom fields

Tip: To make changes to custom fields without affecting existing items, you can copy the field as a draft and then make changes to the draft. See Creating draft custom fields, page 387. 1. Choose Tools > Administration > Custom Fields. 2. Select a record Type. The custom fields displayed depend on the selected record type. 3. Select the custom field and click Edit. The Edit Custom Fields dialog box opens. 4. Make any changes and click OK. You cannot change the Location option if other users are logged in to TestTrack. 5. Click OK to save the changes.
389
Con figu r in g Cal cu l at e d Cu st om Fie l d s
Deleting custom fields

1. Choose Tools > Administration > Custom Fields. 2. Select a record Type. The custom fields displayed depend on the selected record type. 3. Select the custom field and click Delete. You are prompted to confirm the deletion. 4. Click Yes. The custom field is deleted. 5. Click OK to save the changes.
Configuring Calculated Custom Fields

You can add calculated custom fields that generate values based on other field input values. Calculated custom fields generate read-only numeric, text, date/time, list item, and time span output values. Keep the following in mind before configuring calculated fields.
n
Options for calculating values depend on the calculated field's output type. Numeric, text, date/time, and list item output can be generated using a formula. List item outputs can also be generated using the table lookup method.Time span outputs can be generated using selected field values. Calculated fields use formulas to generate values. ECMAScript is the standard scripting language used in formulas. You can use the built-in formula editor and toolbar to create simple formulas that generate output, such as a value calculated by multiplying numeric input values or a value that concatenates two input values to generate a new text string. See Adding calculated field formulas, page 398. If you are familiar with ECMAScript, you can configure more complex formulas for calculated fields. See Understanding calculated field formula syntax, page 400. Calculated field values are stored in the TestTrack database. When new calculated fields are added, formulas must run for all existing items to update the project. These updates may impact TestTrack performance, so consider making calculated fields active in the project during downtime. After adding calculated fields, you can specify when you want to recalculate values in items. See Recalculating field values, page 404. If field values used in a formula calculation are not available in an item, the calculated field is left empty. This may occur if a formula relies on other fields created after items were added to the project. Editing existing items to provide the missing input values automatically updates the calculated field value.
1. Choose Tools > Administration > Custom Fields. The Setup Custom Fields dialog box opens.
390
2. Select a record Type. The custom fields displayed depend on the selected record type. 3. Click Add in the Active Fields area to create a new calculated field. See Adding calculated custom fields, page 391. Note: The TestTrack database must be locked to add active custom fields. See Locking Projects, page 354. To add a field without affecting existing items, click Add in the Draft Fields area. See Creating draft custom fields, page 387. 4. Select a custom field and click Edit to change it. See Editing custom fields, page 389. 5. Select an active custom field and click Top, Move Up, Move Down, or Bottom to change the display order. 6. Click OK to save the changes. Note: Depending on the changes, you may be prompted to recalculate fields in items. See Recalculating field values, page 404.
Adding calculated custom fields

You can add calculated fields that automatically generate read-only numeric, text, date/time, list item, and time span field values based on other field values. 1. Choose Tools >Administration >Custom Fields. The SetupCustom Fields dialog box opens. 2. Select a record Type. The fields displayed depend on the selected record type.
391
3. To add a field, click Add in the Active Fields area. The TestTrack database must be locked to add active custom fields. See Locking Projects, page 354. To add a field without affecting existing items, click Add in the Draft Fields area. See Creating draft custom fields, page 387. The Add Custom Fields dialog box opens.
4. Enter a Field name. 5. Enter the Long label. Long labels are displayed in drop-down lists and help users distinguish between the same fields in different events. 6. Enter the Field code. The field code is replaced with data and is used in email templates and reports. 7. Select a Location if you are creating issue custom fields.
n
Select Main Issue Window to display the field on the Add Issue, Edit Issue, and View Issue dialog boxes. Select Custom Fields Tab to display the field on the Custom Fields tab.
8. Select Calculated as the Field type. 9. Select an Output type and select any Field Properties. The available properties depend on the selected output type. Output types specify the type of value calculated fields generate. Field values calculated using a formula must return a value of the selected output type. If the calculated value does not match the output type, an error is displayed.
392
Numeric outputs are numeric values generated based on other field values. Enter the number of decimal places to round to. See Calculated numeric field example, page 393. Note: Calculated numeric output values can only include 15 digits or less.
Text outputs are string values, truncated to the specified character length, generated based on other text field values. The maximum output length is 255 characters. See Calculated text field example, page 394. Date/time outputs are date/time values generated based on date/time values or after a time value is added to an input value. Select Include time to include a time in the output value. See Calculated date/time field example, page 395. List item outputs are list item values generated based on mappings configured for numeric values or combinations of list item input values. Select a Calculated using option to calculate the output using a formula or the table lookup method. Select a Value list or click Setup List Items to create a new one. See Calculated list item field example, page 395. Note: Formulas for list item outputs use other field values to calculate a numeric value. The calculation result is mapped to a list item value, which is the generated output for the calculated field. See Adding calculated field formulas, page 398. The table lookup method provides a matrix of possible input combinations and allows you to assign output values to each combination. See Mapping calculated list item output values, page 402.
Time span outputs are the numeric difference between two specified date/time field values. Select the number of decimal places to round to, the fields to calculate the difference between, and a unit of time. See Calculated time span field time example, page 397. Note: If you select <Current time> as a time span calculation value, the field's calculated output is based on the last time the items were refreshed. To manually refresh time span values, choose View >Refresh. Time span fields that use the current time cannot be used as input for other calculated fields.
10. Click Edit to add a formula that calculates the output. You can only use formulas to calculate numeric, text, date/time, and list item outputs. See Adding calculated field formulas, page 398. 11. Click OK. The field is added. Tip: After you add a calculated field, you may want to add the corresponding column to the list window to view generated output. See Customizing list windows, page 23.
Calculated numeric field example

Calculated numeric fields can calculate numeric values, such as the number of times an event occurred. The following example shows the configuration for a calculated field that generates the number of times an issue was fixed.
393
The following formula returns the number of Fix events. If there are no Fix events, the result is 0. Item.Events.count("Fix")
Calculated text field example

Calculated text fields can concatenate text strings or return text values. The following example shows the configuration for a calculated field that analyzes requirement status and groups them into a smaller set of categories, which can be useful when reporting on requirements that are drafts, in progress, or complete.
The following formula returns the status category name. Comments are included to explain each line of the formula. // variables for the return value and requirement status var category = ""; var status = ""; // retrieve workflow status as a string status = Item.fieldValue("Status").toString(); // status included in Draft category if (status.match("Draft")) category = "Draft"; // statuses included in Done category
394
else if (status.match("Implemented")) category = "Done"; else if (status.match("Obsolete")) category = "Done"; // all other statuses are included in In Progress category else category = "In Progress"; // returns the category category;
Calculated date/time field example

Calculated date/time fields can generate date/time values or add time to date/time input values to generate new values, such as due dates. The following example shows the configuration for a calculated field that generates a test run due date by adding two weeks to the assignment date.
The following formula returns the due date. The function's first input value specifies the assignment date and the second value specifies the number of weeks to add. DateTime.addWeeks(Item.Events.last("Assign").fieldValue("Date"), 2)
Calculated list item field example

Calculated list item fields can return list values mapped to calculation results, such as risk level based on selected values for issue severity and occurrence. These fields can use either a formula or the table lookup method to return values.
Formula
List item fields that use a formula to calculate values must return a numeric value. The numeric result is mapped to a list value, which is generated as the field output. The following example shows the configuration for a list item field that uses a formula to calculate a risk score from values assigned to severity, occurrence, and detection inputs.
395
The following formula calculates the risk score. Item.mappedValue("Severity") * Item.mappedValue("Occurrence") * Item.mappedValue("Detection") To return a numeric value, the input field values are mapped to numbers used in the calculation.
To generate a list value output, a set of conditions are configured to map the calculation result to a list item. The conditions run top to bottom until the result matches a mapped list value, which is the field's generated output.
396
Table lookup
The following example calculates the same risk score using the table lookup method. Instead of mapping input and output values to numeric values, list items are mapped to each possible combination of input values. When the list item field value is calculated, the mapped list value is generated as the output.
Calculated time span field time example

Calculated time span fields can generate the time difference between two workflow events or a workflow event and the current time. This can be useful for tracking how long it took to move items through the workflow, such as the time to close a test run after it was assigned. The following example shows the configuration for a calculated field that returns the number of days to close an issue after it was created.
397
Adding calculated field formulas

You use formulas to return values for calculated custom fields. Formulas can use input values from numeric, text, date/time, and check box fields and values mapped to list menu items. Note: Calculated fields use ECMAScript formulas to generate output values. If you are familiar with the ECMAScript language, you can create more complex formulas to calculate values. See Understanding calculated field formula syntax, page 400. 1. Click Edit in the Formula area when adding a calculated custom field. The Edit Formula dialog box opens.
398
2. Use the formula toolbar to enter a formula.

n
Click Insert Field to insert a field value. Select the field and click OK. Note: Some fields cannot be used for calculated field input because the values can change even if items are not modified, such as Folders and Has Emails. Other field values may change when administrative changes occur, such as updating time tracking project options, but can still be used in calculated field formulas. See Fields Affected by Administrative Changes, page 627. If fields that can be affected by administrative changes are used in calculated custom field formulas, values are only recalculated when individual items are modified and saved. You can also create an escalation rule to schedule field recalculations. See Adding escalation rules, page 449.
Click Insert Mapped Field to insert a list field value. Select the field and click OK. Mapped fields use the input list mappings configured in step 3. Click Insert Function to insert a function that performs more complex actions on an input field to return values. See Inserting functions in calculated field formulas, page 401.
399
Note: The last line of a formula must evaluate to a value of the same type as the calculated field output. For example, if you are adding a formula to calculate numeric output, the formula must return a numeric value. List item formulas must evaluate to a numeric value, which is mapped to a list item value configured in step 4 to generate the output. 3. Configure Input List Mapping settings to map list items to numeric or text values. Mapped values are used as the input to evaluate when calculating output values.
n
Click Add to insert a field to map values for. If you added a mapped field in the formula editor, the field is automatically added to the list. Select a list item and enter the Value to map it to. Enter an Unmapped items default to value to specify the default value for unmapped input items. Select an input field and click Delete to delete it.
n n
4. Configure Output List Item Mapping rules to map the calculated output to a list item value. These options are only available for calculated fields with list item outputs.
n
Click Add to add a new calculation rule. Select the Condition the rule must meet, enter the Calculation Result, and select a Mapped Item. Select an Unmapped calculation results default to value to specify the default value for calculations not mapped to an output item. Click Top, Move Up, Move Down, and Bottom to change the output mapping order. Rules evaluate from top to bottom and stop when a match is found. Select an output mapping rule and click Delete to delete it.
5. Click Test to test the formula. See Testing calculated field formulas, page 403. 6. Click OK to save the formula.
Understanding calculated field formula syntax

Calculated custom field formulas use the ECMAScript language, which is a subset of JavaScript. If you are familiar withJavaScript, you may be able to create calculated custom field formulas, but there are differences between JavaScript and ECMAScript.
n
Browsers are not used inECMAScript formulas. There are no objects or methods for actions on the Document Object Model (DOM). You cannot display alerts using ECMAScript. All user input for ECMAScript formulas is provided by values in other TestTrack item fields. Return statements are not used inECMAScript. The last line of a formula returns the calculation result.
n n n
Only administrators familiar with the scripting language should configure complex formulas for calculated fields. Refer to the ECMA-262 Standard Language Specification (http://www.ecmainternational.org/publications/standards/Ecma-262.htm) for information.
400
Tip: You can create new calculated custom fields as drafts to experiment with formulas without affecting existing items. See Creating draft custom fields, page 387.
About ECMAScript functions

Each function has its own syntax rules. If you do not follow these rules, errors are generated when you test the formula or save the calculated field.
n
All standard ECMAScript is supported. Only functions should be used to query input data. See Calculated Custom Field Functions, page 619. The scripting language is case sensitive. Text strings, including TestTrack field names, are entered in double quotation marks.For example, "TextString". Numeric values and variables do not use quotation marks. Each line of code should end with a semicolon (;). You can use two single forward slashes (//) before a line of code to comment it so it does not run as part of the formula. You may want to use comments to help determine lines of code that are not be running correctly. The last line of a formula should return a value of the corresponding output type. If you are using a formula in a list item field, the formula must return a numeric value that can be mapped to a list item value to generate as the output.
n n
n n n
About code completion

If you manually enter formulas, code completion displays the available functions or properties as you type. Enter a period (.) after an object to display a list of supported functions and properties.
The items in this list change based on the selected object. Scroll through the list to select the functions or property you want to use. Double-click the function or property or press Enter to add it to the formula.
Inserting functions in calculated field formulas

You can use functions in calculated field formulas to query item data. 1. Click Insert Function when adding a formula for a calculated field. The Insert Function dialog box opens.
401
2. Select the function you want to add. See Calculated Custom Field Functions, page 619. Tip: Select a function category from the Category list to display the function type you want. You can also enter the first few letters of the function name in the Filter field to display matching functions. 3. Enter the function Inputs. Note: The last line of a formula must evaluate to the same value type as the selected output. Each function lists the value type it returns in the Output area. 4. Click Insert. The function is inserted in the formula.
Mapping calculated list item output values

You can map output values for calculated list item fields using the table lookup method. The table displays all possible input value combinations based on the fields you want to use in a calculation. Each combination can be mapped to a list value, which is returned as the output for the list item field. Use the table lookup to set up a calculation without using the scripting language. Note: You can also use a formula to calculate list item outputs. See Adding calculated field formulas, page 398. 1. Select List Item as the Output type when adding a calculated custom field. 2. Select Table Lookup from the Calculated using list. 3. Select a Value list or click Setup List Items to create a new list. See Configuring custom value lists, page 388. 4. Click Edit to map the input fields. The Edit Mapping dialog box opens.
402
5. Click Add Field to add an input field to include in the calculation. The Add Field dialog box opens. 6. Select the field and click Add. The field is added as a new column in the table. 7. Repeat steps 5 and 6 for each field you want to include in the calculation. You must add each field before mapping any values. 8. Select a row and select the Mapped Value to assign to the combination of field inputs. Tip: Ctrl+click multiple rows and click Set Value to assign multiple fields at once. 9. Click Delete Field to remove a field from the table. Select the field you want to delete and click Delete. Deleting a field clears all mapped values. 10. Select an Unmapped outputs default to value to specify the default value for combinations that are not mapped to an output value. 11. ClickTest to test the configuration. See Testing calculated field formulas, page 403. 12. Click OK to save the mapping.
Testing calculated field formulas

You can test formulas before saving calculated custom fields to make sure they are configured correctly. Note: Draft calculated fields that use other draft fields as input values cannot be tested. See Creating draft custom fields, page 387. 1. ClickTest when editing a formula. The Test Formula dialog box opens.
403
2. Enter the item number for the Test Items or click the Select additional items to test button to select items. Note: A maximum of 100 items can be tested at a time. Separate multiple item numbers with spaces or commas. 3. Click Test. The Results are displayed. Click a result to view its details.
Recalculating field values

Changes to custom field configurations may affect calculated field values. You can select when to recalculate the values. Tip: You can also create an escalation rule to schedule field recalculations. See Adding escalation rules, page 449. 1. Save any changes to custom fields. The Recalculate dialog box opens.
404
2. Select a recalculation option.

n n
Delay recalculation until <server time> specifies when to recalculate fields. Select a time. Recalculate now updates the calculated values in all fields immediately. Note: Recalculating fields automatically creates an escalation rule that runs once, either immediately or at the specified time. TestTrackServer performance may be slower when the escalation rule runs.
Do not recalculate recalculates fields only when individual items are modified.
3. Click OK.
Troubleshooting calculated custom fields

If errors occur when calculating custom field values, use the following methods to troubleshoot.
Has CalculationError field

To view items with calculation errors, insert the Has Calculation Error column in the item list window. 1. Right-click a column header in the list window and choose Insert Column. A new column is added. 2. Right-click the new column and choose General > Has Calculation Error. The column is added. Items with calculation errors display a Yes value.
Last Error Date information

If a calculated field generates an error, the date and time of the last error is displayed in the Setup Custom Fields dialog box. 1. Choose Tools >Administration > Custom Fields. The SetupCustomFields dialog box opens. 2. Select a record Type. Calculated fields with errors display a date and time in the Last Error Date column in the Active Fields area.
405
De fin in g Re q u ir e d Fie l d s an d De fau l t Val u e s
Server log
When items are saved with calculation errors, a message is added to the server log for each field with an error. An error is only logged the first time it occurs for each field in a 24-hour period.
Defining Required Fields and Default Values

You can set any input field, including custom fields, as a required field. When a field is required, users must enter data in the field before TestTrack can save any changes. You can also define default values for fields. Required fields and default field values are project-specific. Required fields must be populated for all instances of actions. For example, the Found by field is required and does not have a default value. When multiple detail records are created for a single issue, the Found by field must be populated for all detail records. Note: Field-level security can be used to restrict access to required fields. If a required field is hidden for a security group, users may not be able to add items, such as issues. As a workaround, you can grant access to a required field when users add records and hide the field when users edit records. You can also allow users to save records without setting values in required fields they do not have permission to edit. See Setting required field options, page 374. 1. Choose Tools > Administration > Required Fields & Default Values. The Required Fields & Default Values dialog box opens.
2. Select a record Type. The fields displayed depend on the selected record type. If you are configuring requirement fields, select a requirement type to configure fields for the type.
406
Con figu r in g Fie l d Re l at ion sh ip s
Note: By default, required fields and default values are the same for all requirement types. You can override the default setting and configure different fields for each requirement type. An asterisk indicates the requirement types that do not use the default settings. Clear the Use values from <All Requirement Types> option to change the settings for the selected type. 3. Select the field group from the list. 4. To set a required field, select the corresponding check box.
n n n
A field that is set using check boxes and/or radio buttons cannot be set as a required field. The check box is selected if a field is always required. The check box is not selected and is inactive if a field cannot be required.
5. Enter or select a default value for the field.

n
Click the Edit the default value button to enter default values for multi-line text fields. You can include formatted text, images, tables, and hyperlinks in most values. See Formatting MultiLine Text Fields, page 49. Click the Select the date/time button to select default date/time values. Click Go to test hyperlink values. The web page opens in a browser window.
n n
6. Repeat steps 2 through 5 to set required fields and default values for other groups. 7. Click OK.
Editing required fields and default values

1. Choose Tools > Administration > Required Fields & Default Values. The Required Fields & Default Values dialog box opens. 2. Select a record Type. The fields displayed depend on the selected record type. 3. Select the field group you want to edit from the menu. 4. Click the corresponding check box to clear a required field. 5. Enter or select a different default value to change it. 6. Click OK to save the changes.
Configuring Field Relationships

Parent-child field relationships create project dependencies that restrict users to selecting values based on the relationship. When a field is selected from a menu and there is a parent-child relationship, the child field is populated with the values based on the parents field value.
n n
Event fields can be set as parent or child fields for other event fields in the same event type. Entered by, Found by, and Fixed by cannot be set as parent or child fields.
1. Choose Tools > Administration > Field Relationships. The Field Relationship Selection dialog box opens.
407
Con figu r in g Fie l d Re l at ion sh ip s
2. Select a record Type. The fields displayed depend on the selected record type. 3. Click Add to create a field relationship. See Adding field relationships, page 408. 4. Select a field relationship and click Edit to change it. See Editing field relationships, page 409. 5. Select a field relationship and click Delete to delete it. See Deleting field relationships, page 409. 6. Click OK to save the changes.
Adding field relationships

1. Choose Tools > Administration > Field Relationships. The Field Relationship Selection dialog box opens. 2. Select a record Type. The fields displayed depend on the selected record type. 3. Click Add. The Setup Parent-Child Relationship dialog box opens. 4. Select a Parent field then select a Child field. 5. Click OK. The Setup Field Relationships dialog box opens.
6. Enable or disable the child fields for each field in the parent list.
408
Re n amin g Fie l d Lab e l s
A parent field can have one or more child field relationships. A child field can only have one parent. A child field can also be the parent of another field. When a field is set as a child field, it is excluded from the child field list. To prevent circular references, parent or grandparent fields are excluded from the parent list.
n n
7. Click OK when you finish setting up the field relationship. You return to the Field Relationship Selection dialog box. 8. Click OK to save the changes. Tip: If a project uses default values, the child fields default value may be invalid, depending on the parent fields default value. The default value can still be used. Hidden fields can cause unintended changes. If a parent field is changed, the child field may be changed to <not set> depending on project options. In addition, changes cannot be saved if the child field is required.
Editing field relationships

1. Choose Tools > Administration > Field Relationships. The Field Relationship Selection dialog box opens. 2. Select a record Type. The fields displayed depend on the selected record type. 3. Select the field relationship and click Edit. The Setup Field Relationships dialog box opens. 4. Make any changes and click OK.
Deleting field relationships

1. Choose Tools > Administration > Field Relationships. The Field Relationship Selection dialog box opens. 2. Select a record Type. The fields displayed depend on the selected record type. 3. Select the field relationship and click Delete. The field relationship is deleted.
Renaming Field Labels

You can rename field labels to match your companys terminology. Keep the following in mind:
n
Field codes do not change. For example, if you rename Disposition (%DISP%) to Substatus, you use %DISP% to include the Substatus data in an email template. Columns in the project database are not renamed. If you use the ODBC driver, the original database field name must be used.
409
Re n amin g Fie l d Lab e l s
Field label changes do not apply to SoloBug. Field names can be changed when you customize the SoloBug executable.
1. Choose Tools > Administration > Rename Field Labels. The Rename Field Labels dialog box opens.
Note: Fields marked with an asterisk have short and long field names. The short name is used to allow fields to fit into the user interface without being truncated. Date Found and Version Found, which are both long versions, are used in filters, reports, and columns. Date and Version, which are both short versions, are used in the issue windows (e.g., Add Issue). Use the same terminology for short and long field names. For example, if you rename Version to Account, make sure you change Version Found to Account Found. 2. Select a record Type. The field labels displayed depend on the selected record type. 3. Select the field you want to rename and click Edit. The Edit Field Label Value dialog box opens.
4. Enter the Field Label. Labels must be 32 characters or less. Labels that do not fit in the allotted space are truncated. 5. Click OK. 6. When you finish, click OK in the Rename Field Labels dialog box. The changes are saved and the project is updated with the new field labels.
410
Con figu r in g Fol d e r Typ e s
Note: Renaming a field does not affect image files. To change the tab name in the TestTrack Web interface you can modify the image file, which is generally stored in inetpub/wwwroot/ttweb/images. Most graphics include one image for a selected tab and one for a non-selected tab.
Restoring field labels

You can restore the field labels to their original values at any time. 1. Choose Tools > Administration > Rename Field Labels. The Rename Field Labels dialog box opens. 2. Click Restore to Original Values. The field labels revert to the original values. 3. Click OK to save the changes.
Configuring Folder Types

You can create folder types to control the appearance of folders and the type of data displayed for a group of folders. Folder types also provide a way to tag a group of folders used for similar purposes, which is useful for reporting. TestTrack includes the following default folder types: Folder, Product, Release, Iteration, and Backlog. You can add other folder types to support your organization's development process. 1. Choose Tools > Administration > Folder Types. The Configure Folder Types dialog box opens.
2. Click Add to create a new folder type. See Adding folder types, page 412. 3. Select a folder type and click Edit to change it. See Editing folder types, page 413. 4. Select a folder type and click Top, Move Up, Move Down, or Bottom to change the display order. You may want to move the most frequently used folder types to the top of the list. 5. Select a folder type and click Inactivate to inactivate it is no longer used. See Inactivating folder types, page 413. 6. Select a folder type and click Delete to delete it. See Deleting folder types, page 414.
411
Ad d in g fol d e r t yp e s
Adding folder types

Add a folder type when you want to differentiate the appearance and data displayed for a group of folders. Users can select a folder type when creating folders or change the type of an existing folder. See Adding folders, page 61. TestTrack includes the following default folder types. Folder type Folder Product Use to: Organize and group related items. Organize the activities and items related to a product. Plan and track a release. Plan and track an iteration. Organize and prioritize backlog items. Panes enabled on the Folders list window -Details, Web View
Release Iteration Backlog
Details, Web View, Release Planning Details, Web View, Release Planning Details, Web View
Note: A project must include at least one folder type. 1. Choose Tools > Administration > Folder Types. The Configure Folder Types dialog box opens. 2. Click Add. The Add Folder Type dialog box opens.
412
Ed it in g fol d e r t yp e s
3. Enter a Name and Description. 4. Select any Banner Options to change the appearance of folders in the Folders list window and other windows.
n
Select a Banner Color to use for this folder type. The folder type and name are displayed in the banner in the Folders list window. Click Choose Closed Icon to change the icon used when this folder type is not selected. Click Choose Open Icon to change the icon used when this folder type is selected. Note: Icons are available in the workflowicons directory in the default TestTrack application directory. You can also use custom icons. Custom icons must be 16x16, 24x24, or 32x32 pixels in BMP, GIF, or PNG format. The pixel at 0,0 in the image is used for the transparency color.
n n
5. Select any Folder Options to specify the panes to display when this folder type is open in the Folders list window. See Using the Folders list window, page 58.
n
Enable Release Planning fields displays the Release Planning pane, which provides information about release schedules. See Configuring release planning information, page 64. Enable Details Pane displays the Details pane, which provides additional information about folders. See Entering folder details, page 63. Enable Web View Pane displays the Web View pane, which displays a web page related to the folder. See Setting the default folder web page, page 64.
6. Click OK to save the folder type.
Editing folder types

You can edit a folder type to change the banner color, icons, or panes displayed on the Folders list window. 1. Choose Tools > Administration > Folder Types. The Configure Folder Types dialog box opens. 2. Select a folder type and click Edit. The Edit Folder Type dialog box opens. 3. Make any changes. 4. Click OK to save the changes.
Inactivating folder types

You can inactivate a folder type if it is not used. You can activate the folder type if you decide to use it again. 1. Choose Tools > Administration > Folder Types. The Configure Folder Types dialog box opens. 2. Select a folder type and click Inactivate. The folder type is inactivated.
413
De l e t in g fol d e r t yp e s
Note: Inactive folder types are displayed in gray. To activate an inactive folder type, select the folder type and click Activate.
Deleting folder types

You can only delete folders types that are not in use by folders. 1. Choose Tools > Administration > Folder Types. The Configure Folder Types dialog box opens. 2. Select a folder type and click Delete. You are prompted to confirm the deletion. 3. Click Yes. The folder type is deleted. 4. Click OK to save the changes.
Customizing Workflows
A workflow consists of states, events, and transitions that define the path an issue, requirement, requirement document, test case, or test run follows throughout its lifecycle. The workflow guides users through your tracking process. Simple processes may only require a few steps while more complex processes may include multi-user assignments and stricter requirements.
n n
States indicate a step in the workflow. For example, Open - On Hold or Closed - Verified. Events specify the action that can be performed at each state or step in the workflow. For example, Assign, Estimate, or Verify. Workflow events are stored with the record history. Edit or view a record to access the History tab and view any events. Transitions specify the initial state when a record is created and the events that can be added for each state. Transitions move records from one state to another. For example, Open to Fixed or Fixed to Closed. Assignment rules specify how assignment events are processed. For example, use the state with highest priority.
TestTrack includes default workflows that you can customize. If you need to track different types of processes, you can create multiple TestTrack projects and customize the workflows for each project. Workflow customization generally includes the following steps:
n n n n
Configuring Workflow States, page 415 Configuring Workflow Events, page 417 Configuring Workflow Transitions, page 423 Configuring Workflow Assignment Rules, page 424
Before you customize the workflow, take the time to document and understand your companys business process. Analyzing your workflow helps you easily determine the states that are used, the actions that users perform, and how information moves through the workflow. A clearly defined workflow ensures that issues move from initial reporting to resolution and do not get stranded.
414
Con figu r in g Wor kfl ow S t at e s
A carefully analyzed and customized workflow can guard against wasted time, redundancy, and disorganization. When analyzing your workflow, identify the steps that make up your business process and determine the actions that you want to associate with each step. In addition, consider the individuals involved in the process, the types of events they perform, the type of data they track, and the types of transitions that are used.
n
After you analyze the process, create a list of the states, events, and transitions used throughout the workflow. To begin customization, first create the workflow states then define the events that can be performed for each state. See Configuring Workflow States, page 415 and Configuring Workflow Events, page 417. It can be difficult to track a workflows states, events, and transitions and how they relate to each other. You can evaluate the workflow to view any potential problems or view a diagram of the workflow. See Evaluating the Workflow, page 426 and Diagramming the Workflow, page 427.
Tip: You may also want to configure automation rules to extend the functionality of the workflow and automate actions. You can configure notification rules to automatically email users and customers when an activity is performed, triggers to perform actions based on an activity such as a state change, and escalation rules to perform actions based on a schedule. See Configuring Automation Rules, page 436.
Configuring Workflow States

A state is a step or decision point in the workflow. While items are either open or closed, you may create different states. For example, an open issue can be On Hold or Pending Verification. 1. Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens with the States tab selected.
415
Con figu r in g Wor kfl ow S t at e s
2. Select a record Type. The items change based on the selected record type. 3. Click Add to create a new state. See Adding states, page 416. 4. Select a state and click Edit to change it. See Editing states, page 416. 5. Select a state and click Top, Move Up, Move Down, or Bottom to change the display order. 6. Select a state and click Inactivate to inactivate it if no longer used. See Inactivating states, page 417. 7. Select a state and click Delete to delete it. See Deleting states, page 417. 8. Click OK to save the changes.
Adding states
1. Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens with the States tab selected. 2. Select a record Type. The items change based on the selected record type. 3. Click Add. The Add State dialog box opens.
4. Enter a State Name and Description. 5. Select an Attribute. 6. If you are adding a requirement or requirement document state, select a Lock setting to allow or restrict item editing in this state. 7. If you are adding a requirement state, select Can generate test case to allow test cases to be generated for requirements in this state. 8. If you are adding a test case state, select Can generate test run to allow test runs to be generated for test cases in this state. 9. If you are adding a closed test run state, select a Test run result. The result is added to the test run when it enters this state. 10. Click OK. The state is added.
Editing states
1. Choose Tools > Administration > Workflow.
416
Con figu r in g Wor kfl ow Eve n t s
The Configure Workflow dialog box opens with the States tab selected. 2. Select a record Type. The items change based on the selected record type. 3. Select a state and click Edit. The Edit State dialog box opens. 4. Make any changes and click OK. The changes are saved.
Inactivating states
To preserve historical information, inactivate a state instead of deleting it. You cannot inactivate a state if a record is currently in the state. 1. Choose Tools > Administration > Workflow. The Configure Workflow dialog box with the States tab selected. 2. Select a record Type. The items change based on the selected record type. 3. Select a state and click Inactivate. You are prompted to confirm the inactivation. 4. Click Yes. The state is inactivated. Note: To activate an inactive state, select the state and click Activate.
Deleting states
You cannot delete states that are referenced in the project. Inactivate states that you do not want users to access. See Inactivating states, page 417. 1. Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens with the States tab selected. 2. Select a record Type. The items change based on the selected record type. 3. Select a state and click Delete. You are prompted to confirm the deletion. 4. Click Yes. The state is deleted.
Configuring Workflow Events

Events specify the action that can be performed at each state. For example, an event can assign the record to another user. Some events are performed by users and others are system events. 1. Choose Tools > Administration > Workflow. 2. Select a record Type. The items change based on the selected record type. 3. Click the Events tab.
417
4. Click Add to create a new event. See Adding events, page 418. 5. Select an event and click Edit to change it. See Editing events, page 422. 6. Select an event and click Top, Move Up, Move Down, or Bottom to change the display order. 7. Select an event and click Inactivate to inactivate if it is no longer used. See Inactivating events, page 422. 8. Select an event and click Delete to delete it. See Deleting events, page 423. 9. Click OK to save the changes.
Adding events
1. Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens. 2. Select a record Type. The items change based on the selected record type. 3. Click the Events tab. 4. Click Add. The Add Event dialog box opens with the Details tab selected.
418
5. Enter a Name and Description. 6. Select Informational Event to use the event for information only. Informational events can be added to the record from any state in the workflow because they do not affect the workflow. 7. Select a Resulting State to specify which state the record moves to after the event is entered. Select multiple states if you want the user to select a resulting state. For example, you want users to select a state for a fix event so you select Fixed, Closed, or Closed (Fixed). When users enter fix events, they are prompted to select a resulting state. 8. Select an Assignments option to specify how the event affects the assignment.
n n
Event results in a new assignment adds an Assign to field to the event. Allow multiple user assignments allows the record to be assigned to multiple users if the event results in a new assignment. Event does not affect the current assignment does not change the assignment. Event clears the current assignment removes the current assignment so the record is not assigned.
n n
9. Select Display time tracking field using to enable the built-in time tracking field in the event dialog box.
419
You may want to select this option if items can have multiple instances of the same event so you can choose how to calculate the total hours. See Configuring Time Tracking, page 429.
n
Sum of hours from all events of this type uses the total hours entered in the time tracking field for all instances of the event for an item. For example, select this option for the Fix event to report the total time spent fixing issues. Hours from last entered event of this type uses only the hours from the last instance of the event for an item. For example, select this option for the Estimate event to report the most recent estimate entered. Note: If this option is enabled, an Hours field is added to the event dialog box. You can rename the field on the Fields tab.
10. Select Files can be attached to this event to allow users to attach files to the event. An Attachments tab is added to the event if this option is selected. 11. Select Include event notes with the release notes to add event notes to the release notes. This option only applies to issue events. 12. Select Electronic signatures are required when adding or editing this event to require electronic signatures when the event is added or changed. This option is only available if Enable detailed audit trail logging is enabled and Electronic signatures are required is disabled in the Compliance project options. See Setting compliance options, page 368. 13. Select Do not show the dialog box when entering this event to prevent the event dialog box from opening. This option can only be selected if an event is not informational, has one resulting state, does not allow assignments, and does not use the built-in time tracking field. 14. Select Make event visible in review mode to display events in review mode. This option only applies to requirements and requirement documents. 15. Select Include option to mark dependent items as suspect to add the option of marking dependent items as suspect in the event dialog box. 16. Click the Custom tab to add custom fields and icons to the event.
n
Click Custom Fields to add a custom field to the event. A Custom Fields tab is added to the event dialog box. See Configuring Custom Fields, page 384. Select Add a custom icon to the TestTrack Client events toolbar to add an icon to the toolbar. Click Choose Icon to select an icon. See Customizing the events toolbar, page 421. Tip: If you do not select an event icon, the event text is displayed in the toolbar.
Enter a graphic file name to upload a TestTrack Web quick link icon. The web page requires two icons, one for the enabled event and one for the disabled event. The disabled icon must be preceded with d_. Both images must be added to the ttweb/images folder on the web server.
420
17. Click the Fields tab. The Fields tab includes the standard fields that are included on the event dialog box.
n n
Select a field and click Edit to change the name, the long label, or the field code. Make any changes and click OK.
Note: Field names, or short labels, are displayed in event dialog boxes. Long labels are displayed in drop-down lists to distinguish between the same fields in different events. Field codes automatically generate data and are used with such things as email templates. 18. Click OK to add the event.
Customizing the events toolbar

The workflow event toolbar icons can be customized using the icons installed in the workflowicons directory in the default TestTrack application directory or with custom icons. Keep the following in mind if you use custom icons:
n n
Icons must be 16x16, 24x24, or 32x32 pixels in BMP, GIF, or PNG formats. The pixel at 0,0 is used for the transparency color.
1. Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens. 2. Select a record Type. The items change based on the selected record type. 3. Click the Events tab.
421
4. Select the event you want to add the custom icon to and click Edit. The Edit Event dialog box opens. 5. Click the Custom tab. 6. Select Add a custom icon to the TestTrack Client events toolbar. 7. Click Choose Icon. The Open dialog box opens. 8. Browse for and select an icon then click Open. The icon is added to the event. 9. Click OK. The changes are saved. Note: If you do not select an event icon, the event text is displayed in the toolbar.
Editing events
1. Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens. 2. Select a record Type. The items change based on the selected record type. 3. Click the Events tab. 4. Select an event and click Edit. The Edit Event dialog box opens. 5. Make any changes and click OK. The changes are saved.
Inactivating events
To preserve historical information, inactivate an event instead of deleting it. 1. Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens. 2. Select a record Type. The items change based on the selected record type. 3. Click the Events tab. 4. Select an event and click Inactivate. You are prompted to confirm the inactivation. 5. Click Yes. The event is inactivated. Note: To activate an inactive event, select the event and click Activate.
422
Con figu r in g Wor kfl ow Tr an sit ion s
Deleting events
You cannot delete events referenced by the Transitions tab or that are part of a records historical events. 1. Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens. 2. Select a record Type. The items change based on the selected record type. 3. Select an event and click Delete. You are prompted to confirm the deletion. 4. Click Yes. The event is deleted.
Configuring Workflow Transitions

Transitions specify the initial state when a record is created and the events that can be added for each state. Transitions help enforce the workflow by enabling event menu items and icons based on the current state of the record. 1. Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens. 2. Select a record Type. The items change based on the selected record type. 3. Click the Transitions tab. 4. Select a transition and click Edit to change it. See Editing transitions, page 423. 5. Select a resulting state and click Edit to change it. See Editing event resulting states, page 424. 6. Click OK to save the changes.
Selecting the initial record state

1. Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens. 2. Select a record Type. The items change based on the selected record type. 3. Click the Transitions tab. 4. Select the Initial State. All new records are added in the selected state. 5. Click OK to save the changes.
Editing transitions
1. Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens. 2. Select a record Type. The items change based on the selected record type.
423
Con figu r in g Wor kfl ow Assign me n t Ru l e s
3. Click the Transitions tab. 4. Click Edit in the State Transitions area. The Edit State Transitions dialog box opens.
5. Select the events that can be entered for each state. 6. Click OK. The changes are saved and you return to the Configure Workflow dialog box.
Editing event resulting states

1. Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens. 2. Select a record Type. The items change based on the selected record type. 3. Click the Transitions tab. 4. Click Edit in the Event Resulting States area. The Edit Event Resulting States dialog box opens.
5. Select the states that the record can move to for each event. 6. Click OK. The changes are saved and you return to the Configure Workflow dialog box.
Configuring Workflow Assignment Rules

Assignment rules specify how state assignment events are processed. You can restrict which users can enter an event, specify multi-user assignment options, and change the rules order. 1. Choose Tools > Administration > Workflow.
424
Con figu r in g Wor kfl ow Assign me n t Ru l e s
The Configure Workflow dialog box opens. 2. Select a record Type. The items change based on the selected record type. 3. Click the Assignment Rules tab. 4. Select a state to view its assignment rules and resulting state priorities.
5. Select a state and click Edit to change assignment rules or the resulting states priority. The Edit Assignment Rules dialog box opens.
425
Eval u at in g t h e Wor kfl ow
6. Select Only allow assigned users to enter an event when the issue is in the selected state if you only want assigned users to be able to enter an event. 7. Select a Multi-User Assignment Rules option to determine the resulting state if a conflict occurs. Records can have different resulting states when they are assigned to multiple users. These options also change based on the selected assignment rules.
n
Use state entered by first user to respond processes the event entered by the first user and moves the record to the corresponding state. If the event moves the record to a new state or affects the current assignment, the remaining assignments are removed. If the event leaves the record in the current state or does not affect the assignment, the assignments are not removed and users can enter events. Wait for all assigned users to respond then use the state with the highest priority waits until all users respond then uses the event with the highest resulting state to determine the next state. For example, one user enters Verify Fixed resulting in a Close state and another user enters Verify Failed resulting in an Open state. The record moves to Open because it has the highest priority. Use the state with the highest priority and proceed as soon as an event with the highest priority is entered accepts events from users until an event with the highest resulting state priority is entered or until all users respond. If all users respond, the highest resulting state is used. For example, Open is the highest resulting state. As soon an event with Open as a resulting state is entered, the record moves to Open and the assignment list is cleared. If all users enter events with Close as a resulting state, the record moves to Closed.
8. Make sure the Resulting State Priorities list is ordered from highest to lowest priority. Select a state and click Top, Move Up, Move Down, or Bottom to reorder the states. 9. Click OK. The changes are saved.
Evaluating the Workflow

You can evaluate a workflow to view potential issues and correct them. For example, if a state is set to only allow assigned users to enter an event, but the state can be reached through an event other than an assign event, it is reported as a potential workflow issue that needs to be fixed. 1. Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens. 2. Click Evaluate Workflow. The Potential Issues dialog box opens. All potential issues are listed.
426
Diagr ammin g t h e Wor kfl ow
3. Click Save As to save the information as a text file. 4. Click OK to close the dialog box.
Diagramming the Workflow

You can diagram the workflow to view configured states, events, and transitions. 1. Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens. 2. Click Diagram Workflow. The Diagram Workflow dialog box opens. 3. Select the states you want to include in the diagram. If you do not include a state, the states and events leading to are not included in the diagram. 4. Click OK. The diagram opens.
427
Ove r r id in g t h e Wor kfl ow
States and transitions are represented with the following colors and objects:
n n n n n n
Green double circleDefault state Red double circleClosed state Blue circleOpen state Blue lineNormal transition Red lineTransition to a closed state Yellow lineTransition from a closed state to an open state Note: You can also set project options to specify the font and output type of the workflow diagram. See Setting report options, page 377.
Overriding the Workflow

You can override the workflow to move a record to its resulting state. A record can be delayed if it is assigned to multiple users and events can only be entered by the assigned users. If one of the users is out of the office or busy with other tasks, you may want to override the workflow. 1. Open the record you want to override the workflow for. All workflow events are disabled after the record is open. 2. Choose Activities > Override Workflow. The valid events for the current state are enabled. 3. Select an event from the Activities list. The record moves to the resulting state for the selected event. A workflow override entry is recorded and can be viewed on the record Workflow tab.
Resetting the Workflow

If a project does not contain any records, you can reset the workflow. When the workflow is reset all states, events, and transitions except for the default state are removed. Tip: Only reset the workflow if you want to start with an empty workflow. 1. Choose Tools > Administration > Workflow. The Configure Workflow dialog box opens. 2. Click Reset. The Reset button is only visible if there are no records in the project. 3. Click Yes when you are prompted to confirm that you want to reset the workflow. The workflow is reset.
428
Con figu r in g Time Tr ackin g
Configuring Time Tracking

Time tracking data can help you monitor the progress of a release, iteration, or project and capture information for planning and analysis. For example, time tracking data can help you identify the percentage of work complete on a feature, potential schedule overruns, progress on tasks by team members, and the amount of time spent each day on specific items for resource allocation and billing purposes. Users enter time tracking data when they perform activities on items, such as fixing issues. TestTrack groups time tracking values and calculates totals to provide up-to-date information for a project, a segment of a project, or specific items. You can choose the values you want to use to report time tracking totals for issues, requirements, requirement documents, test cases, and test runs. TestTrack can capture and calculate the following time tracking data:
n n n
Estimated hoursThe approximate number of total hours it should take to complete an activity. Actual hoursThe actual number of hours it takes to complete an activity. Remaining hoursThe estimated number of hours it should take to complete an activity from its current state.
Note: Time tracking can also be used to track story points used in Agile development.
Capturing time tracking data

Time tracking values are captured in workflow event dialog boxes, such as the Estimate dialog box. You can use built-in time tracking fields or event custom fields to capture time tracking values based on how you want to report the data.
Built-in workflow event time tracking field

Events have a built-in time tracking field that you can enable. For example, the Estimate event in the default requirement workflow has an Estimated Time field used for time tracking.
To enable the built-in time tracking field, select the Display the time tracking field using option on the Details tab in the Add Event or Edit Event dialog box. See Adding events, page 418.
429
Workflow event custom fields

You can add numeric custom fields to events to capture time tracking values. For example, the Enter Work event in the default workflows has a Remaining Time decimal custom field used for time tracking.
To add custom fields to an event, click the Custom Fields tab in the Add Event or Edit Event dialog box. See Adding events, page 418.
Choosing a time tracking field type

The type of time tracking field you should use depends on how you want to calculate values and if an event can be entered multiple times for an item. The built-in time tracking field provides options for calculating time tracking values. You can use:
n
The sum of all time tracking values entered for all instances of an event for an item. For example, if the Fix event is added to an issue twice and 2 and 6 are entered in the Effort field, the actual hours total is 8. The time tracking value entered for the last instance of the event for an item. For example, if the Estimate event is added to an issue twice and 2 and 6 are entered in the Effort field, the actual hours total is 6.
430
Custom time tracking fields always use the time tracking value from the last instance of the event entered for the item. If items can have multiple instances of the same event, use the built-in time tracking field so you can choose how to calculate the total hours. This is especially important for reporting actual hours because you want a sum of values from all instances of an event to calculate an accurate total. If items can only have one instance of an event, you can use either the built-in field or event custom fields for time tracking. You can use a combination of the built-in field and custom fields in one event to capture multiple time tracking values for the activity. Note: You can use integer custom fields on the Add or Edit item dialog boxes or integer event fields to capture story points values.
Selecting fields to include in time tracking totals

Regardless of the type of time tracking fields you use, you need to select the fields you want to use to calculate actual hours, estimated hours, remaining hours, and story points. You can select the fields to use for each item type in project options.
431
You can select one field or a combination of fields for each calculated value. If multiple fields are selected, the sum of those field values is used as the total. See Setting time tracking options, page 375. Time tracking is automatically configured in new projects based on the default workflows. See Default time tracking fields, page 433. If you modify the default workflows, review the time tracking settings to make they are configured correctly.
Additional time tracking values

TestTrack also automatically calculates additional values based on the estimated, actual, and remaining hours values:
n
Percent doneThe percentage of work completed compared to the remaining hours reported. For example, if the actual hours value for a test case is 5 and the remaining hours value is 4, the percent complete value is 56%. VarianceThe difference between the number of actual hours and remaining hours compared to the estimated hours. For example, if the actual hours value for a test case is 5, the remaining hours value is 2, and the estimated hours value is 8, the variance value is -1. A positive variance indicates an activity is taking more time to complete than the estimate and a negative variance indicates an activity is taking less time to complete.
432
De fau l t t ime t r ackin g fie l d s
Viewing time tracking data

There are several areas in TestTrack where you can view time tracking data. Following are some of the common areas to view this data.
List windows
You can add columns to list windows to display any of the available time tracking values for each item. The Percent Complete column displays a graphical progress bar for each item. You can also display numeric column totals in list windows to see the calculated totals for each column. See Customizing list windows, page 23.
Reports
Several built-in reports include estimated hours, actual hours, remaining hours, percent done, variance, and story points values. In reports, time tracking fields can be summed across all item types to give you a complete picture of the effort required to complete work. See Report types, page 119. Specifically, time tracking reports provide information that helps with tracking and communicating actual work performed by items and users. See Time tracking reports, page 121. You can also create live charts to monitor progress in real time from the Folders list window or a standalone window. See Creating live charts, page 143.
Work Items tab

This tab displays events with time tracking fields that were entered for a specific item. The estimated, actual, and remaining work for an item, and the variance between the estimated and actual hours, is displayed. See Viewing work items, page 44.
Default time tracking fields

The following time tracking fields and options are used for the default workflows.
n
Time tracking valueThe time tracking value that the event time tracking field value is added to. See Setting time tracking options, page 375. EventThe event dialog box that contains the time tracking field. FieldThe field used for time tracking in the event dialog box. Field long labelThe long label for the time tracking field in the event dialog box. This value is selected in the time tracking project options. See Setting time tracking options, page 375. Field typeThe type of time tracking field used in the event dialog box. Built-in indicates that the Display the time tracking field using option is selected for the event. Custom indicates that event custom fields are used. See Adding events, page 418. Built-in field calculationThe built-in time tracking field option selected for the event. Sum of hours from all events of this type uses a sum of all values entered in the time tracking field. Hours from last entered event of this type uses the value entered in the time tracking field in the last instance of the event for the item. See Adding events, page 418.
n n n
433
Issues
Time tracking value Actual hours Event Field Field long label Field type Built-in Built-in field calculation
Enter Work Fix
Actual Effort Effort
Enter Work Actual Effort (Hours) Hours to Fix
Sum of hours from all events of this type Sum of hours from all events of this type Hours from last entered event of this type --
Built-in
Estimated hours Remaining hours
Estimate
Effort
Estimated Effort
Built-in
Enter Work Fix
Remaining Time Remaining Time
Enter Work Remaining Time Fix Remaining Time
Custom
Custom
--
Requirements and requirement documents

Time tracking value Actual hours Event Field Field long label Field type Built-in Built-in field calculation
Enter Work Estimate
Actual Effort Estimated Time Remaining Time
Enter Work Actual Effort (Hours) Estimated Effort
Sum of hours from all events of this type Hours from last entered event of this type --
Built-in
Enter Work
Enter Work Remaining Time
Custom
434
Test cases
Time tracking value Actual hours Event Field Field long label Field type Built-in Built-in field calculation Sum of hours from all events of this type Hours from last entered event of this type Hours from last entered event of this type Hours from last entered event of this type Hours from last entered event of this type --
Enter Work Ready
Actual Effort Actual Effort Actual Effort Actual Effort Estimated Time Remaining Time
Enter Work Actual Effort (Hours) Ready Actual Effort (Hours) Ready for Review Actual Effort (Hours) Reviewed Actual Effort (Hours) Estimated Effort
Built-in
Ready for Review Reviewed
Built-in
Built-in
Estimate
Built-in
Enter Work
Custom
Test runs
Time tracking value Actual hours Event Field Field long label Field type Built-in Built-in field calculation Sum of hours from all events of this type Sum of hours from all events of this type --
Enter Work
Actual Effort
Enter Work Actual Effort (Hours) Enter Result Actual Effort (Hours) Test Run Estimated Run Time Estimated Effort
Enter Result
Actual Effort
Built-in
Estimated hours
--
Estimated run time field on the Edit Test Run window
Custom
Estimate
Estimated Time
Built-in
Hours from last entered event of this type --
Remaining hours
Enter Work
Remaining Time
Custom
435
Con figu r in g Au t omat ion Ru l e s
Configuring Automation Rules

Automation rules help you extend TestTracks functionality to better support your organizations process. In conjunction with TestTrack workflows, automation rules reduce the manual intervention required to keep projects running smoothly. Based on filters, automation rules can be used to automatically enter workflow events, send email, modify fields, enforce rules, and run external applications. You can configure the following types of automation rules:
n
Notification rules email users or customers based on records that pass a filter after an activity is performed on a record. For example, you can configure a rule that emails the QA team lead each time a Fixed event is entered on an issue. See Configuring System Notification Rules, page 438. Trigger rules are evaluated when the TestTrack Server receives a request to save records from TestTrack clients. If the records pass the filter and activity in the trigger rule, actions are performed on the issue, test case, or test run. Triggers can perform actions before or after records are saved in the project database. Before save triggers can prevent users from performing the activity that caused the trigger to run, enter a workflow event, modify record fields, or run a server-side executable. After save triggers can run a server-side executable or create a requirement document snapshot. For example, you can configure a trigger to automatically assign test runs to testers based on the required operating system for testing. See About triggers, page 442. Escalation rules are evaluated based on a schedule. Escalations can enter a workflow event, modify record fields, send email, run a server-side executable, or create a requirement document snapshot. For example, you can configure a rule that is evaluated every Monday morning to modify the Priority field for issues in the same state for more than seven days. See About escalation rules, page 448.
Note: When an automation rule passes and performs an action, a system comment is added to the Workflow tab. If an action enters an event on a record, the event is added to the Workflow tab instead of the system comment. 1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens.
436
Ru n n in g Exe cu t ab l e s fr om Au t omat ion Ru l e s
2. Select a record Type. The items change based on the selected record type. 3. Click the Notifications tab to configure notifications. See Configuring System Notification Rules, page 438. 4. Click the Triggers tab to configure triggers. See Configuring Triggers, page 441. 5. Click the Escalations tab to configure escalations. See Configuring Escalation Rules, page 448. 6. Click OK to save the changes.
Running Executables from Automation Rules

You can add the run executable action to triggers and escalation rules to run a script or compiled program when a rule passes. Before save triggers can run server scripts that perform additional checks. After save triggers and escalation rules can run server scripts that perform additional actions based on saved records. For example, you can create scripts to send record information to an external reporting system. See About triggers, page 442 and About escalation rules, page 448.
n
The executable must be located on the TestTrack Server computer because the server launches the executable. The server administrator needs to make sure that appropriate directory access permissions are set up for the executable. The executable must have the same run privileges as the TestTrack Server. The executable path specified in the run executable action must specify the relative or absolute path to a single file. Multiple files and arguments are not supported.
If TestTrack cannot find the executable, an error message is returned to TestTrack and the action configured in the trigger or escalation rule does not run. Executables that run for before save triggers must return a value that tells the server if records can be saved. A return value of zero means the records should be saved. A non-zero value means the records should not be saved. If a non-zero value is returned, any messages output by the executable (output to stdout) are sent back to TestTrack with the error message. Note that this error message is truncated to 1024 characters. Following are some examples of how to return a value from the triggered executable:
437
Con figu r in g S yst e m N ot ificat ion Ru l e s
From a C program, specify the value in the return() statement in the main() routine. You can also use a parameter in the exit statement. From a Windows/DOS batch file, set the ERRORLEVEL value. From a Windows application, use the CWinApp::ExitInstance() function.
n n
Executables that run for after save triggers and escalation rules do not require a return value and run immediately when the rule passes. You can use environment variables to retrieve data about the item that caused rules to run and pass the data back to the executable. See Environment Variables, page 517. Note: You can configure time out limits and the maximum number of simultaneous processes that can run for executables in the TestTrack Registry Utility.
Configuring System Notification Rules

You can configure system notification rules to email users and customers about changes. Notifications are sent after records are saved in the project database. For example, you may want users to receive an email when a record is assigned to them. Notifications only inform users of changes, they do not assign issues, the record to a user. Note: You can configure escalation rules to send email based on a schedule. See Configuring Escalation Rules, page 448. 1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens with the Notifications tab selected.
2. Select a record Type. The items change based on the selected record type. Notifications are displayed in groups that correspond with the activity that causes the notification to be sent.
438
Note: Notifications are not sent for invalid rules, which are displayed in gray. For example, a notification rule becomes invalid if the filter used in the rule is deleted. You can edit an invalid rule to correct the problem. 3. Click Add to create a notification rule. See Adding system notification rules, page 439. 4. Select a rule and click Edit to change it. See Editing system notification rules, page 440. 5. Select a rule and click Inactivate to inactivate it. See Inactivating system notification rules, page 441. 6. Select a rule and click Delete to delete it. See Deleting system notification rules, page 441. 7. Click OK to save the changes.
Adding system notification rules

1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens with the Notifications tab selected. 2. Select a record Type. The items change based on the selected record type. 3. Click Add to add a rule. The Add Notification Rule dialog box opens with the Precondition tab selected. A rule summary that changes as you configure the rule is displayed in the Summary field.
4. Enter a Rule name. 5. Optionally select a Passes filter. You may want to select a filter if the project contains a large number of records. Click Create Filter to create a new filter. See Adding Filters, page 97. 6. Click the Trigger When tab to specify when the notification is sent.
439
7. Select the activity that causes the notification to be sent. If notifications are configured to be sent when an item is created, they are also sent when items are duplicated. Note: Notifications are not sent if you copy requirements when you duplicate requirement documents. 8. Click the Actions tab to configure the send email action.
n n n
Click Add to add an action. See Adding automation rule actions, page 453. Select an action and click Edit to change it. See Editing automation rule actions, page 458. Select an action and click Delete to delete it. See Deleting automation rule actions, page 458.
9. Click OK. The rule is added.
Editing system notification rules

You can edit notification rules, but cannot change the activity selected on the Trigger When tab. 1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens with the Notifications tab selected. 2. Select a record Type. The items change based on the selected record type. 3. Select a rule and click Edit. The Edit Notification Rule dialog box opens. 4. Make any changes and click OK.
440
Con figu r in g Tr igge r s
The changes are saved.
Inactivating system notification rules

You can inactivate a rule if it is not used. You can activate the rule if you decide to use it again. 1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens with the Notifications tab selected. 2. Select a record Type. The items change based on the selected record type. 3. Select a rule and click Inactivate. The rule is inactivated. Note: To activate an inactive rule, select the rule and click Activate.
Deleting system notification rules

You may want to delete notification rules that are no longer used. 1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens with the Notifications tab selected. 2. Select a record Type. The items change based on the selected record type. 3. Select a rule and click Delete. You are prompted to confirm the deletion. 4. Click Yes. The rule is deleted.
Configuring Triggers
1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens. 2. Click the Triggers tab.
441
Ab ou t t r igge r s
3. Select a record Type. The items change based on the selected record type. Triggers are displayed in groups that correspond with the activity that causes the trigger to run. Within each group, before save triggers are displayed, followed by the default trigger for the activity, and after save triggers. Note: Triggers do not run for invalid rules, which are displayed in gray. For example, a trigger becomes invalid if the filter used in the rule is deleted. You can edit an invalid rule to correct the problem. 4. Click Add to create a trigger. See Adding triggers, page 444. 5. Click Add Default to create a default trigger. See Adding default triggers, page 446. 6. Select a trigger and click Edit to change it. See Editing triggers, page 447. 7. Select a trigger and click Inactivate to inactivate it. See Inactivating triggers, page 447. 8. Select a before save trigger and click Top, Move Up, Move Down, or Bottom to reorder it. The default trigger and after save triggers cannot be reordered. 9. Select a trigger and click Delete to delete it. See Deleting triggers, page 447. 10. Click OK to save the changes.
About triggers
Triggers automatically perform actions based on activities that occur on records, such as issues. The TestTrack Server evaluates trigger rules when it receives a request to save records from TestTrack clients. For example, if a user makes changes in the Edit Issue dialog box, the trigger rule is evaluated when the user clicks OK or Apply to save the changes. If a record passes the filter and activity in the trigger rule, the trigger runs and performs the action. Triggers can perform actions before or after records are saved in the project database. Triggers can run when the following activities occur:
442
Records are created Test runs are generated Records change Records change state Actions (workflow events) are added, edited, or deleted
Issues are merged Records are assigned Specific actions are added to records Records enter a specific state
Keep the following in mind:

n n
Triggers run in the order that the events occur on records. If the same event type occurs on a record multiple times before saving, trigger rules for that event only run once.
About before save triggers

Before save triggers perform actions when the TestTrack Server receives a request to save records, but before the records are saved in the project database. Before save triggers can perform the following actions:
n n n n n
Enter a workflow event Modify the record field values Prevent users from performing an activity Run a server-side executable (script or compiled program) Create a requirement document snapshot
About after save triggers

After save triggers perform actions after records are saved in the project database. After save triggers can run a server-side executable (script or compiled program) or create a requirement document snapshot.
Trigger examples
Following are examples of common actions you can automate with triggers: Automatically assign records based on workflow stateYou want all issues in the Fixed state to be assigned to a specific tester for verification. You can configure a trigger that assigns Fixed issues to the appropriate tester. Automatically assign records based on a field valueYou want new test runs for a specific product on the Mac OS X platform to be assigned to a specific tester to run. You can create a filter that returns test runs with the product selected in the Product field and Mac OS X in the Operating System field. You can then create a trigger based on the filter that assigns the new test runs to the tester.
443
Prevent users from saving a record without file attachmentsYou want users to attach a screenshot when they add cosmetic issues. You can create a filter that returns issues with Cosmetic selected in the Type field that do not have attachments. You can then create a trigger based on the filter that prevents users from saving issues and display a message to explain that a screenshot must be attached to the issue. Prepend a record summary with information based on a field selectionYou want to add a value to the beginning of each test case summary that identifies the functional area the test case applies to. You can create filters for each value in the Component field. You can then create triggers based on the filters that prepend the functional area in the Summary field value when test cases are created. Send record information to an external reporting systemYou want to send issue information to an external reporting system after issues about a specific product are added to the project. You can create a filter that returns issues with the product selected in the Product field. You can then create a trigger based on the filter to run a script that sends the information to the reporting system after issues are saved. Create a requirement document snapshot when a document is approvedYou want to create a requirement document snapshot when it is approved to capture a version of the document for historical purposes. You can configure a trigger to create the snapshot when the document moves to the Approved workflow state.
Adding triggers
1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens. 2. Click the Triggers tab. 3. Select a record Type. The items change based on the selected record type. 4. Click Add. The Add Trigger Rule dialog box opens with the Precondition tab selected. A trigger summary that changes as you configure the trigger is displayed in the Summary field.
5. Enter a Rule name. 6. Optionally select a Passes filter. You may want to select a filter if the project contains a large number of records.
444
Click Create Filter to create a filter. See Adding Filters, page 97. Note: Triggers that perform an action when a record is created do not run if the selected filter contains restrictions on the Number field because numbers are not assigned until records are saved. 7. Select Apply this rule to items imported from a text or XML file to run the trigger when records are imported into the project from a text or XML file. 8. Click the Trigger When tab to specify when the trigger runs.
n
Select Before save to perform actions before records are saved in the project database. Select Do not process additional rules if this rule passes if you do not want to pass subsequent rules if this rule passes. See About triggers, page 442. Select After save to perform actions after the record is saved in the project database. See About triggers, page 442. Select the activity that causes the trigger to run. If triggers are configured to run when an item is created, they also run when items are duplicated.
Note: Triggers do not run if you choose to copy requirements to duplicated requirement documents. 9. Click the Actions tab to select the actions to perform when the trigger runs. You can add the following actions for before save triggers: enter event, modify, prevent, create snapshot, and run executable. You can add the run executable and create snapshot action for after save triggers. The create snapshot action only applies to requirement document triggers.
n n n
Click Add to add an action. See Adding automation rule actions, page 453. Select an action and click Edit to change it. See Editing automation rule actions, page 458. Select an action and click Delete to delete it. See Deleting automation rule actions, page 458. Note: You can only configure one action of each type per rule. For example, you cannot add two Prevent actions to one trigger.
445
10. Click OK. The trigger is added.
Adding default triggers

You can configure a default trigger to perform actions on records that are not acted on by other triggers. Default triggers run before records are saved in the project database, after all other trigger rules are evaluated. For example, a product is in beta testing and you want to make sure that failed issues get immediate attention. You configured a trigger to automatically assign an issue when it fails verification. If the issue passes the Failed Fix filter, it is assigned to the last Fixed By user. You can configure a default trigger to assign the issue to another user if it does not pass the Failed Fix filter. Note: You can only add one default trigger per activity. 1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens. 2. Click the Triggers tab. 3. Select a record Type. The items change based on the selected record type. 4. Click Add Default. The Add Trigger Rule dialog box opens with the Precondition tab selected. Note: The rule name is <default> and it cannot be changed. 5. Optionally select a Passes filter. You may want to select a filter if the project contains a large number of records. Click Create Filter to create a filter. See Adding Filters, page 97. 6. Select Apply this rule to items imported from a text or XML file to run the trigger when records are imported into the project from a text or XML file. 7. Click the Trigger When tab to specify when the trigger runs. 8. Select the activity that causes the trigger to run. 9. Click the Actions tab to select the actions to perform when the trigger runs. You can add the following actions: enter event, modify, prevent, and run executable.
n n
Click Add to add an action. See Adding automation rule actions, page 453. Select an action and click Edit to change it. See Editing automation rule actions, page 458.
446
Select an action and click Delete to delete it. See Deleting automation rule actions, page 458. Note: You can only configure one action of each type per rule. For example, you cannot add two Prevent actions to one trigger.
10. Click OK. The default trigger is added.
Editing triggers
You can edit triggers, but cannot change the Before save or After save option or the activity selected on the Trigger When tab. 1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens. 2. Click the Triggers tab. 3. Select a record Type. The items change based on the selected record type. 4. Select a trigger and click Edit. The Edit Trigger Rule dialog box opens. 5. Make any changes and click OK. The changes are saved.
Inactivating triggers
You can inactivate a trigger if it is not used. You can activate the trigger if you decide to use it again. 1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens. 2. Click the Triggers tab. 3. Select a record Type. The items change based on the selected record type. 4. Select a rule and click Inactivate. The trigger is inactivated. Note: To activate an inactive trigger, select the trigger and click Activate.
Deleting triggers
You may want to delete triggers that are no longer used. 1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens. 2. Click the Triggers tab. 3. Select a record Type. The items change based on the selected record type. 4. Select a trigger and click Delete.
447
Con figu r in g Escal at ion Ru l e s
You are prompted to confirm the deletion. 5. Click Yes. The trigger is deleted.
Configuring Escalation Rules

1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens. 2. Click the Escalations tab.
3. Select a record Type. The items change based on the selected record type. Note: Escalation rules do not run for invalid rules, which are displayed in gray. For example, an escalation rule becomes invalid if the filter used in the rule is deleted. You can edit an invalid rule to correct the problem. 4. Click Add to create an escalation rule. See Adding escalation rules, page 449. 5. Select a rule and click Edit to change it. See Editing escalation rules, page 451. 6. Select a rule and click Inactivate to inactivate it. See Inactivating escalation rules, page 452. 7. Select a rule and click Delete to delete it. See Deleting escalation rules, page 452. 8. Click OK to save the changes.
About escalation rules

Escalation rules automatically perform actions based on a specified time frame. Escalation rules are evaluated on a daily, weekly, or monthly schedule. You can also manually evaluate rules to perform actions on records that pass the rule immediately. See Configuring Escalation Rules, page 448. Escalation rules can perform the following actions:
n n
Enter a workflow event Modify the record field values
448
n n n n
Send an email to users or customers Run a server-side executable (script or compiled program) Create a requirement document snapshot Recalculate custom field values
Note: If the TestTrack Server is not available when rules are scheduled for evaluation, they are evaluated after the server is started and the project loads.
Escalation rule examples

Following are some common uses for escalation rules: Raise the priority of issuesEvery Monday, you want to change the value in the Priority field for open customer issues to make sure urgent issues are addressed within your service level agreements. You can create a filter for each value in the Priority field. You can then create escalation rules based on each filter to change the priority to the next highest level every Monday. Automatically assign issues that have not been modified within a time frameEvery Friday, you want to assign high priority issues that have not been modified in the last seven days to the development manager. You can create a filter that returns issues with High selected in the Priority field. You can then create an escalation rule based on the filter that assigns high priority issues to the development manager at a specific time every Friday. Email testers about aged test run assignmentsYou want to notify testers if test runs assigned to them are not complete within 10 days. You can create a filter that returns test runs with an Assign event entered within the past 10 days. You can then create an escalation rule based on the filter that emails a reminder to the tester. Send aged issue information to an external reporting systemAt the end of the month, you want to send information about open issues for a specific product to an external reporting system. You can create a filter that returns open issues with the product selected in the Product field. You can then create an escalation rule based on the filter that runs a script every month to send information to the reporting system.
Adding escalation rules

1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens. 2. Click the Escalations tab. 3. Select a record Type. The items change based on the selected record type. 4. Click Add. The Add Escalation Rule dialog box opens with the Precondition tab selected. A rule summary that changes as you configure the rule is displayed in the Summary field.
449
5. Optionally select a Passes filter. You may want to select a filter if the project contains a large number of records. Click Create Filter to create a filter. See Adding Filters, page 97. Note: Escalation rules do not run if the selected filter contains includes <Current User> restrictions. The TestTrack Server performs escalations as the System user, which is the current user when escalations run. 6. Click the Schedule tab to specify when the rules are evaluated.
7. Select the frequency to Evaluate the rule.

n
Daily evaluates the rule every day at a specified time or number of hours. To evaluate the rule at a specific time, select Start time and enter the time. To evaluate the rule on an hourly basis, select the hours option and enter the number of hours between each evaluation. Weekly evaluates the rule at a specified time on specified days each week. Enter the Start time and select the days to evaluate the rule.
450
Monthly evaluates the rule at a specified time during specified months. Enter the Start time to evaluate the rule. To evaluate the rule on a specific day of the month, select On this day and enter the day number. To evaluate the rule on a specific day based on a pattern (first, second, third, fourth, or last day of the month), select a pattern option and then select the pattern and day. Select the Months to evaluate the rule. Manually only evaluates the rule when you select the Run Now check box on the Escalations tab in the Configure Automation Rules dialog box. See Manually running escalation rules, page 452. Note: You cannot change the evaluation order of multiple escalation rules. If an activity has multiple rules that are evaluated based on the result of another rule, you may want to change the time that each rule is evaluated. For example, evaluate one rule at 10:00 and the next rule at 10:01.
8. Click the Actions tab to select the actions to perform when the rule passes. You can add the following actions: enter event, modify, send email, run executable, recalculate fields, and create snapshot. The create snapshot action only applies to requirement document triggers. See Adding automation rule actions, page 453.
Note: You can only configure one action of each type per rule. For example, you cannot add two send email actions to one rule. 9. Select Inactivate rule after it runs once to inactivate the rule so it does not run again after the first time it runs. 10. Select This rule should only be applied once per item to apply the escalation rule once per record. You may want to select this option if the rule is evaluated frequently. 11. Click OK. The rule is added.
Editing escalation rules

1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens. 2. Click the Escalations tab. 3. Select a record Type. The items change based on the selected record type. 4. Select an escalation rule and click Edit. The Edit Escalation Rule dialog box opens. 5. Make any changes and click OK.
451
The changes are saved.
Manually running escalation rules

You can manually run escalation rules if you need to evaluate a rule outside of the configured schedule. If you manually run a rule, it is still evaluated at the next scheduled time. 1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens. 2. Click the Escalations tab. 3. Select a record Type. The items change based on the selected record type. 4. Select the Run Now check box for each rule you want to evaluate manually. 5. Click OK to save the escalation rule changes. 6. Click OK to save the automation rule changes. The escalation rules you selected are evaluated.
Inactivating escalation rules

You can inactivate an escalation rule if it is not used. You can activate the rule if you decide to use it again. 1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens. 2. Click the Escalations tab. 3. Select a record Type. The items change based on the selected record type. 4. Select an escalation rule and click Inactivate. The rule is inactivated. Note: To activate an inactive escalation rule, select the rule and click Activate.
Deleting escalation rules

You may want to delete escalation rules that are no longer used. 1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens. 2. Click the Escalations tab. 3. Select a record Type. The items change based on the selected record type. 4. Select an escalation rule and click Delete. You are prompted to confirm the deletion. 5. Click Yes. The rule is deleted.
452
Con figu r in g Au t omat ion Ru l e Act ion s
Configuring Automation Rule Actions

Rule actions are performed when a notification, trigger, or escalation rule passes. You can use the following actions in automation rules, depending on the valid actions for the rule.
n n n n n n
Prevent Enter event Modify Send email Run executable Create snapshot (requirement documents only)
You can only add one action to each rule. If you want TestTrack to perform multiple actions of the same type, configure multiple rules for each activity. For example, to send different emails to multiple recipients when an issue changes, you can configure multiple rules for the Issue is created action, each with a different email and recipients.
Adding automation rule actions

1. Select the action you want to add from the Action list in the Add Rule Action dialog box. 2. Enter or select the action options. The option changes based on the selected action. Note: Tracking automated emails requires more storage space on the server and will result in slower performance. 3. Click OK to add the action.
Prevent action
The prevent action prevents users from performing an activity and displays a message to inform them why they cannot perform the activity. You can add this action to before save triggers. 1. Select Prevent from the Action list in the Add Rule Action dialog box.
2. Enter the Message to display when users attempt to perform the event. 3. Click OK to add the action.
453
Note: If a rule with a prevent action passes, subsequent rules are not evaluated and the record is not saved.
Enter event action

The enter event action enters a workflow event on records. You can add this action to before save triggers and escalation rules. This rule action is used to auto-assign items to users. Note: If the event is not valid based on the configured workflow, the event is not added to the record and a warning is added to the automation rules log. 1. Select Enter event from the Action list in the Add Rule Action dialog box.
2. Select the Event to enter. 3. Select Assign Options if the event results in a new assignment.
n n n
Make it unassigned removes the current assignment. Assign to the Entered by user assigns the record to the user who entered the record. Assign to Found by users assigns the record to all Found by users, the first Found by user, or the last Found by user. Assign to the last user to enter an event assigns the record to the last user who entered the event. If the user entered the event in response to a multi-user assignment, the record is assigned to all users who responded. Assign to the following users assigns the record to the selected users or customers. Click the Find button to search for users. See Finding users and customers, page 39.
454
Assign to the following list of users assigns the record to users in the selected custom field list. Only enter this event if the item being processed is unassigned enters the event if the record is not assigned when the rule is evaluated.
4. Click OK to add the action.
Modify action
The modify action changes record field values. This action can only modify general and custom field values. You can add this action to before save triggers and escalation rules. 1. Select Modify from the Action list in the Add Rule Action dialog box.
2. Make any changes. The available options depend on the field type.
n n n n
To set the field to a new value, select Set to value and enter a value. To add text to the beginning of a text field value, select Prepend and enter the text. To add text to the end of a text field value, select Append and enter the text. To replace a text field value, select Replace and enter the text you want to search for. Enter the replacement text in the With field. Note: The Custom Fields tab is displayed if custom fields are configured for the project.
3. Click OK to add the action.
455
Run executable action

The run executable action runs a script or compiled program if a rule passes. You can add this action to before save triggers, after save triggers, and escalation rules. See Running Executables from Automation Rules, page 437. 1. Select Run executable from the Action list in the Add Rule Action dialog box.
2. 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. 3. Click OK to add the action.
Send email action

The send mail action emails users and customers. You can add this action to notifications and escalation rules. 1. Select Send email from the Action list in the Add Rule Action dialog box.
456
2. Select a Recipient.
n n n
Send to the Entered by user emails the user who entered the record. Send to the currently assigned users emails all currently assigned users. Send to Found by users emails all Found by users, the first Found by user, or the last Found by user. Send to Modified by users emails all Modified by users, the first Modified by user, or the last Modified by user. Send to the last user to enter an event emails the user who last entered the selected event. The list includes all events defined for the workflow. If the last user entered the event in response to a multi-user assignment, the notification is sent to all users who responded. Send to the following users emails the selected users or customers. Click the Find button to search for users. See Finding users and customers, page 39. Send to the following groups emails the selected group. Send to the following list of users emails users in the selected custom field list.
n n
3. Select an email Template. Users can view all information in the email. Do not select a template that includes restricted information. Note: When email templates are created, you can set template access options. These options are ignored when notification rules are created. Depending on who the notification is sent to, you may not want to select an email template that includes sensitive information. 4. Select Do not send email if current user made the change if you do not want to email the user who made the change. This option is only available for notification rules. 5. Select Only send email to currently assigned users if you only want the currently assigned users to receive an email. 6. Select Track sent emails to add the sent email to the corresponding record. Email tracking must be enabled for the project. See Setting email options, page 359. 7. Click OK. The action is added.
Create snapshot action

The create snapshot action automatically creates a requirement document snapshot. See Creating Requirement Document Snapshots, page 230. You can add this action to before save triggers, after save triggers, and escalation rules created for requirement documents. 1. Select Create snapshot from the Action list in the Add Rule Action dialog box.
457
Vie win g t h e Au t omat ion Ru l e s Log
2. Enter the Label to summarize the purpose of the snapshot or project milestone it corresponds with. 3. Click OK to add the action.
Editing automation rule actions

You can edit rule actions, but you cannot change the selected action. 1. Select an action on the Actions tab in a system notification, trigger, or escalation rule. 2. Click Edit. The Edit Rule Action dialog box opens. 3. Make any changes. Note: Tracking automated emails requires more storage space on the server and will result in slower performance. 4. Click OK to save the changes.
Deleting automation rule actions

1. Select an action on the Actions tab in a system notification, trigger, or escalation rule. 2. Click Delete. You are prompted to confirm the deletion. 3. Click Yes. The action is deleted.
Viewing the Automation Rules Log

The TestTrack Server records information about automation rules. You can use this information to monitor manually evaluated rules and troubleshoot rules that did not perform actions. For example, if a user is editing a record when a rule passes, the action is not performed and an error is added to the rules log. 1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens. 2. Click Rules Log. The Automation Rules Log dialog box opens.
458
Vie win g t h e Au t omat ion Ru l e s Log
3. Select a record Type. The items change based on the selected record type. 4. Select the entry you want to view. The details are displayed in the Selected Log Entry area. 5. Click Go to Rule to edit the corresponding rule. See Editing system notification rules, page 440, Editing triggers, page 447, or Editing escalation rules, page 451. 6. Click OK to close the Automation Rule Log dialog box.
Exporting the automation rules log

You can export the log file to a text file for analysis or report generation with other tools. 1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens. 2. Click Rules Log. The Automation Rules Log dialog box opens. 3. Select a record Type. The items change based on the selected record type. Rules are only exported for the selected record type. 4. Click Export Log. The Export File dialog box opens. 5. Choose a Save in location, enter a File name, and click Save. The log file is exported and saved as a text file.
Deleting automation rules log entries by date

You can safely delete log entries if you are not experiencing any problems. 1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens. 2. Click Rules Log. The Automation Rules Log dialog box opens.
459
Con figu r in g It e m M ap p in g Ru l e s
3. Select a record Type. The items change based on the selected record type. Rules are only deleted for the selected record type. 4. Click Delete by Date. The Delete Log Entries dialog box opens.
5. Enter a Date and click OK. You are prompted to confirm the deletion. 6. Click Yes. Any entries that occurred prior to and on the date you entered are deleted from the rules log.
Deleting all automation rules log entries

You can safely delete log entries if you are not experiencing any problems. 1. Choose Tools > Administration > Automation Rules. The Configure Automation Rules dialog box opens. 2. Click Rules Log. The Automation Rules Log dialog box opens. 3. Select a record Type. The items change based on the selected record type. Rules are only deleted for the selected record type. 4. Click Delete All. You are prompted to confirm the deletion. 5. Click Yes. The entries are deleted from the rules log.
Configuring Item Mapping Rules

You can configure item mapping rules to specify how field values are copied into items created from other items, such as issues created from test runs, and how items are linked. These rules allow you to copy additional information between items and offer more flexibility when copying values from custom fields. For example, you can map a custom test run pop-up menu field to any issue field without creating a custom issue pop-up menu. Keep the following in mind:
460
Con figu r in g It e m M ap p in g Ru l e s
You can map item fields of the same type. For example, you can map test run text fields to issue text fields. You can also map pop-up menu, integer, and date/time fields to text fields. If a text field's limit is exceeded, the data is truncated to the field limit. To map two pop-up menu fields, the fields must use the same value list. You can map multiple fields to one field in new items. For example, you can map the test run Summary and Steps fields to the issue Description field to include the information from both test run fields in the issue Description. You can select Folders as the field to copy to a new item. Folders can only be mapped to text fields. If the Folders field is mapped to a single-line text field, a list of folder names is copied to the new item. If the Folders field is mapped to a multi-line text field, a list of folder paths is copied to the new item. You can map decimal fields to integer fields. When an item is created from another item and the Add dialog box opens, the decimal value copied into the integer field must be changed before the new item can be added. When an item is generated from an item and automatically added to the project, the decimal value copied to the integer field is accepted. If the generated item is edited, users are notified that the decimal value is invalid and must be changed before the changes can be saved. You can map calculated custom fields as the source field to copy to new items. but these fields cannot be selected as the field to be populated.
1. Choose Tools >Administration >Item Mapping Rules. The Configure Item Mapping Rules dialog box opens.
2. Select a rule Type. 3. Click Add to create a new rule. See Adding item mapping rules, page 464. 4. Select a rule in the Custom Mappings list to modify it. See Editing item mapping rules, page 465. 5. Select a rule and click Top, Move Up, Move Down, or Bottom to organize the field order.
461
De fau l t it e m map p in g r u l e s
If multiple fields are mapped to the same field in a new item, the values are added in the order they appear in the Custom Mappings list. 6. Click Restore Default Values to restore the default mapping rules. See Default item mapping rules, page 462. 7. Select a rule and click Delete to delete it. 8. Click Export to export the item mapping rules. See Exporting item mapping rules, page 465. 9. Click Import to import the item mapping rules. See Importing item mapping rules, page 466. 10. Click OK to save the changes.
Default item mapping rules

The following default rules are used to copy field values to items created from other items and link items using the default link definitions. See About default link definitions, page 471. These rules can be edited but not deleted. Note: Custom fields with the same name and field type are included in the default mapping rules.
Create Test Case from Issue

The Related Items link definition is used to link test cases and issues. Users are prompted before adding the link. The new test case is not added to the same folders as the issue. Issue field Steps to Reproduce Summary Maps to test case field Steps Notes Steps from the first record are copied from issues with multiple reported by records. The Issue Label and Number are prepended to the field value.
Summary
Create Requirement from Issue

The Requirement Source link definition is used to link requirements and issues. Users are prompted before adding the link. The new requirement is not added to the same folders as the issue. Issue field Summary Maps to requirement field Summary Notes The Issue Label and Number are prepended to the field value.
Create Issue from TestRun

The Related Items link definition is used to link test runs and issues. Users are prompted before adding the link. The new issue is not added to the same folders as the test run.
462
De fau l t it e m map p in g r u l e s
Test run field Summary Summary
Maps to issue field Summary Description
Notes The Issue Label and Number are prepended to the field value. The Issue Label, Test Run Label, and Test Run Number are prepended to the field value. The Test Run Label and Number are prepended to the field value.
Steps
Steps to Reproduce
Create Issue from Requirement

The Requirement Source link definition is used to link issues and requirements. Users are prompted before adding the link. The new issue is not added to the same folders as the requirement. Requirement Maps to field issue field Summary Summary Summary Description Notes The Requirement Label and Number are prepended to the field value. The Issue Label, Requirement Label, and Requirement Number are prepended to the field value.
Generate Test Runs from Test Cases

Test case field Steps Maps to test run field Steps Notes
Test case steps are always copied when generating test runs. This rule is not included in the custom mappings list and cannot be changed.
Summary Description Scope PreConditions Expected Results
Summary Description Scope PreConditions Expected Results
Generate Test Cases from Requirements

The Requirement Tested By link definition is used to link test cases and requirements. Users are prompted before adding the link.
463
Ad d in g it e m map p in g r u l e s
Requirement field Summary
Maps to test case field Summary
Notes The Requirement Label and Number are prepended to the field value.
Insert Shared Steps in Test Case

The Shared Test Case Steps link definition is used to link test cases. Users are not prompted before adding the link.
Adding item mapping rules

You can add item mapping rules to copy information to an item created from another item. See Configuring Item Mapping Rules, page 460. 1. Choose Tools >Administration >Item Mapping Rules. The Configure Item Mapping Rules dialog box opens.
2. Select a rule Type. The available options depend on the type of rule you are configuring. 3. Click Add. A new row is added to the Custom Mappings list.
n
Select a field to copy from the Copy Field list. The field value in the source item is copied to the field it is mapped to in the new item. Note: You must select a field to copy before setting other mapping options.
464
Ed it in g it e m map p in g r u l e s
Select a field to map the source field to from the to Field list. This field in the new item is populated with the value from the source item field. Optionally enter text or field codes in the Prepend Text and Append Text fields. You can only prepend and append text to values that are mapped to text fields. Click the Insert Field Code button to select from a list of available field codes.
4. Select Copy all issue reported by description fields to requirement description to copy information from the issue Detail:Found by mini tab to the requirement Description. This option is only available for Create Requirement fromIssue rules. If you map an issue reported by field with multiple records, only fields from the first record will be used if this option is not selected. 5. Select Copy test run problems statements to issue description to copy information from the test run Steps tab to the issue Description. This option is only available for Create Issue from Test Run rules. 6. Select a Link definition to use when a new item is created from an existing item. The list includes all link definitions that allow linking of the two item types. Select Prompt user before adding link to prompt users to create a link when creating new items from existing items. If this option is not selected, the link is automatically created. The selected link definition is always used. See Linking Items, page 77. 7. Select Add the new item to the same folders option to add new items to the same folders as the source items. When the new item is created, users can open the folder or remove the item from the folder on the Folders tab. 8. Click OK to save the changes.
Editing item mapping rules

You can edit an item mapping rule to change which fields are mapped to each other, prepend or append text to include with copied values, or change the linking options. 1. Choose Tools >Administration >Item Mapping Rules. The Configure Item Mapping Rules dialog box opens. 2. Select a rule Type. 3. Select a rule in the Custom Mappings list and make any changes. 4. Click OK to save the changes.
Exporting item mapping rules

You can export item mapping rules to an XML file. You may want to do this after configuring rules to easily import them into other TestTrack projects. See Importing item mapping rules, page 466. 1. Choose Tools >Administration >Item Mapping Rules. The Configure Item Mapping Rules dialog box opens. 2. Click Export. The Item Mapping Rules Export dialog box opens.
465
Imp or t in g it e m map p in g r u l e s
3. Choose a Save in location, enter a File name, and click Save. The item mapping rules are exported and saved as anXML file.
Importing item mapping rules

You can import item mapping rules exported to an XML file from another TestTrack project. 1. Choose Tools >Administration >Item Mapping Rules. The Configure Item Mapping Rules dialog box opens. 2. Click Import. The Item Mapping Rules Import dialog box opens. 3. Select the XML file that contains the rules and click Open. You are prompted to confirm replacing the current rules. 4. Click Yes to import the rules. 5. Click OK to save the changes.
Customizing Email Templates

TestTrack includes standard templates that can be customized. You can also create templates. Email templates are used when notifications are sent to users and when confirmation messages are sent to users and customers who submit items via email. 1. Choose Tools > Administration > Email Templates. The Configure Email Templates dialog box opens. 2. Select a record Type. The items change based on the selected record type.
466
Ad d in g e mail t e mp l at e s
3. Select a template and click View to view it. See Viewing email templates, page 470. 4. Click Add to create a template. See Adding email templates, page 467. 5. Select a template and click Edit to change it. See Editing email templates, page 470. 6. Select a template and click Delete to delete it. See Deleting email templates, page 470.
Adding email templates

1. Choose Tools > Administration > Email Templates. The Configure Email Templates dialog box opens. 2. Click Add. The Add Email Template dialog box opens with the Format tab selected.
3. Enter a Name and Description. 4. Enter a Subject. You can enter text and use field codes to customize the subject line. 5. Select Send email in HTML format to send HTML-formatted email. If you select this option and want to use email notification hyperlinks, see Configuring Notification Hyperlinks, page 475. 6. Select a View option. This option is available if you selected the HTML format option.
n
Layout displays the email template in rich text format. Use the style and formatting options to change the format of the email.
467
Ad d in g e mail t e mp l at e s
HTML displays the email template in HTML code. You can add HTML tags to change the format of the email.
7. Enter the Message body.

n
To insert a field code in the message body, click Insert Field Code. Enter the first few letters of a field name in the Search field to display matching field codes. Select a code from the list and click OK. See Using field codes in email templates, page 469. If the email template is in HTML format, you can import a text or HTML file as the message body. The imported file replaces any existing text in the message body field. Click Import, select a file, and click Open. The file contents are added to the message body. Note: Any field added to a template can be viewed by all email recipients, regardless of security settings. Field-level security settings are enforced when users send email. If the email uses a template, fields hidden for the email sender are not displayed.
8. Click the Options tab.
9. Select a Template Access option.

n
Select All users can view this template if you do not want to restrict users from viewing the template. Select Only allow users in the following groups to view this template then choose the security groups that you want to have access to the template. Users who do not belong to the security groups cannot view or select the template when they set up notification rules or send email. Note: Users can still receive email notifications that use a restricted template. If you restrict template access, make sure that users who can access it understand the type of information it contains and what it is used for. For example, you create a template to notify managers about sensitive information. You also restrict template access to the manager security group to ensure that other employees cannot select it. However, other employees can still receive an email that uses the restricted template.
10. Select a Recipient list for email notifications option. Do not select Each email contains multiple recipients (can see who received mail) if you are using email notification hyperlinks with this template. The same email cannot be sent to multiple recipients because each recipient requires a unique cookie. 11. Click OK.
468
U sin g fie l d cod e s in e mail t e mp l at e s
The email template is added.
Using field codes in email templates

You can use field codes in email templates to dynamically populate emails with specific information about the record that triggered a notification or, in the case of an email acknowledgment, was imported via email. When an email is sent, field codes, which are enclosed in percent signs (%), are replaced with the corresponding data from a record. See Field Codes, page 529 for a list of field codes. For example, the following email template is used for emails sent when test cases are assigned.
When the email is sent, the field codes in the template are replaced with the following information. Field code %TCUS_L% %TCNUM% %TCDTM% %TCSUM_L% %TCSUM% %TCTYP_L% %TCTYP% Replaced with: Test case label Test case number Test case modified date Test case Summary field label Test case Summary field value Test case Type field label Test case Type field value
When a test case is assigned, information similar to the following example is included in the sent email.
Tip: You can use the %CHNGHTML% field code in HTML email templates to include details about field changes in issues, requirements, requirement documents, test cases, and test runs. Content added to fields is displayed in green text and content removed from fields is displayed in red strikethrough text, making it easy to see the exact changes. This field code is only replaced in email sent from user or system notifications. You can also use field codes in email subject lines. For example, 'Change to %SUMM%' results in a subject of 'Change to' appended with the issue Summary field value.
469
Vie win g e mail t e mp l at e s
To insert a field code in an email template, click Insert Field Code. Select a code in the Select Field dialog box and click OK.
Viewing email templates

1. Choose Tools > Administration > Email Templates. The Configure Email Templates dialog box opens. 2. Select an email template and click View. The View Email Template dialog box opens. 3. Click OK when you finish viewing the template.
Editing email templates

1. Choose Tools > Administration > Email Templates. The Configure Email Templates dialog box opens. 2. Select an email template and click Edit. The Edit Email Template dialog box opens. 3. Make any changes and click OK. The changes are saved.
Deleting email templates

1. Choose Tools > Administration > Email Templates. The Configure Email Templates dialog box opens. 2. Select an email template and click Delete. You are prompted to confirm the deletion. 3. Click Yes. The template is deleted.
Configuring Link Definitions

You must configure link definitions before users can link items. The sample TestTrack projects and each new project you create includes default link definitions. Many companies can use the default link definitions. See About default link definitions, page 471. 1. Choose Tools > Administration > Link Definitions. The Configure Link Definitions dialog box opens. Existing link definitions are displayed.
470
Con figu r in g Lin k De fin it ion s
2. Click Add to create a new link definition. See Adding link definitions, page 472. 3. Select a link definition and click Edit to change it. See Editing link definitions, page 474. 4. Select a link definition and click Inactivate to inactivate it. See Inactivating link definitions, page 475. 5. Select a link definition and click Delete to delete it. Deleting link definitions, page 475. 6. Click OK to save the changes.
About default link definitions

Items, such as requirements and test cases, are linked using link definitions. A link definition specifies the type of relationship to establish between items, the item types and number of items allowed in a link, and optional behaviors that restrict the workflow of linked items. The available default link definitions and items allowed in definitions depend on the TestTrack products you are using. For example, if you use TestTrack Pro and TestTrack TCM, you can create link definitions for linking issues, test cases, and test runs. None of the default link definitions have workflow restrictions. Note: If you have administrative privileges, you can modify the default link definitions or add new ones. See Configuring Link Definitions, page 470. Link definition Allowed item types Relationship Relationship restrictions type Allow marking dependent items as suspect? No
Parent/Child
Issues, test cases, test runs Issues, test cases, test runs
Parent/child
Use any item type as parent or child items --
Related Items
Peer
No
471
Link definition
Allowed item types
Relationship Relationship restrictions type
Allow marking dependent items as suspect? Yes
Related Requirements Requirement Source
Requirements
Peer
--
Issues, requirements, requirement documents, test cases, test runs Requirements, test cases
Peer
--
Yes
Requirement Tested By
Parent/child
Parent items must be requirements and child items must be test cases Parent items must be test cases and child items must be test cases. Can only link two test cases.
Yes
Shared Test Case Steps
Test cases
Parent/child
Yes
Adding link definitions

Create a link definition to allow users to establish relationships between specific item types, such as test cases and requirements, and to control how linked items are handled in the workflow. You can create link definitions to allow parent/child or peer relationships between items. Items linked in a parent/child relationship have one item that is the parent item and other related items are children. Items linked in a peer relationship have a common element, but do not have a defined hierarchical relationship. There may be an advantage to working on both items at the same time, but one item is not more important than the other. 1. Click Add on the Configure Link Definitions dialog box. The Add Link Definition dialog box opens.
472
2. Enter a Name and Description. The definition name must be unique. 3. Choose the item types to allow in links that use the definition. 4. Select any General Options.
n n
Select Require a link comment to require users to enter a comment when linking items. Select Allow dependent items to be marked as suspect to allow users to mark linked items as suspect. See Marking Items as Suspect, page 82. Select Limit number of items allowed to and enter a value to specify how many items can be linked.
5. Select a Relationship option.

n
Select Use peer relationship to create a peer relationship between linked items. For example, you may create a link definition for issues that are related but do not need to be fixed together. Select Use parent/child relationship to create a parent/child relationship between linked items. For example, you may create a link definition for requirements and the test cases that are generated from them to track project coverage. To restrict the item types that can be used as the parent in links, select Restrict parent type to and select the parent item type. To restrict the item types that can be used as children in links, select Restrict child type to and select the child item type.
6. Optionally expand the Workflow Restrictions area to specify how relationships affect the workflow.
473
Parent/child relationship does not restrict workflow is selected by default. This option does not add any additional workflow restrictions to linked items that use the link definition. Parent restricts workflow enforces restrictions based on the parent item in links. Parent cannot be closed if any child is open requires all child items to be closed before the parent. Child cannot be re-opened if parent is closed prevents reopening child items if the parent is closed. Child restricts workflow enforces restrictions based on child items in links. Child cannot be closed if parent is open requires the parent item be closed before the child. Parent cannot be re-opened if any child is closed prevents reopening the parent item if a child is closed. Select Peers must be closed in the specified order to specify that items must be closed in the order they are linked. For example, issues #980, #872, and #922 are linked in a peer relationship in that order. If this option is selected, #872 cannot be closed until #980 is closed and #922 cannot be closed until #872 is closed. Select Peers must be re-opened in inverse order to specify that items can only be reopened in reverse order. For example, requirement #299 and test cases #3147, #3148, and #3153 are linked in a parent/child relationship. Requirement #299 is the parent and cannot be reopened if any children are closed. The last child, #3153, must be reopened first. Next, #3148 can be reopened then #3147. The parent, #299, can be reopened after #3147 is reopened.
7. Click OK. The link definition is added and you return to the Configure Link Definitions dialog box. Note: You may want to reorder definitions so the most-used definitions are displayed at the top of the Add Link and Edit Link dialog boxes. Select a definition and click Top, Move Up, Move Down, or Bottom to move it.
Editing link definitions

You can edit a link definition to update the name and description, change the allowed item types, or select additional workflow restrictions. You cannot change any relationship options if the link definition is in use. 1. Click Edit on the Configure Link Definitions dialog box. The Edit Link Definition dialog box opens. 2. Make any changes.
474
Con figu r in g N ot ificat ion Hyp e r l in ks
You cannot remove an item type from the link definition if the definition is selected in project options to be used when creating items from other item types, such as generating test cases from issues. 3. Click OK. The changes are saved.
Inactivating link definitions

If you want to prevent users from using a link definition, you can inactivate it. Inactivating a link definition does not affect existing links that use the definition. 1. Select the link definition on the Configure Link Definitions dialog box. 2. Click Inactivate. The link definition is inactivated. Users cannot use the definition to create new links. Note: To activate an inactive link definition, select the definition and click Activate.
Deleting link definitions

You can delete link definitions that are not being used. 1. Select the link definition on the Configure Link Definitions dialog box. 2. Click Delete. The link definition is deleted.
Configuring Notification Hyperlinks

Email notification hyperlinks can be added to email templates. These clickable links take users directly to the record that caused the notification to be sent. For example, when users receive an email about an assignment, they can click the link to go directly to the assigned record. You can use controlled hyperlinks to require recipients to log in to view records, make hyperlinks invalid after one use, or disable hyperlink access after a specific time period. Controlled hyperlinks are tracked and can be viewed or deleted. See Managing Controlled Email Notification Hyperlinks, page 476. The following field codes can be used to add hyperlinks to email templates:
n
%TTSTUDIOURL%Creates ttstudio hyperlinks to items. Always use this field code to provide links to requirements, requirement documents, test cases, and test runs. Use this field code to provide links to issues for TestTrack Client and TestTrack Web if you do not want to control access to the hyperlink. %HTTPURL%Creates http hyperlinks to issues. Use this field code to provide links to issues for TestTrack Web users if you do not want to control access to the hyperlink. The TestTrack CGI must be configured if you use this field code. See Setting hyperlink options, page 360. %NURL%Creates controlled http hyperlinks to issues. Use this field code to provide links to issues for TestTrack Web users if you want to control access to the hyperlink. The TestTrack CGI must be configured and the Enable controlled email notification hyperlinks option must be enabled if you use this field code. See Setting hyperlink options, page 360.
475
M an agin g Con t r ol l e d Email N ot ificat ion Hyp e r l in ks
Note: Disable the Allow Access via Email Notification Hyperlink security command if you do not want a security group to have access to email notification hyperlinks. 1. Choose Tools > Administration > Email Templates. The Configure Email Templates dialog box opens. 2. Select the email template you want to add the hyperlink to and click Edit. You can also add email notification hyperlinks when you add email templates. 3. Add the %HTTPURL%, %TTSTUDIOURL%, or %NURL% field code and any text to the body of the message. When the email is generated, the field code is replaced with a hyperlink to the record. If the recipients email client does not recognize the ttstudio protocol, the hyperlink may be inactive. Users can copy the URL from the email and paste it in the Address bar to open the related item. See Using the Address bar, page 13. Note: If the Send email in HTML format option is enabled, select the field code from the Available fields code list and click Insert to create a hyperlink. If you manually enter the field code, you must add href tags in the HTML view to make the link clickable (e.g., <a href=%NURL%> Text </a>). 4. Click OK. The changes are saved.
Managing Controlled Email Notification Hyperlinks

You can view and delete active controlled hyperlinks. Controlled hyperlinks are added to email templates using the %NURL% field code. See Configuring Notification Hyperlinks, page 475. Note: %TTSTUDIOURL% and %HTTPURL% field codes do not create controlled hyperlinks. 1. Choose Tools > Administration > Email Notification Hyperlinks. The Manage Email Notification Hyperlinks dialog box opens. All active hyperlinks are displayed.
2. Click a column heading to sort the hyperlinks. 3. Select a hyperlink and click Delete to delete it. You are prompted to confirm the deletion. 4. Click Yes.
476
M an agin g Au d it ab l e P r oce sse s
The hyperlink is deleted. Users can no longer access the record using the hyperlink.
Managing Auditable Processes

When properly implemented and managed, TestTrack can strengthen most best practice and regulatory compliance processes. TestTracks compliance features can be used to track both internal processes and regulatory compliance processes. Compliance needs can be direct (e.g., meeting 21 CFR Title 11 or Sarbanes-Oxley requirements) or indirect (e.g., passing life sciences supplier audits). TestTrack gives you the tools you need to demonstrate a repeatable, accurate testing process. You can satisfy compliance requirements with detailed histories of test cases, data, and results. You can also ensure processes, test data, and results are secure and cannot be accessed by unauthorized personnel.
Entering Electronic Signatures

You may be required to enter an electronic signature when you add, edit, or delete items, enter workflow events, or perform other actions, such as adding and removing requirements from requirement documents. Electronic signatures are saved in the projects audit trail, which tracks when and how data was modified. 1. The Signature Required dialog box opens after making a change to an item.
2. Enter your electronic signature. An electronic signature may require a username, password, and reason for making the change 3. Click OK. The changes are saved.
Managing Audit Trails

When audit trail logging is enabled, an audit trail record is created when an item is added, edited, or deleted, or when other actions are performed, such as adding, moving, or removing requirements from requirement documents. See Setting item compliance options, page 369. Audit trail logging records the information that is changed when an item is modified. 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. This provides a more secure environment with stricter auditing of changes and greater accountability. The audit trail is project-specific and is only viewable for the project you are currently logged in to.
477
M an agin g Au d it Tr ail s
You can search audit trail records and trace back to view a complete trail of when and how data was modified. Audit trail records are not affected when items are deleted because they are maintained separately from the history log. It is important to understand the difference between data records and audit trail records:
n
Data records contain the information stored in items and associated tables as well as cached in memory. Data records can be edited by TestTrack users. Audit trail records are created within the audit trail and are stored in a separate table. Audit trail records cannot be edited using TestTrack.
Searching audit trail records

You can search the audit trail to find change records based on criteria such as date, user, number, modification source, and modification type. 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 todays date. You can enter another date. 3. Select a Users option.
n n
Select All users to include records for all users. Select Selected users to include records only for specific users. Select the users to include. Click the Find button to find users to include in the search. See Finding users and customers, page 39.
4. Select an Items option.
478
Select All Items to include records of all issues, folders, requirements, requirement documents, test cases, and test runs in the project. Select Only and then choose the item type to include. Select an item type and then enter the item number to include specific records.
n n
5. Select a Modification Sources option.

n n
Select All sources to include records of items changed using all sources. Select Selected sources to include records of items changed using specific sources.
6. Select a Modification Types option to include records based on the action that changed the record.
n n
Select All types to include all modification types. Select Selected types then choose the modification types to include.
7. Click Search. The View Audit Trail dialog box opens. A list of matching records is displayed.
Viewing audit trail record details

1. Choose Tools > Administration > View Audit Trail. The Search Audit Trail dialog box opens. 2. Select search criteria and click Search. See Searching audit trail records, page 478. The View Audit Trail dialog box opens.
479
3. Select a record to view the details. 4. Select records and click Validate Records to ensure records were created using a valid TestTrack source. See Validating audit trail records, page 481. 5. Select records and click Export Records to export the records to a text or XML file. See Exporting audit trail records, page 481. 6. Select records and click View Report to generate a report detailing what changed in the record. See Generating an audit trail detail report, page 480. 7. Click Search to narrow or broaden the previous search or perform a new search. See Searching audit trail records, page 478.
Generating an audit trail detail report

You can generate a report that contains all details in the change record. The report includes fields before they changed (From) and after they changed (To). The electronic signature is also displayed if a change was signed. Note: Audit trail records created prior to TestTrack Pro 7.1 only include changed to data. Electronic signatures are only displayed for changes made in TestTrack 2012 and later. 1. Choose Tools > Administration > View Audit Trail. The Search Audit Trail dialog box opens. 2. Select search criteria and click Search. See Searching audit trail records, page 478. The View Audit Trail dialog box opens.
480
3. Select the records to include in the report. To select all records, click Select All. To include more than one record, Ctrl+click each record. 4. Click View Report. The Audit Trail Detail Report opens in a new browser window.
Validating audit trail records

You can validate audit trail records to ensure changes were made using TestTrack, not other means such as editing a record directly in a database table. Note: You can only validate audit trail records created in TestTrack Pro 7.1 and later. 1. Choose Tools > Administration > View Audit Trail. The Search Audit Trail dialog box opens. 2. Select search criteria and click Search. The View Audit Trail dialog box opens. 3. Select the records to validate. To select all records, click Select All. To select more than one record, Ctrl+click each record. 4. Click Validate Records.
n n
Click OK if the records are valid. Records that cannot be validated are displayed in a report for further review.
Exporting audit trail records

You can export audit trail records to text or XML files. Exported records do not include the related items or file attachments. To export items, see Importing and Exporting Data, page 89. Note: Electronic signature data is only exported with audit trail records created in TestTrack 2012 and later. 1. Choose Tools > Administration > View Audit Trail. The Search Audit Trail dialog box opens. 2. Select search criteria and click Search. The View Audit Trail dialog box opens. 3. Select the records to export. To select all records, click Select All. To include more than one record, Ctrl+click each record. 4. Click Export Records. The Export Audit Trail dialog box opens. 5. Select the file location, enter a file name, select the file format, and click Save. A progress indicator opens.
481
De l e t in g Hist or ical Log In for mat ion
Deleting Historical Log Information

You can delete log entries if the project becomes too large because of historical information. Deleting historical log entries does not reduce the amount of used disk space until the project is compressed. Tip: To delete log entries for specific records, select the records on the list window before continuing. 1. Choose Tools > Administration > Delete Historical Info. The Delete Historical Info dialog box opens.
2. Select the record Type that you want to delete historical information for. 3. Select a Log Entry option.
n n
Delete historical information regardless of log date deletes all log entries. Delete historical information with dates prior to and including deletes log entries prior to and including the date you enter.
4. Click a record option button. You can delete historical information for all, closed, or specific issues, requirements, requirement documents, test cases, or test runs, or all or specific folders. 5. Click Yes when you are prompted to confirm the deletion. The historical log information entries are deleted. 6. Click Close to close the Delete Historical Info dialog box.
482
Configuring SoloBug
SoloBug is a cross-platform, stand-alone bug reporting application that allows customers and other users to submit issues directly to TestTrack Pro. A SoloBug file contains a single bug report or feature request, and it is emailed to an address you specify. You can import the file into any TestTrack Pro project.
Distributing SoloBug
You can email the SoloBug executable (EXE or PDB) to customers, or put it on your web site and allow customers to download it. When customers find bugs or want to request features, they simply start SoloBug, enter the information, save the file, and then email it to you. A SoloBug file is a single bug report that contains contact information and computer configuration, a description of the problem or feature request, and any file attachments. You can easily import the SoloBug file information into TestTrack Pro. You can use the email import method, configure TestTrack to automatically import SoloBug files, or manually import them. A new issue is created each time a SoloBug file is imported. See Automatically importing SoloBug files, page 485 and Manually importing SoloBug files, page 485. You can download the SoloBug Guide (http://downloads.seapine.com/pub/docs/solobuguser.doc), customize it, and distribute it freely to your customers who use SoloBug.
Customizing SoloBug
Before distributing SoloBug, customize the executable to make sure customers and users provide all the information you need. You can customize such things as the title, instructions, or field names. You can also rename fields, add field values, and make fields required. Note: To ensure the correct SoloBug executable is distributed with each project, copy and rename the executable to match the project name. On Windows, only one executable can be the registered application for a file extension. When you double-click a SoloBug file, the registered SoloBug application opens. To ensure custom information is available, open the file using the project-specific SoloBug application. 1. Start TestTrack Pro and log in to the project you want to customize SoloBug for. 2. Choose Tools > Administration > Customize SoloBug. The Customize SoloBug dialog box opens. 3. Click Browse to select the SoloBug executable you want to customize. The Open SoloBug Application dialog box opens. 4. Select a SoloBug executable and click Open. You return to the Customize SoloBug dialog box. All fields are populated.
483
Cu st omiz in g S ol oB u g
5. Enter the General SoloBug Settings.

n n
Title appears in the title bar of SoloBug, preceding the name of the open bug report file. File Name Prefix is added to the SoloBug file name. The remaining portion of the file name is an automatically generated sequence number. Use this field to help organize SoloBug files. For example, enter each customers name in this field. Instructions provide users with information specific to your use of SoloBug, such as the email address you want the files sent to. Instructions are not displayed if this field is empty.
6. Select a Field to Customize. You can customize names, add field values, and set user options.
n
Click Use Project Settings to use the required fields, field names, and field values set up in the TestTrack project. The <Name> field is visible is selected by default. Clear the check box to make the field and its label invisible. Select User is required to select a value for the <Name> field to make the field required. When a field is required, users cannot save a SoloBug file until values are entered for all required fields. Select User can enter a free form text entry in the <Name> field to allow users to enter a value. Enter a name in the text box to rename the field. The In SoloBug, the <Name> field is named value is populated from the SoloBug executable and may not match the Field to Customize selection.
484
Au t omat ical l y imp or t in g S ol oB u g fil e s
Default field values are displayed in the Field Values for the <Name> field list. You can add new values or edit or delete existing values. To reorder values, click the arrow next to the field and drag it up or down.
7. Click Update SoloBug & Close when you finish configuring SoloBug. The customized SoloBug executable is ready for distribution. See Distributing SoloBug, page 483.
Automatically importing SoloBug files

If you receive a large number of SoloBug files, you can configure TestTrack to automatically import SoloBug files. 1. Choose Tools > Administration > Project Options. The Project Options dialog box opens. 2. Click the SoloBug tab. 3. Select a Look for new files option. Note: You can override this setting by choosing File > Import > Perform Server Import. New SoloBug files will be imported regardless of the time interval you set. 4. Click OK to save the settings.
Manually importing SoloBug files

If you do not receive a large number of SoloBug files, or want to make sure they are imported into the right project, you can manually import the files at any time. 1. Choose File > Import > Load SoloBug Files. The SoloBug Files to Import dialog box opens. 2. Select the SoloBug file you want to import. SoloBug files are saved with an SBG extension. 3. Click Open. The imported file appears in the Issues list window at the end of the list. Notice the new issue icon appears next to it. Note: You can also drag the SoloBug file onto the Issues list window.
485
Configuring SoloSubmit
SoloSubmit allows an unlimited number of customers and external users to submit bug reports and feature requests to TestTrack projects from a web browser. It eliminates data entry of bug reports by automatically importing bug reports. SoloSubmit includes the following features:
n n
Customers can attach files to bug reports. SoloSubmit automatically uses the reporting terminology you define for your projects. For example, SoloSubmit uses any customized product names. Customers can access SoloSubmit from any platform that supports a web browser. SoloSubmit uses cookies to store contact information. Cookies can be turned off. See Turning Off SoloSubmit Cookies, page 491. The SoloSubmit web page can be customized to match the look of your web site.
n n
Installing SoloSubmit
SoloSubmit ships with TestTrack Pro and is installed during the installation. 1. Start the installation program. 2. The Welcome dialog box opens. Click Next. 3. Accept the license terms and click Next. 4. Choose the installation type and click Next. Select Server installation with Web components or Custom installation to install SoloSubmit. 5. Click Next to complete the installation.
Enabling SoloSubmit
Note: SoloSubmit must be enabled for each project. 1. Start TestTrack and open the project you want to enable SoloSubmit for.
n
If you are using the TestTrack Client, choose Tools > Administration > Project Options then select the SoloSubmit category. If you are using TestTrack Web, click Configure > Project Options then click the SoloSubmit tab.
487
En ab l in g S ol oS u b mit
2. Select Enable entering issues via the SoloSubmit web page to enable SoloSubmit. This option is project-specific. SoloSubmit must be enabled for each project. 3. The SoloSubmit HTML page field defaults to solosubmit.htm. If you use a customized SoloSubmit HTML page, enter the file name. Make sure the HTML file is in the correct TestTrack directory on your web server. 4. Select Email an acknowledgement to the submitter to automatically send an acknowledgement. Select the email template you want to use. 5. Select Enter next sequence number in issues reference field to automatically enter the next available number. 6. Select Enforce required field validation to ensure that values are entered for all required fields. The required field validation is not enforced for the Entered By field because users do not log into SoloSubmit. If Entered By is a required field, issues entered via SoloSubmit cannot pass the required field validation check. Tip: If you configure required fields in TestTrack that you do not use on the SoloSubmit page, an error is returned when an issue is submitted. As a workaround, do one of the following: add the field so the user can enter the value, add the field as a hidden field, do not mark the field as required, do not enforce required field validation. 7. Select Use default values to initially populate the SoloSubmit web page with default values. SoloSubmit cannot determine which time zone to use as default values for date/time custom fields. When an issue is submitted via SoloSubmit there is no associated user in the project, so there are no user options to check to determine the time zone. The current time of the computer the SoloSubmit CGI is running on when the SoloSubmit page is loaded is used as the default value for date/time custom fields. The date is also assumed to be in the servers time zone. 8. Select fields you do not want JavaScript to handle field relationships for on the SoloSubmit web page. You would choose not to include the JavaScript for one of the following reasons:
488
Cu st omiz in g S ol oS u b mit
The SoloSubmit web page includes hidden fields. For example, you comment out a field you do not want the customer to see. You can delete the HTML, but the field and its values are still displayed in the JavaScript if the customer chooses View Source on the SoloSubmit web page. Choosing not to include the JavaScript resolves this issue. The SoloSubmit web page is customized and you do not want to overwrite the customization. For example, you hard code a list of field values in the HTML. If you include the JavaScript your customization is overwritten. By ignoring JavaScript for the field, the hard coded list values are used
If neither reason applies and you select a field from the list it can result in unexpected behavior. For example, you ignore JavaScript for Component, which is a child field of Product. When SoloSubmit is accessed, Product and Component are populated with the initial values. If the user chooses a different Product, the Component values are not changed. 9. Click OK (Client) or Save (Web). SoloSubmit is enabled for the project. You can customize the SoloSubmit web page or use the default page. Note: Remember to provide users and customers with the URL. To submit bugs or feature requests, they open a browser and enter the SoloSubmit URL (e.g., www.acme.com/ttweb/loginSoloSubmit.htm).
Customizing SoloSubmit
Using a text editor or an HTML editor, you can customize SoloSubmit web pages to match your corporate web site. You can include all of your bug reporting fields or limit customers to just a few fields or create different web pages for feature requests and bug reports. See Customizing SoloSubmit pages, page 490.
About SoloSubmit pages

n n n
The login page is named loginSoloSubmit.htm The issue submittal page is named SoloSubmit.htm The errors page is named ss_errormsg.htm
Customization notes
n
You need the ID of each project you are customizing SoloSubmit for. To find this value, start the TestTrack Server Admin Utility and click Projects. The ID value is listed in the first column. If you are using Windows NT, you must have permissions to save changes. If you change the default pages, we strongly recommend that you comment out the default HTML instead of deleting it. You can easily compare the modified and unmodified versions of a page if you experience problems.
n n
489
Cu st omiz in g S ol oS u b mit
Default SoloSubmit fields

n n n
The default title is Report a Bug. Default pop-up menu values: product, component, type of problem, and severity. Default text fields: first name, last name, company, email address, phone number, version, computer model, operating system, description, and how to reproduce.
Customizing SoloSubmit pages

If you only want to change the appearance of the web pages, or add images and links, you can customize the pages that all customers access. 1. Copy and rename the SoloSubmit.htm file. Use a unique file name such as YourCompanyNameSoloSubmit.htm. 2. Customize the file using a text editor or an HTML editor.
n
You can customize such things as the page title, background color, or fonts. You can also add graphics and links and customize the text on the page. You can add JavaScript to SoloSubmit pages. Place the code inside the <head> </head> statements in the HTML then modify the <form > statement to call the validation function. SoloSubmit supports TestTrack field codes, which are codes that are replaced with information from the project. For a list of supported codes, and how to use field codes, see SoloSubmit Field Codes, page 492.
3. Copy and rename the loginSoloSubmit.htm file to customize the login page. 4. Copy and rename the ss_errormsg.htm file to customize the errors page.
Customizing static SoloSubmit pages

Use static SoloSubmit pages to provide customized pages while restricting menu values. For example, you have one project and want to provide SoloSubmit access to customers who are competitors. Provide each customer with a static SoloSubmit page with customized product fields. When customers access the static SoloSubmit page, their product name is the only value in the product menu. Note: If you use static pages, and menu values change in the TestTrack project, remember to update SoloSubmit with the changes. 1. Open SoloSubmit by browsing to the loginSoloSubmit.htm page. 2. Select a project and click Continue. The Report a Bug page opens. 3. Right-click and select View Source. The source code opens in Notepad or another text editor. 4. Select all of the source code. Copy and paste it into a new HTML document. 5. Save the HTML file using a unique file name such as YourCompanyNameSoloSubmit.htm. This document is the starting point for your customized static SoloSubmit page.
490
Tu r n in g Off S ol oS u b mit Cookie s
6. Customize the file using a text editor or an HTML editor.

n
You can customize such things as the page title, background color, or fonts. You can also add graphics and links and customize the text on the page. Customize this file to include your products, components, versions, etc. All fields are optional. You can add JavaScript to SoloSubmit pages. Place the code inside the <head> </head> statements in your HTML then modify the <form >statement to call the validation function. SoloSubmit supports field codes, which are codes that are replaced with information from the project. For a list of supported codes, and how to use field codes, see SoloSubmit Field Codes, page 492.
n n
7. Copy and rename the loginSoloSubmit.htm file to customize the login page. 8. Copy and rename the ss_errormsg.htm file to customize the errors page. 9. When you finish customizing the web pages, edit the SoloSubmit settings in the project. See Setting SoloSubmit options, page 364. Static SoloSubmit pages can be hosted from any location because they do not need a direct server connection to spool field values. SoloSubmit pages require access to the TestTrack CGI. If you move the SoloSubmit pages, make sure the CGI can be accessed.
Turning Off SoloSubmit Cookies

SoloSubmit uses cookies to store contact information. Customers do not have to keep entering this information. Cookies can be turned off. 1. Edit the SoloSubmit.htm page in Notepad or another editor. 2. Find the following function. function writeCookies() { var expdate = new Date (); expdate.setTime (expdate.getTime() + (365 * 24 * 60 * 60 * 1000)); // 365 days from now with(document.theForm) { 3. Comment the function writeCookies code. //function writeCookies() //{ // var expdate = new Date (); // expdate.setTime (expdate.getTime() + (365 * 24 * 60 * 60 * 1000)); // 365 days from now // with(document.theForm) // { 4. Cookies are now turned off. Customers contact information is not stored.
491
S ol oS u b mit Fie l d Cod e s
SoloSubmit Field Codes

SoloSubmit field codes can be used with drop-down and text fields to customize SoloSubmit.
n n
The control name code, label code, and value code are all used with dynamic SoloSubmit web pages. Static field numbers are only used with static SoloSubmit web pages. The TestTrack Server uses this information to identify the field and return the corresponding value. If you use the reference field code, make sure the enter next sequence number option is disabled. If this option is enabled, the reference field is overwritten. The other hardware and software field (%HWSW%) is populated with its own entry and most user field code data, with the following exceptions: company, email, first name, last name, and phone number.
SoloSubmit drop-down fields

Control Name Code %COMP_ CN% %DISP_CN% Value Code %COMP_ V% %DISP_ V% %FNDV_ V% %PRIO_ V% %PROD_ V% %REPR_ V% %SEVR_ V% %TCFG_ V% %TYPE_ V% Label Code %COMP_ L% %DISP_ L% %FNDV_ L% %PRIO_ L% %PROD_ L% %REPR_ L% %SEVR_ L% %TCFG_ L% %TYPE_ L% Static Field Number 24 Description Component that contains the issue
43
Disposition
%FNDV_CN%
12
Found in version (used with drop-down and text fields) Priority
%PRIO_CN%
%PROD_ CN% %REPR_CN%
Product
11
Reproduced?
%SEVR_CN%
33
Severity
%TCFG_CN%
13
Test configuration name
%TYPE_CN%
Type
492
S ol oS u b mit U se r Fie l d Cod e s
SoloSubmit text fields

Control Name Code %DESC_ CN% %FNDD_ CN% %FNDV_CN% Value Code %DESC_ V% %FNDD_ V% %FNDV_ V% %HWSW_ V% %REFR_ V% %STEP_ V% %SUMM_ V% %WORK_ V% Label Code %DESC_ L% %FNDD_ L% %FNDV_ L% %HWSW_ L% %REFR_ L% %STEP_ L% %SUMM_ L% %WORK_ L% Static Field Number 54 Description Description
Found date
12
Found in version (used with drop-down and text fields) Other hardware and software
%HWSW_ CN% %REFR_CN%
64
25
Reference
%STEP_CN%
58
Steps to reproduce
%SUMM_ CN% %WORK_ CN%
Summary
55
Workaround
SoloSubmit User Field Codes

SoloSubmit user information is added to the corresponding record in TestTrack Pro. This information is also added to the Other Hardware and Software area of the Issue Detail tab, with the following exceptions: company, email, first name, last name, and phone number. Note: Do not include the percent signs if you are using the user field codes with static SoloSubmit web pages. Field Code %ADHW% %BRND% %CDMD% %CMPY% %CPUS% Description Additional hardware and software Computer brand CD-ROM type Company name CPU speed
493
S ol oS u b mit U se r Fie l d Cod e s
Field Code %CPUT% %EMAL% %FNAM% %HDSZ% %HDTP% %LNAM% %MDMD% %MMON% %MODL% %OTYP% %OSVR% %PHON% %PRMD% %RAMS% %ROMS% %SCMD% %VIDC%
Description CPU type Email address First name Hard disk size Hard disk type Last name Modem type Multiple monitors? Computer model Operating system Operating system version Phone number Printer type RAM ROM Scanner type Video controller type
494
Integrating with Source Control Tools

You can integrate Surround SCM and other source code control (SCC) applications with TestTrack, which gives you access to TestTrack items and source code files from either application. A change made in one application is also available in the other application. The following resources are available to help you integrate TestTrack with SCC applications:
n
The TestTrack Integrations knowledgebase article (www.seapine.com/kb/questions/1451) lists the supported integrations. The Integrations knowledgebase category (www.seapine.com/kb/categories/TestTrack/Integrations/) provides integration installation instructions, setup information, and troubleshooting help.
Note: The following instructions explain how to use Surround SCM with TestTrack. Keep in mind that the source code commands you have access to may vary depending on the application you are using.
Configuring SCC Integration

Before you can start working with source code files, you need to select the SCC application are you are using, select the project path for the files you are working with, and enter your login information. See Setting SCC local options, page 495 and Setting SCC user options, page 496. The TestTrack administrator or another high-level user can configure project options, project paths, and check in options. Note: Most users only have access to configure local and user options for SCC integrations.
Setting SCC local options

Before you configure SCC integration, you need to select the application you want to integrate TestTrack with. 1. Choose Tools > SCC Integration. The Configure SCC Integration dialog box opens. 2. Select the Local Options category. A list supported source control applications is displayed.
495
Con figu r in g S CC In t e gr at ion
3. Select the application you want to use from the Available Providers list and click Make Current. The selected application is displayed in the Current field. 4. Click OKto save the changes.
Setting SCC user options

The SCC user options specify the SCC project database to connect to from TestTrack and your SCC application login information. 1. Choose Tools > SCC Integration. The Configure SCC Integration dialog box opens. 2. Select the User Options category. User options settings are stored in the TestTrack project for the currently logged in user. If you log in to multiple TestTrack projects, you must configure SCC user options for each project.
3. Click Browse to select the SCC project database. 4. Select Use your TestTrack username and password if you use the same login credentials for the SCC application or select Use the following and enter your SCC username and password. 5. Click Validate Connection to test the connection. 6. Click OK tosave the changes.
496
Setting SCC project options

You can create a template that automatically populates the comments field when source files are checked in. Users can also enter additional text when checking in files. 1. Choose Tools > SCC Integration. The Configure SCC Integration dialog box opens. 2. Select the Project Options category.
3. Enter text and field codes to create a template. See Field Codes, page 529 fora list of field codes. 4. Click OK to save the changes.
Setting SCC project paths

You can select the projects that users can access in the SCC application to limit access from TestTrack. 1. Choose Tools > SCC Integration. The Configure SCC Integration dialog box opens. 2. Select the Project Paths category.
497
3. Expand the root repository, select a path, and click Add to select the project paths you want to give users access to. Users can access all files if you select the root repository. Select specific repositories to limit the files users can access. 4. Click OK to save the changes.
Setting SCC check in options

You can set options to allow users to enter a fix workflow event when checking in files from TestTrack and select the event to use. 1. Choose Tools > SCC Integration. The Configure SCC Integration dialog box opens. 2. Click the Check In Options category.
3. Select Include options to enter fix event on check in to allow users to add a fix event when checking in a file. The Check In & Fix dialog box opens when users check in files. 4. Select the Event to use.
498
Wor kin g wit h S ou r ce Cod e Fil e s
The selected event is applied to the TestTrack itemwhen it is checked in using the Check In & Fix dialog box. 5. Click OK to save the changes.
Working with Source Code Files

You can link source code files to items in TestTrack, which allows you to work with the files without switching to your source code application. You can view source code files and commands on the Source Code tab if items have attached files. Note: To access the Source Code tab when you are editing items other than issues, click the Files tab. Keep in mind that the source code commands you have access to may vary depending on the application you are using. The Source Code tab includes the following information about the files attached to an item.
n n
Source FilesAll files attached to the item. Fixed RevisionsFixed revision number. Revision numbers are retrieved from the SCC application and cannot be updated if the file is not checked in from TestTrack. Fixed TimestampTimestamp of the latest fixed revision found. Locked ByUsername if it can be determined.
n n
Tip: Add a column to a list window and select Has SCC files as the column contents to quickly view items with source code file attachments. See Using List Windows, page 21.
Attaching source code files

You can attach source code files to items, such as issues or requirements. After a file is attached to an item, the file is under source control. 1. If you are editing an issue, click the Source Code tab.
499
If you are editing another item type, such as a test case, click the Files tab and then click the Source Code tab. 2. Click Attach File. The Attach Files dialog box opens.
3. Select the project from the SCC Projects list. A list of available files is displayed in the Files in project list. If you add files or directories to your SCC project, click Refresh Project Data. 4. Select the files you want to attach from the Files in project list and click Add to move them to the Files to attach list. 5. Click OK to attach the files. Note: You can detach a file to break the connection. See Detaching source code files, page 512
Attaching changelists
A changelist, which is a list of files and the actions to be performed on the files, groups transactions together and treats the files in the changelist as one unit, also known as an atomic transaction. You can attach changelists to TestTrack items. If one action in a changelist fails, the entire operation is cancelled and changes are not made in the SCC application Note: Commands and options may be different depending on the source code control application you are using. Refer to the SCCapplication documentation for more information. 1. Click the Source Code tab when you are editing an item. 2. Select the file and click Attach Changelist. The Select Changelist dialog box opens.
500
3. Select the changelist you want to attach to the item. 4. Click OK. The changelist is attached. Changelist actions are not performed until the changelist is committed. See Committing pending changelists, page 510.
Getting source code files

Get files when you want to view a file but do not need to make any changes. A read-only copy of the file is created in the specified directory. Note: Commands and options may be different depending on the source code control application you are using. Refer to the SCCapplication documentation for more information. 1. Click the Source Code tab when you are editing an item. 2. Select the file and click Get. The Get Files dialog box opens.
501
3. Enter a Location to retrieve the files to or click Browse to select a file. If you are only getting one file, the location is determined by the SCC user configuration. If you are getting multiple files, the Location field may be empty because each file can have a different default location. 4. Select Only show dialog when Shift key is pressed to only display the dialog box again if the Shift key is pressed. 5. Optionally expand the Get based on area to display options for retrieving files based on version, timestamp, label, or workflow state set in the SCC application. 6. Optionally expand the Advanced options to select advanced get options. You can make the file writable, retrieve the server copy of the file, and enable automatic merges. You can also specify an overwrite option if the local and server file are different and select the timestamp to set on the local file when it is retrieved. 7. Click OK to get the files.
Viewing source code files

View a source code file to open the local copy in the associated viewer or application. 1. Click the Source Code tab when you are editing an item. 2. Select the file and click View Local Copy. The View Files dialog box opens. 3. Select a View option. 4. Click OK to view the file.
Editing source code files

When you edit a file, the source code application checks it out and opens it for editing.
502
1. Click the Source Code tab when you are editing an item. 2. Select the file and click History. 3. Select a file version and click Edit File. The file opens in the associated application. 4. Make any changes and save the file. Remember to check in the file. When you edit a file, it is automatically checked out to the working directory.
Checking out source code files

Check out files when you need to make changes. If the SCC application is not configured to allow multiple check outs, or a user has exclusively locked a file, it cannot be checked out. Note: Commands and options may be different depending on the source code control application you are using. Refer to the SCCapplication documentation for more information. 1. Click the Source Code tab when you are editing an item. 2. Select the file and click Check Out. The Check Out Files dialog box opens.
3. Optionally enter any Comments, such as the reason for checking out the file. 4. Select Only show dialog if Shift key pressed to only display the dialog box again if the Shift key is pressed. 5. Select Exclusive check out to prevent other users from checking out the files.
503
6. Optionally expand the Changelist options area to display options for checking in files as part of a changelist. Changelists group related files and the actions performed on them and treat the files as one unit. You can use an existing changelist or create a new one when checking out files. Files you add to a changelist during check out are checked in when the changelist is committed. See Committing pending changelists, page 510. 7. Optionally expand the Advanced options area to display advanced check out options. You can check out the server copy of the file, specify an overwrite option if the local and server file are different, and select the timestamp to set on the local file when it is checked out. 8. Click OK to check out the file.
Viewing source code file history

You can view a source files history and work with a historic version. Note: Commands and options may be different depending on the source code control application you are using. Refer to the SCCapplication documentation for more information. 1. Click the Source Code tab when you are editing an item. 2. Select the file and click History. The History dialog box opens.
504
3. Optionally select a Filter by user. 4. Optionally select a Filter by action. 5. Optionally select Show workflow history to display all file workflow state changes. 6. Optionally select Show custom field history to display the file custom field values. 7. Optionally select Show labeling history to display all labels that have been applied to the file. 8. Select a version and click Details to view version details. The read-only History Details dialog box opens. When you view detailed historical information about a file, the information that is displayed depends on the file action performed on the selected version. 9. Select a version and click Get to get the file. See Getting source code files, page 501. 10. Select a version and click Check Out to check out the file. See Checking out source code files, page 503. 11. Select a version and click Add to Label to label the file. See Labeling source code files, page 507. 12. Select a version and click Show Labels to view any labels applied to the file. 13. Select a version and click Differences to view file differences. See Diffing source code files, page 506.
505
14. Select a version and click View File to view it. 15. Select a version and click Edit File to edit it. See Editing source code files, page 502. 16. Select a version and click Rollback File to revert to a previous file version. See Rolling back source code files, page 510. 17. Select a version and click View Changelist to view the committed changelist. See Viewing changelists, page 511. 18. Select a version with an attach action and click View Attached to view the TestTrack item the file was attached to. 19. Select a version and click Attach to TestTrack to attach the file to other TestTrack items. 20. Select a version and click Set State to set the workflow state for the file. 21. Click Close to close the file history.
Diffing source code files

You can diff files to compare differences between two file versions. After you make changes to a file, but before you check in the file, you may want to compare the file to another copy and reconcile differences. Note: Commands and options may be different depending on the source code control application you are using. Refer to the SCCapplication documentation for more information. 1. Click the Source Code tab when you are editing an item. 2. Click History. The History dialog box opens. 3. Select a version and click Differences. The Differences dialog box opens. Read-only information is displayed in the File to Compare area.
506
4. Select a Second File option. You can compare the server file with the working directory file or select a different file on your local drive. 5. Click Advanced to select a file or version on the SCC application server. You can also compare the file with a selected branched file, historic version, or an unrelated file. 6. Click Differences. The differences utility starts. Refer to the utilitys documentation for additional information.
Labeling source code files

Labels provide a way to mark a specific version of a file or repository. When you create a label, a new entry is created in the history. The file and the version number do not change. Note: Commands and options may be different depending on the source code control application you are using. Refer to the SCCapplication documentation for more information. 1. Click the Source Code tab when you are editing an item. 2. Select the file and click History. 3. Click Add to Label on the History dialog box. The Add to Label dialog box opens.
507
4. Select a Label. Select <New Label> to create a label. Click Select to view label details or search for a label. 5. Optionally enter any comments about the label. 6. Optionally select Update label with selected version to remove the label from earlier file versions. 7. Click OK to apply the label to the files.
Checking in source code files

Check in updates files with changes, removes the lock on the files, makes changes available to other users, and increments the version number by one. Note: Commands and options may be different depending on the source code control application you are using. Refer to the SCCapplication documentation for more information. 1. Click the Source Code tab when you are editing an item. 2. Select the file and click Check In. The Check In Files dialog box opens.
508
3. Enter any comments. Your project may use a check in comments template that automatically populates the Comments field. You can add comments to the field or delete comments and add your own. 4. Select Apply comments to all to use the same comment for all files you are checking in. 5. Optionally expand the Changelist options area to display options for checking in files as part of a changelist. Changelists group related files and the actions performed on them and treat the files as one unit. You can use an existing changelist or create a new one when checking in files. 6. Optionally expand the Workflow options area to set a workflow state on files in the SCC application. 7. Optionally expand the Local file options to display options for handling local files after changes are checked in. 8. Optionally expand the Advanced options area to display advanced check in options. You can select a label to apply to the file or create a new one. You can also skip server auto-merge to check in the file without merging changes and update the file version number even if no changes were made. 9. Click OK to check in the file.
509
Committing pending changelists

Changelist actions are not performed until you commit the changelist. When you commit a changelist, all files in the changelist are submitted to the SCC application server at the same time. Note: Commands and options may be different depending on the source code control application you are using. Refer to the SCCapplication documentation for more information. 1. Click the Source Code tab when you are editing an item. 2. Select the changelist and click Commit Changelist. The file actions are submitted to the server. If the transaction is successful, the changelist is removed from the pending list and added to the committed list. If a transaction fails, an error is displayed. Correct the error and recommit the changelist.
Rolling back source code files

You can roll back files to discard changes and revert to a previous file version. The version number increments even though the contents do not change. For example, the current version is 5 and you rollback to version 3. After the rollback, the new version is 6. Version 3 and version 6 have the same contents. Note: Commands and options may be different depending on the source code control application you are using. Refer to the SCCapplication documentation for more information. 1. Click the Source Code tab when you are editing an item. 2. Select the file and click History. The History dialog box opens. 3. Select the file version you want to roll back to and click Rollback File. The Rollback File dialog box opens.
4. Enter any comments and click OK. The file is rolled back to the selected version.
510
Viewing changelists
You can view details about committed changelists attached to items. Note: Commands and options may be different depending on the source code control application you are using. Refer to the SCCapplication documentation for more information. 1. Click the Source Code tab when you are editing an item. 2. Select the file and click History. The History dialog box opens. 3. Click View Changelist. The Changelists dialog box opens.
4. Select a changelist and click View Details to view additional details. 5. Select a changelist and click Get to retrieve a copy of all files associated with it. You can also get individual files in the changelist 6. Select a file and click History to view the file history. 7. Select a file and click Differences to view differences between the version of the changelist file and the version the action modified. 8. Select a file and click View File to view the file. 9. Select a changelist and click Label to label the files in the changelist. You can also label individual files in the changelist. 10. Select a changelist and click Save As to save it or click Print to print it. 11. Click Close to close the Changelists dialog box.
Undoing source code file check out

If you modify a source code file and then decide you do not want to save the changes, you can undo the check out. This discards changes, checks in the file, and does not change the version number.
511
Disab l in g S CC In t e gr at ion
Note: Commands and options may be different depending on the source code control application you are using. Refer to the SCCapplication documentation for more information. 1. Click the Source Code tab when you are editing an item. 2. Select the file and click Undo Check Out. The Undo Check Out Files dialog box opens.
3. Select Only show dialog when Shift key is pressed to only display the dialog box again if the Shift key is pressed. 4. Select a File overwrite option to specify what happens if a writable file is found in the working directory. 5. Select Make files writable to leave a read-write copy of the file in the working directory. 6. Click OK. The file is no longer checked out.
Detaching source code files

When you detach files, the link between TestTrack and the source code file is removed. 1. Click the Source Code tab when you are editing an item. 2. Select the file and click Detach. You are prompted to confirm that you want to detach the file. 3. Click Yes. The file is detached.
Disabling SCC Integration

1. Choose Tools > SCC Integration. The Configure SCC Integration dialog box opens. 2. Select the provider you want to disable and click Disable SCC Integration. You are prompted to confirm that you want to disable the integration. 3. Click Yes to disable the integration. 4. Click OKto save the changes.
512
Using the Outlook Add-in

The TestTrack Outlook add-in allows you to add Microsoft Outlook emails as new issues, requirements, requirement documents, or test cases or as tracked email to existing items in TestTrack. The add-in is compatible with Outlook 2003, 2007, and 2010. During installation, you are prompted to install the Outlook add-in if Outlook is installed on your computer. The add-in is automatically installed in the same directory as the TestTrack Client. When you start Outlook after installing the add-in, a TestTrack menu and toolbar are added to Outlook. If the menu and toolbar are not available, refer to the Microsoft Office Outlook help for information about enabling add-ins.
Configuring the Outlook add-in settings

You can set your preference for connecting to TestTrack manually or automatically when Outlook starts. 1. In Outlook, choose TestTrack > Settings. The TestTrack Outlook Add-in Settings dialog box opens. 2. Select an option for what the add-in should do when Outlook starts. 3. Click OK to save the settings.
Accessing TestTrack projects from Outlook

Before you can add emails from Outlook to a TestTrack project, you must connect to the TestTrack Server and project. You can also switch projects, connect Outlook to a different server, and disconnect Outlook from the TestTrack Server.
Connecting to a TestTrack Server

1. In Outlook, choose TestTrack > Connect to Server. The TestTrack Login dialog box opens. 2. Select the Server you want to connect to. Click Setup if you need to add a server. 3. Enter your Username and Password or select Use single sign-on to log in with your network credentials. 4. Click Connect. 5. Select a Project. Click Refresh if the project you want to connect to is not listed. 6. Click OK. You are connected to the TestTrack project.
Switching projects
To switch to a different project, choose TestTrack >Switch Project, select the project, and click Switch.
513
Cr e at in g it e ms fr om Ou t l ook e mail s
Connecting to a different server

To connect to a different server, choose TestTrack >Connect to Server. Click Yes when prompted to close the open project. Select the server, enter the login information, and click Connect.
Disconnecting from a server

To log out of a project or disconnect from a server, choose TestTrack >Logout and Disconnect. Click Yes when prompted to close the project and server connection.
Creating items from Outlook emails

You can create a TestTrack item from Outlook. The email subject is used as the item summary and the email body is used as the item description. 1. In Outlook, select an email and choose TestTrack > Create Item from Email. The Select Item Type dialog box opens. 2. Select the type of item to create and click OK. The Add dialog box opens. The available fields depend on item type. 3. Enter any additional information. For example, you may want to change the Found By user to the customer who sent the email. 4. Click Add. The item is saved and added to the project.
Attaching Outlook emails to items

If you receive an email with information that applies to an existing TestTrack item, you can attach the email to the item. Note: Email tracking must be enabled for the project before you can attach Outlook emails to TestTrack items. Ask your TestTrack administrator for information. 1. In Outlook, select an email and choose TestTrack > Attach Email to Item. The Attach Email to Item dialog box opens. Note: This dialog box includes many of the same functions as list windows. For example, you can filter or search for specific items. 2. Select an item Type. 3. Select the item to attach the email to and click Add. The email is added to the TestTrack item.
514
Appendix A: Third-Party Development Tool Integrations

TestTrack can be integrated with Visual Studio and Eclipse, making it easy for you to work in your development environment while accessing TestTrack. The Integrations knowledgebase category (www.seapine.com/kb/categories/TestTrack/Integrations) provides integration installation instructions, setup information, and troubleshooting help. See the TestTrack Integrations knowledgebase article (www.seapine.com/kb/questions/1451) for a list of supported integrations.
515
Appendix B: Environment Variables

Environment variables can be used in executables that run when automation rules pass. Environment variables pass values to the executable from the issue, test case, or test run that caused a trigger or escalation rule to run so additional actions can be performed. See Running Executables from Automation Rules, page 437.
Issue environment variables

The following environment variables can be used to return values from the issue that caused the executable to run. The NUMR environment variable returns the number that corresponds to the order of the Reported by record within all Reported by records. For example, DESC_2 returns the Description field of the second Reported by record. Variable BKLNK COMP CREB CRED CREL DCAB DCAD DCAT DCLB DCLD DESC DFSA DISP DNUM ENTB ENTD FNDB Description Number of Broken Links Issue Component Issue Created By Issue Date Created Issue Creation Method Issue Current Assignment By Issue Current Assignment Date Issue Currently Assigned To Issue Closed By Issue Closed Date Issue Description Issue State Attribute Issue Disposition Issue Number Issue Entered By Issue Date Entered Issue Found By
517
Issu e e n vir on me n t var iab l e s
Variable FNDD FNDG FNDV FOLDS HEML HTTPURL HWSW LINK LNKB LNKC LNKID LNKP MODB MODD NMLNK NUMR PRIO PROD PROJNAME RBDE RBDI RBYC REFR RELH REPR SEVR
Description Issue Date Found Issue Group Issue Version Found Folders Containing Item Issue Has Emails HTTP Hyperlink Issue Other Hardware and Software Issue Has Links Issue Has Broken Links Issue Is A Link Child Link IDs Containing Item Issue Is A Link Parent Issue Modified By Issue Date Modified Number of Links Issue Number Reported Issue Priority Issue Product Project Name Issue Found By Department Issue Found By Division Issue Found By Company Issue Reference Issue Has Release Notes Issue Reproducible Issue Severity
518
Re q u ir e me n t e n vir on me n t var iab l e s
Variable STAT STEP SUMM SUSPT TCFG TTSTUDIOURL TYPE WORK WRKH
Description Issue Status Issue Steps to Reproduce Issue Summary Is Marked As Suspect Issue Test Config TTSTUDIO Hyperlink Issue Type Issue Workaround Issue Has Workaround
Requirement environment variables

The following environment variables can be used to return values from the requirement that caused the executable to run. Variable BKLNK FOLDS HEML HTTPURL LNKID NMLNK PROJNAME RQABY RQADT RQATO RQCBY RQCDT RQCSD Description Number of Broken Links Folders Containing Item Requirement Has Emails HTTP Hyperlink Link IDs Containing Item Number of Links Project Name Requirement Currently Assigned By Requirement Currently Assigned Date Requirement Currently Assigned To Requirement Created By Requirement Closed Date Requirement Closed By
519
Re q u ir e me n t e n vir on me n t var iab l e s
Variable RQDOCLST RQDSC RQDTC RQDTE RQDTM RQENB RQFIL RQHBL RQHLK RQICL RQIPL RQISSHRD RQLCKRSN RQLOC RQLST RQNDOC RQNUM RQPRI RQSCC RQSTA RQSTS RQSUM RQTYP SUSPT TAGNM TTSTUDIOURL
Description Requirement Document List Requirement Description Requirement Date Created Requirement Date Entered Requirement Date Modified Requirement Entered By Requirement Has File Attachments Requirement Has Broken Links Requirement Has Links Requirement Is Child Link Requirement Is Parent In Link Requirement Is Shared Requirement Lock Reason Requirement Creation Method Requirement Last Modified By Number of Requirement Documents Requirement Number Requirement Importance Has Source Code Files Requirement State Attribute Requirement Status Requirement Summary Requirement Type Is Marked As Suspect Tag TTStudio Hyperlink
520
Re q u ir e me n t d ocu me n t e n vir on me n t var iab l e s
Variable VERSN VLOCK
Description Version Version Is Locked
Requirement document environment variables

The following environment variables can be used to return values from the requirement document that caused the executable to run. Variable BKLNK FOLDS HEML HTTPURL LNKID NMLNK PROJNAME RDABY RDADT RDATO RDCBY RDCDT RDCSD RDDSC RDDTC RDDTM RDFIL RDHBL RDHLK RDICL Description Number of Broken Links Folders Containing Item Requirement Document Has Emails HTTP Hyperlink Link IDs Containing Item Number of Links Project Name Requirement Document Currently Assigned By Requirement Document Currently Assigned Date Requirement Document Currently Assigned To Requirement Document Created By Requirement Document Closed Date Requirement Document Closed By Requirement Document Description Requirement Document Date Created Requirement Document Date Modified Requirement Document File Attachments Requirement Document Has Broken Links Requirement Document Has Links Requirement Document Is Child Link
521
Te st case e n vir on me n t var iab l e s
Variable RDIPL RDLOC RDLST RDNAM RDNSP RDNUM RDSCC RDSTA RDSTS SUSPT VERSN VLOCK TTSTUDIOURL
Description Requirement Document Is Parent In Link Requirement Document Creation Method Requirement Document Last Modified By Requirement Document Name Number of Snapshots Requirement Document Number Has Source Code Files Requirement Document State Attribute Requirement Document Status Is Marked As Suspect Version Version Is Locked TTSTUDIO Hyperlink
Test case environment variables

The following environment variables can be used to return values from the test case that caused the executable to run. Variable BKLNK FOLDS HEML HTTPURL LNKID NMLNK PROJNAME SUSPT TCABY Description Number of Broken Links Folders Containing Item Test Case Has Emails HTTP Hyperlink Link IDs Containing Item Number of Links Project Name Is Marked As Suspect Test Case Currently Assigned By
522
Te st case e n vir on me n t var iab l e s
Variable TCADT TCATO TCAUT TCCBY TCCDT TCCSD TCCTR TCDTC TCDTM TCEST TCFIL TCFTR TCHBL TCHLK TCICL TCIPL TCITR TCLOC TCLST TCNUM TCOTR TCPTR TCSCC TCSCR TCSGM TCSTA
Description Test Case Currently Assigned Date Test Case Currently Assigned To Test Case Is A Automated Test Test Case Created By Test Case Closed Date Test Case Closed By Total Number Of Closed Test Runs Test Case Date Created Test Case Date Modified Test Case Estimated Time Test Case File Attachments Test Case Number Of Test Runs Failed Test Case Has Broken Links Test Case Has Links Test Case Is Child Link Test Case Is Parent In Link Test Case Number Of Test Runs Other Test Case Creation Method Test Case Last Modified By Test Case Number Total Number Of Open Test Runs Test Case Number Of Test Runs Passed Has SCC Files Test Case Has Scripts Test Run Steps Mode Test Case State Attribute
523
Te st r u n e n vir on me n t var iab l e s
Variable TCSTP TCSTS TCSUM TCTTR TCTYP TTSTUDIOURL
Description Test Case Steps Test Case Status Test Case Summary Total Number Of Test Runs Test Type TTSTUDIO Hyperlink
Test run environment variables

The following environment variables can be used to return values from the test run that caused the executable to run. Variable BKLNK FOLDS HEML HTTPURL LNKID NMLNK PROJNAME SUSPT TRABY TRADT TRATO TRAUT TRCBY TRCDT TRCOV TRCSD Description Number of Broken Links Folders Containing Item Test Run Has Emails HTTP Hyperlink Link IDs Containing Item Number of Links Project Name Is Marked As Suspect Test Run Currently Assigned By Test Run Currently Assigned Date Test Run Currently Assigned To Test Run Is an Automated Test Test Run Created By Test Run Closed Date Test Variants Test Run Closed By
524
Te st r u n e n vir on me n t var iab l e s
Variable TRCST TRDTC TRDTM TREST TRFIL TRHBL TRHLK TRICL TRIPL TRLOC TRLST TRNUM TRPST TRRES TRRST TRSCC TRSCR TRSET TRSTA TRSTP TRSTS TRSUM TRTCN TRTYP TTSTUDIOURL
Description Test Run Completion Status Test Run Date Created Test Run Date Modified Test Run Estimated Time Test Run File Attachments Test Run Has Broken Links Test Run Has Links Test Run Is Child Link Test Run Is Parent In Link Test Run Creation Method Test Run Last Modified By Test Run Number Problem Statement Has Run Results Test Run Result Status Has SCC Files Test Run Has Scripts Test Run Set Test Run State Attribute Test Run Steps Test Run Status Test Run Summary Test Case Number Test Type TTSTUDIO Hyperlink
525
Cu st om fie l d e n vir on me n t var iab l e s
Custom field environment variables

You can use environment variables to return custom field values. However, you need to look up the variable value in TestTrack. 1. Choose Tools > Administration > Custom Fields. 2. Select the custom field and click Edit. 3. Use the Field code field without the percent symbols as the environment variable. For example, Z_ CUSTOMFIELD.
Workflow event environment variables

To use environment variables to return workflow event values, you need to look up the variable value in TestTrack. 1. Choose Tools > Administration > Workflow. 2. Click the Events tab. 3. Select the event and click Edit. 4. Click the Fields tab. 5. Use Field Code column value without the percent symbols as the environment variable. For example, Z_ASSB returns the value from the Assign By field. Note: Use the EVT_CNT environment variable to return the number that corresponds to the order of the event within all record events. For example, EVT4_Z_ASSB returns the Assign By value from the fourth event on the record.
File attachment environment variables

Use the following environment variables to return data about the files attached to the specific issue, test case, or test run that caused the executable to run. Environment Description variable ATT_CNT Number that corresponds to the order of the attachment in all record file attachments; used to identify each attachment in ATT_NAME and ATT_LOC File attachment name Example Not applicable
ATT_NAME
ATT4_NAME returns the name of the fourth file attachment ATT3_LOC returns the location of the third file attachment
ATT_LOC
Path to the DAT file if it is stored on the local hard drive or the database name if the file is stored on the TestTrack Server
526
S ou r ce fil e at t ach me n t e n vir on me n t var iab l e s
Source file attachment environment variables

Use the following environment variables to return data about the source files attached to the specific issue, test case, or test run that caused the executable to run. Environment Description variable SCC_CNT Number that corresponds to the order of the source file attachment in all record source file attachments; used to identify each attachment in SCC_NAME, SCC_TIME, and SCC_VERS Source file path and file name Example Not applicable
SCC_NAME
SCC4_NAME returns the path and file name of the fourth source file attachment SCC4_TIME returns the date and time the fourth source file was attached SCC4_VERS returns the versions of the fourth source file attached to the record
SCC_TIME
Date and time the source file was attached to the record
SCC_VERS
Source file versions attached to the record
527
Appendix C: Field Codes

Field codes are used to build customized emails that provide information specific to the record that triggered the notification or, in the case of an email acknowledgment, was imported via email. If you are creating an ad hoc report, you can use field codes to include specific project information for the report. You can also use field codes to build personalized SoloSubmit web pages that provide information specific to your company and your customers use of SoloSubmit. For example, the sequence %DATS% is replaced with the current date format. The sequence %DNUM% is replaced with the issue number.
Field code notes

n
All dates use system-defined date formats. TestTrack uses the short-date style of the regional settings properties defined in the operating system. To include a percent sign (%) in the body of a message, include two percent signs in a row (e.g., %%). Email notifications support field codes in the email subject line. You can include personalized subjects such as Re:%SUMM% which expand to include the issues summary field in the emails subject. If a field code is used outside an HTML tag, use the percent signs. If a field code is used instead an HTML tag, do not use the percent signs. For example: Field code used inside an HTML tag: <input type=Text name=fname> Field code used outside an HTML tag: <select name=%PROD_CO%> %PROD_V% </select>
Issue field codes

You can use label field codes to include field labels in emails. See Label field codes, page 540. Field code %ACTHR% %BKLNK% %CHNG% %CHNGHTML% %CLCER% %COMP% %CREB% %CRED% %CREL% %DCAB% Description Actual Hours Number of Broken Links Changes Changes with Differences (HTML) Has Calculation Error Issue Component Issue Created By Issue Date Created Issue Creation Method Issue Current Assignment By
529
Issu e fie l d cod e s
Field code %DCAD% %DCAT% %DCLB% %DCLD% %DESC% %DFFIL% %DFSA% %DISP% %DNUM% %DTENS% %ENTB% %ENTD% %ESTHR% %FNDB% %FNDD% %FNDG% %FNDV% %FOLDS% %HEML% %HTTPURL% %HWSW% %LINK% %LNKB% %LNKC% %LNKID% %LNKP%
Description Issue Current Assignment Date Issue Currently Assigned To Issue Closed By Issue Closed Date Issue Description Issue Has File Attachments Issue State Attribute Issue Disposition Issue Number Date Entered State Issue Entered By Issue Date Entered Estimated Hours Issue Found By Issue Date Found Issue Found by Group Issue Version Found Folders Containing Item Issue Has Emails HTTP Hyperlink Issue Other Hardware and Software Issue Has Links Issue Has Broken Links Issue Is Child in Link Link IDs Containing Item Issue Is Parent in Link
530
Issu e fie l d cod e s
Field code %MODB% %MODD% %NMLNK% %NUMR% %NURL% %PERDN% %PRIO% %PRNM% %PROD% %PROJNAME% %RBDE% %RBDI% %RBYC% %REFR% %RELH% %REMHR% %REPR% %SEVR% %STAT% %STEP% %STPTS% %SUMM% %SUSPT% %TCFG% %TTSTUDIOURL% %TYPE%
Description Issue Modified By Issue Date Modified Number of Links Issue Number Reported Issue Hyperlink Percent Done Issue Priority Project Name (from Project Options) Issue Product Project Name Issue Found By Department Issue Found By Division Issue Found By Company Issue Reference Issue Has Release Notes Remaining Hours Issue Reproducible Issue Severity Issue Status Issue Steps to Reproduce Story Points Issue Summary Is Marked As Suspect Issue Test Config (value pulled from Computer Config list) TTSTUDIO Hyperlink Issue Type
531
Re q u ir e me n t d ocu me n t fie l d cod e s
Field code %VARNC% %WORK% %WRKH%
Description Variance Issue Workaround Issue Has Workaround
Requirement document field codes

You can use label field codes to include field labels in emails. See Label field codes, page 540. Field code %ACTHR% %BKLNK% %CHNG% %CHNGHTML% %CLCER% %DTENS% %ESTHR% %FOLDS% %HEML% %HTTPURL% %LNKID% %NMLNK% %PERDN% %PRNM% %PROJNAME% %RDABY% %RDADT% %RDATO% %RDCBY% %RDCDT% Description Actual Hours Number of Broken Links Changes Changes with Differences (HTML) Has CalculationError Date Entered State Estimated Hours Folders Containing Item Item Has Emails HTTPHyperlink Links IDs Containing Item Number of Links Percent Done Project Name (from Project Options) Project Name Requirement Document Currently Assigned By Requirement Document Currently Assigned Date Requirement Document Currently Assigned To Requirement Document Created By Requirement Document Closed Date
532
Re q u ir e me n t fie l d cod e s
Field code %RDCSD% %RDDSC% %RDDTC% %RDDTM% %RDFIL% %RDHBL% %RDHLK% %RDICL% %RDIPL% %RDLOC% %RDLST% %RDNAM% %RDNRQ% %RDNSP% %RDNUM% %RDSCC% %RDSTA% %RDSTS% %REMHR% %STPTS% %SUSPT% %TTSTUDIOURL% %VERSN% %VLOCK% %VRANC%
Description Requirement Document Closed By Requirement Document Description Requirement Document Date Created Requirement Document Date Modified Requirement Document Has File Attachments Requirement Document Has Broken Links Requirement Document Has Links Requirement Document Is Child Link Requirement Document Is Parent In Link Requirement Document Creation Method Requirement Document Last Modified By Requirement Document Name Number of Requirements Number of Snapshots Requirement Document Number Has Source Code Files Requirement Document State Attribute Requirement Document Status Remaining Hours Story Points Is Marked As Suspect TTSTUDIO Hyperlink Version Version Is Locked Variance
Requirement field codes

You can use label field codes to include field labels in emails. See Label field codes, page 540.
533
Re q u ir e me n t fie l d cod e s
Field code %ACTHR% %BKLNK% %CHNG% %CHNGHTML% %ESTHR% %FOLDS% %HEML% %HTTPURL% %LNKID% %NMLNK% %PERDN% %PRNM% %PROJNAME% %REMHR% %RQABY% %RQADT% %RQATO% %RQCBY% %RQCDT% %RQCSD% %RQDOCLST% %RQDSC% %RQDTC% %RQDTE% %RQDTM% %RQENB%
Description Actual Hours Number of Broken Links Changes Changes with Differences (HTML) Estimated Hours Folders Containing Item Item Has Emails HTTPHyperlink Links IDs Containing Item Number of Links Percent Done Project Name (from Project Options) Project Name Remaining Hours Requirement Currently Assigned By Requirement Currently Assigned Date Requirement Currently Assigned To Requirement Created By Requirement Closed Date Requirement Closed By Requirement Document List Requirement Description Requirement Date Created Requirement Date Entered Requirement Date Modified Requirement Entered By
534
Te st case fie l d cod e s
Field code %RQFIL% %RQHBL% %RQHLK% %RQICL% %RQIPL% %RQISSHRD% %RQLCKRSN% %RQLOC% %RQLST% %RQNDOC% %RQNUM% %RQPRI% %RQSCC% %RQSTA% %RQSTS% %RQSUM% %RQTYP% %STPTS% %SUSPT% %TAGNM% %TTSTUDIOURL% %VERSN% %VLOCK% %VNUMV% %VRANC%
Description Requirement Has File Attachments Requirement Has Broken Links Requirement Has Links Requirement Is Child Link Requirement Is Parent In Link Requirement Is Shared Requirement Lock Reason Requirement Creation Method Requirement Last Modified By Number of Requirement Documents Requirement Number Requirement Importance Has Source Code Files Requirement State Attribute Requirement Status Requirement Summary Requirement Type Story Points Is Marked As Suspect Tag TTSTUDIO Hyperlink Version Version Is Locked Number of Item Versions Variance
Test case field codes

535
Te st case fie l d cod e s
Field code %ACTHR% %BKLNK% %CHNG% %CHNGHTML% %CLCER% %DTENS% %ESTHR% %FOLDS% %HEML% %HTTPURL% %LNKID% %NMLNK% %PERDN% %PRNM% %PROJNAME% %REMHR% %STPTS% %SUSPT% %TCADT% %TCATO% %TCAUT% %TCCBY% %TCCDT% %TCCSD% %TCCTR% %TCDTC%
Description Actual Hours Number of Broken Links Changes Changes with Differences (HTML) Has CalculationError Date Entered State Estimated Hours Folders Containing Item Test Case Has Emails HTTP Hyperlink Link IDs Containing Item Number of Links Percent Done Project Name (from Project Options) Project Name Remaining Hours Story Points Is Marked As Suspect Test Case Currently Assigned Date Test Case Currently Assigned To Test Case Is A Automated Test Test Case Created By Test Case Closed Date Test Case Closed By Total Number Of Closed Test Runs Test Case Date Created
536
Te st r u n fie l d cod e s
Field code %TCDTM% %TCEST% %TCFIL% %TCFTR% %TCHBL% %TCHLK% %TCICL% %TCIPL% %TCITR% %TCLOC% %TCLST% %TCNUM% %TCOTR% %TCPTR% %TCSCC% %TCSCR% %TCSGM% %TCSTA% %TCSTP% %TCSTS% %TCSUM% %TCTTR% %TCTYP% %TTSTUDIOURL% %VRANC%
Description Test Case Date Modified Test Case Estimated Run Time Test Case File Attachments Test Case Number Of Test Runs Failed Test Case Has Broken Links Test Case Has Links Test Case Is Child Link Test Case Is Parent In Link Test Case Number Of Test Runs Undetermined Test Case Creation Method Test Case Last Modified By Test Case Number Total Number Of Open Test Runs Test Case Number Of Test Runs Passed Has Source Code Files Test Case Has Scripts Test Run Steps Mode Test Case State Attribute Test Case Steps Test Case Status Test Case Summary Total Number Of Test Runs Test Type TTSTUDIO Hyperlink Variance
Test run field codes

537
Field code %ACTHR% %BKLNK% %CHNG% %CHNGHTML% %CLCER% %DTENS% %ESTHR% %FOLDS% %HEML% %HTTPURL% %LNKID% %NMLNK% %PERDN% %PRNM% %PROJNAME% %REMHR% %STPTS% %SUSPT% %TRABY% %TRADT% %TRATO% %TRAUT% %TRCBY% %TRCDT% %TRCOV% %TRCSD%
Descriptions Actual Hours Number of Broken Links Changed Changes with Differences (HTML) Has CalculationError Date Entered State Estimated Hours Folders Containing Item Test Run Has Emails HTTP Hyperlink Link IDs Containing Item Number of Links Percent Done Project Name (from Project Options) Project Name Remaining Hours Story Points Is Marked As Suspect Test Run Currently Assigned By Test Run Currently Assigned Date Test Run Currently Assigned To Test Run Is an Automated Test Test Run Created By Test Run Closed Date Test Variants Test Run Closed By
538
Field code %TRCST% %TRDTC% %TRDTM% %TREST% %TRFIL% %TRHBL% %TRHLK% %TRICL% %TRIPL% %TRLOC% %TRLST% %TRNUM% %TRPST% %TRRES% %TRRST% %TRSCC% %TRSCR% %TRSET% %TRSTA% %TRSTP% %TRSTS% %TRSUM% %TRTCN% %TRTYP% %TTSTUDIOURL% %VRANC%
Descriptions Test Run Completion Status Test Run Date Created Test Run Date Modified Test Run Estimated Run Time Test Run File Attachments Test Run Has Broken Links Test Run Has Links Test Run Is Child Link Test Run Is Parent In Link Test Run Creation Method Test Run Last Modified By Test Run Number Problem Statement Has Run Results Test Run Result Status Has Source Code Files Test Run Has Scripts Test Run Set Test Run State Attribute Test Run Steps Test Run Status Test Run Summary Test Case Number Test Type TTSTUDIO Hyperlink Variance
539
Lab e l fie l d cod e s
Label field codes

You can use label field codes to include field labels in emails. For example, you can use the Summary label field code (%SUMM_L%) before the Summary field code (%SUMM%) to include the Summary label with the value. Label field codes only return the field label name, not the field data.
540
Issues
Field label Component Computer Config Custom Fields Date Date Entered Date Found Issue issue Issues issues Issue(s) issue(s) Description DF Disposition Entered by Found by Other Hardware and Software Priority Product Reference Reproduced Severity Status Field code %COMP_L% %TCFG_L% %CFTB_L% %DATE_L% %ENTD_L% %FNDD_L% %DFUS_L% %DFLS_L% %DFUP_L% %DFLP_L% %DFUM_L% %DFLM_L% %DESC_L% %DFABBRU_L% %DISP_L% %ENTB_L% %FNDB_L% %HWSW_L% %PRIO_L% %PROD_L% %REFR_L% %REPR_L% %SEVR_L% %STAT_L%
541
Field label Steps to Reproduce Summary Type Version Version Found
Field code %STEP_L% %SUMM_L% %TYPE_L% %VERS_L% %FNDV_L%
Folders
Field label Details Folder folder Folders folders Folder(s) folder(s) Notes Release Planning Web View Field code %DETLS_L% %FDUS_L% %FDLS_L% %FDUP_L% %FDLP_L% %FDUM_L% %FDLM_L% %NOTES_L% %RELPL_L% %WEBVW_L%
542
Requirements
Field label Custom Fields Date Entered Description Detail Entered By Importance Overview Relationship Relationships Requirement requirement Requirements requirements Requirement(s) requirement(s) Status Summary Tag Workflow Field code %CFRM_L% %RQDTENT_L% %RQDESC_L% %RQDETAIL_L% %RQENTBY_L% %RQPRIOR_L% %RQOVERVIEW_L% %RQRELUS_L% %RQRELUP_L% %RQUS_L% %RQLS_L% %RQUP_L% %RQLP_L% %RQUM_L% %RQLM_L% %RQSTATUS_L% %RQSUMM_L% %RQTAG_L% %RQWORKFLOW_L%
543
Field label Description Document document Documents documents Document(s) document(s) Name Number RD Requirement Document requirement document Requirement Documents requirement documents Requirement Document(s) requirement document(s) Snapshot snapshot Snapshots Specification Document specification document Status Field code %RDDESC_L% %DCUS_L% %DCLS_L% %DCUP_L% %DCLP_L% %DCUM_L% %DCLM_L% %RDNAME_L% %RDNUM_L% %RDABBRU_L% %RDUS_L% %RDLS_L% %RDUP_L% %RDLP_L% %RDUM_L% %RDLM_L% %RDSNAPUS_L% %RDSNAPLS_L% %RDSNAPUP_L% %SPECDOCUS_L% %SPECDOCLS_L% %RDSTATUS_L%
544
Test cases
Field label Comment comment Comments comments Custom Fields Expected Result expected result Expected Results expected results Step step Step Note step note Step Notes step notes Steps Steps steps TC Test Case test case Test Cases test cases Test Case(s) test case(s) Field code %CMNTUS_L% %CMNTLS_L% %CMNTUP_L% %CMNTUP_L% %CTCM_L% %EXPRESUS_L% %EXPRESLS_L% %EXPRESUP_L% %EXPRESLP_L% %STEPUS_L% %STEPLS_L% %STPNTUS_L% %STPNTLS_L% %STPNTUP_L% %STPNTLP_L% %STEPSTAB% %STEPUP_L% %STEPLP_L% %TCABBRU_L% %TCUS_L% %TCLS_L% %TCUP_L% %TCLP_L% %TCUM_L% %TCLM_L% Tab name Additional information
545
Test runs
Field label Actual Result actual result Actual Results actual results Fail fail Failed failed Fails fails Pass pass Passed passed Passes passes Problem Statement problem statement Problem Statements problem statements Step Result step result Step Results step results Field code %ACTRSUS_L% %ACTRSLS_L% %ACTRSUP_L% %ACTRSLP_L% %FLU_L% %FLL_L% %FAIL_L% %FAILL_L% %FAILSU_L% %FAILSL_L% %PSU_L% %PSL_L% %PASS_L% %PASSL_L% %PASSESU_L% %PASSESL_L% %PRBSTUS_L% %PRBSTLS_L% %PRBSTUP_L% %PRBSTLP_L% %STPRSUS_L% %STPRSLS_L% %STPRSUP_L% %STPRSLP_L% Step result Step result Test run result Test run result Step result Step result Step result Step result Test run result Test run result Step result Step result Additional information
546
Field label Actual Result actual result Actual Results actual results Fail fail Failed failed Fails fails Pass pass Test Run test run Test Runs test runs Test Run(s) test run(s) TR Undetermined undetermined Undetermined undetermined
Field code %ACTRSUS_L% %ACTRSLS_L% %ACTRSUP_L% %ACTRSLP_L% %FLU_L% %FLL_L% %FAIL_L% %FAILL_L% %FAILSU_L% %FAILSL_L% %PSU_L% %PSL_L% %TRUS_L% %TRLS_L% %TRUP_L% %TRLP_L% %TRUM_L% %TRLM_L% %TRABBRU_L% %OTHR_L% %OTHRL_L% %UNDU_L% %UNDL_L%
Additional information
Step result Step result Test run result Test run result Step result Step result Step result Step result
Test run result Test run result Step result Step result
547
Test variants
Field label Test Variant test variant Variant variant Field code %CVGU_L% %CVGL_L% %VARU_L% %VARL_L%
548
Miscellaneous
Field label Actual Hours Customer customer Customers customers Customer(s) customer(s) Email Estimated Hours Lock Locked locked Percent Done Remaining Hours Source Code Story Points story points Suspect suspect Unlock Unlocked Variance Field code %ACTHR_L% %CSUS_L% %CSLS_L% %CSUP_L% %CSLP_L% %CSUM_L% %CSLM_L% %EMTB_L% %ESTHR_L% %RDLOCK_L% %RDLOCKED_L% %RDLOCKEDL_L% %PERDN_L% %REMHR_L% %SCCL_L% %STPTS_L% %STPTSL_L% %RDSUSPECT_L% %RDSUSPECTL_L% %RDUNLOCK_L% %RDUNLOCKED_L% %VRANC_L%
549
Cu st om fie l d cod e s
Custom field codes

Custom field codes can be used for issue, requirement, requirement document, test case, and test run custom fields displayed in the Add, Edit, or View dialog boxes, test variants, and event custom fields configured in the workflow. Custom field codes use the same format as general field codes except they start with a Z. Control name code %Z_customfield_CN%
n
Value code %Z_customfield_V%
Label code %Z_customfield_L%
Static field number Custom field #
To find a custom field code, choose Tools > Administration > Custom Fields. Select a record Type. Custom field codes are displayed in the Field Code column. To find an event custom field code, choose Tools > Administration > Workflow. Select a record Type. Click the Events tab. Select an event and click Edit. Click the Fields tab. Custom field codes are displayed in the Field Code column. Custom fields are dynamically built based on the project. In one project, %customfield1% can be a check box while in another project %customfield1% is an edit box. If you use pop-up menus for custom fields, specify the internal record ID value for each entry. If you use custom fields with static SoloSubmit web pages, you need to use the static field number. To find this number, generate a SoloSubmit page and view the source. Copy the static field number from the source document. If you are using custom fields with dynamically generated SoloSubmit pages, %DEFECTCUSTOMFIELDS% returns a list of all custom fields.
n n
550
Appendix D: Report Stylesheets

Stylesheets are templates you can use to generate formatted reports. Several Extensible Style Language (XSL) stylesheets are installed with TestTrack to help you create reports with predefined layout and design options. If you want to perform extensive customization or if you want to create stylesheets, you need a solid understanding of HTML, XML, and XSL.
Customizing stylesheets
You can customize an existing XSL stylesheet or create your own and add it to the TestTrack project. Stylesheets are generally located in the TestTrack application directory (e.g., Program Files/ Seapine/ TestTrack/StyleSheets).
n
To customize an existing stylesheet, open the corresponding report folder, select the stylesheet, and modify it using a third-party tool. To add a new stylesheet, use a third-party tool to create the stylesheet. Copy the completed stylesheet to the corresponding report folder. To include an image with a stylesheet, copy the image to the Images folder in the TestTrack directory. Add the following script to the stylesheet: <img> <xsl:attribute name=src> <xsl:value-of select=external:getserver-image(imagename.gif) /> </xsl:attribute> </img>
Note: For more information on editing stylesheets, we recommend performing a web search on 'editing xsl stylesheets'.
Refreshing stylesheet menus

The TestTrack Server periodically searches the project for new stylesheets. You can determine the frequency of this update by modifying project options. 1. Choose Tools > Administration > Project Options. 2. Select the Reports category. 3. Select how often the server looks for new stylesheets.
4. Click OK.
551
De t ail r e p or t st yl e sh e e t s
Detail report stylesheets

The following stylesheets can be used to create detail reports. Detail report stylesheets are generally located in the Stylesheets/Detail directory in the TestTrack application directory.
Customers
Stylesheet name CustomerDetailReport.xslt Includes: All customer information including computer configurations, the number and percentage of reported issues, and the date of the last reported issue.
Issues
Stylesheet name IssueDetailReport.xslt Includes: All issue information for all reported by records including workflow events, folder, and source file information. Does not include tracked email or information about linked items. All issue information for all reported by records including tracked email. Does not include information about linked items. All issue information for all reported by records including information about linked items. Does not include tracked email. Information from the issue History tab. Information from the issue Workflow tab.
IssueDetailReportWithEmails.xslt
IssueDetailReportWithLinks.xslt
IssueHistoryReport.xslt IssueLifeCycleSummaryReport.xslt
IssueLinksSummaryReport.xslt
The relationship, number, type, summary, and status of all items linked to issues and the link definition used. All release note entries for issues including the release version. General issue information, issue summary, workarounds, and source file information. Information from the issue Found by, Steps to Reproduce, Computer Config, and Attachments mini tabs on the Detail tab for all reported by records.
IssueReleaseNotes.xslt IssueRevisionHistory.xslt
IssueSummaryReport.xslt
552
Folders
Stylesheet name FolderDetailReport.xslt Includes: All folder information including the contents of the Details, Web View, and Release Planning tabs. The type, number, summary, and status of items in folders is also displayed. All folder information including the type, number, summary, and status of items in all child folders.
FolderDetailReportRecursive.xslt
Requirements
Stylesheet name RequirementDetailReport.xslt Includes: All requirement information including version, document, snapshot, and workflow events information. Does not include information about linked items. All requirement information including information about linked items. Information about each test case linked to requirements including the total number of linked test runs and the test run completion status and results. The report can be filtered by folder and includes buttons to expand or collapse all folders. Requirements, test cases linked to each requirement, and issues linked to each test case in grid format. Requirement and test case summary information and issue status information is also displayed. Information from the requirement History tab. Information from the requirement Detail tab. Information about each test case linked to requirements including test case steps and expected results, the total number of linked test runs, and the test run completion status and results. Information about each test run generated from test cases linked to requirements. Includes the total number of linked test runs, the test run completion status and results, and the test run set. The report can be filtered by test run set and includes buttons to expand or collapse all test run sets.
RequirementDetailReportWithLinks.xslt
RequirementFolderCoverageReport.xslt
RequirementForwardTraceabilityReport.xslt
RequirementHistoryReport.xslt RequirementSummaryReport.xslt RequirementTestCaseCoverageReport.xslt
RequirementTestRunCoverageReport.xslt
553
Stylesheet name RequirementDocumentDetailReport.xslt Includes: All requirement document information including snapshot and workflow event information. Does not include information about linked items. Requirements included in a requirement document organized by type, the test cases linked to each requirement, and the issues linked to each test case in grid format. Issue status is also displayed. Requirement summary information and descriptions from the Specification Document window. Information from the requirement document History tab. All requirements in a requirement document and any items linked to the requirements in hierarchical outline format. Tag, summary, risk, difficulty, and status information is also displayed. Information from the requirement document Detail tab.
RequirementDocumentForwardTraceabilityReport.xslt
RequirementDocumentFullSpecificationReport.xslt
RequirementDocumentHistoryReport.xslt
RequirementDocumentImpactReport.xslt
RequirementDocumentSummaryReport.xslt
Security groups
Stylesheet name SecurityGroupComparisonReport.xslt Includes: Enabled and disabled command security and field security options for all or selected security groups. Security group details including the users and customers in the group and enabled and disabled command security and field security options.
UserGroupDetailReport.xslt
554
Test cases
Stylesheet name TestCaseBackwardsTraceabilityReport.xslt Includes: A list of test cases and linked parent requirements in grid format. All test case information including steps, test variants, workflow events, generated test runs and status, and linked items. Information from the test case History tab. Information about test runs generated from test cases including number, assigned to user, due date, test run set, status, and test variants. Includes a summary of items linked to each test case. Information from the test case Detail tab and steps.
TestCaseDetailReport.xslt
TestCaseHistoryReport.xslt TestCaseRunHistoryDetailReport.xslt
TestCaseSummaryReport.xslt
Test configs
Stylesheet name TestConfigDetailReport.xslt Includes: Test configuration information including CPU and peripherals data.
555
Dist r ib u t ion r e p or t st yl e sh e e t s
Test runs
Stylesheet name TestRunDetailReport.xslt Includes: All test run information including test case details, steps, test variants, workflow events, and linked items. If test runs are in detail grid view, also includes actual results and step results. All test run information including steps, test variants, and workflow events. Does not include linked items. If test runs are in detail grid view, also includes actual results and step results. Information from the test run History tab. All test run information including steps and test variants. Does not include linked items or workflow events. Used to generate a printable report for testers to write results during testing. Includes fields for handwritten information and lines for date/time, additional variants tested, results, problems encountered during the test, and signature. If test runs are in detail grid view, also includes actual results and step results. Test run summary information, steps, and test variants. Used to generate a printable report for testers to write results during testing. Includes fields for handwritten information and lines for date/time, additional variants tested, results, problems encountered during the test, and signature. If test runs are in detail grid view, also includes actual results and step results. Information from the test run Detail tab and steps. If test runs are in detail grid view, also includes actual results and step results.
TestRunExecutionDetailReport.xslt
TestRunHistoryReport.xslt TestRunReport.xslt
TestRunStepsDetailReport.xslt
TestRunSummaryReport.xslt
Users
Stylesheet name UserDetailReport.xslt Includes: All user information including computer configurations, last login date/time, the number and percentage of reported, currently assigned, and closed issues, and the date of the last reported issue.
Distribution report stylesheets

The following stylesheets can be used to create distribution reports. Distribution report stylesheets are generally located in the Stylesheets/Distribution directory in the TestTrack application directory. Name NonDetailReport.xslt Includes: Field data in columns with field names as column headings. Optionally includes totals or a chart that displays data as a count or percentage.
556
List r e p or t st yl e sh e e t s
List report stylesheets

The following stylesheets can be used to create list reports. List report stylesheets are generally located in the Stylesheets/List directory in the TestTrack application directory. Name GroupingListReport.xslt Includes: Field data in columns with field names as column headings. Groups data with common values into rows that can be expanded or collapsed. Includes interactive drill-down charts of grouped data that can be altered directly in the browser. Field data in columns with field names as column headings. Column headings are displayed above each data row. Field data in columns with field names as column headings. Includes interactive drill-down charts that can be altered directly in the browser when two or more columns contain numeric data. At least one numeric data column must be included in the report to generate a chart. Field data in columns with field names as column headings. Field data in columns in columns with field names as column headings. Retains line breaks used in description fields.
ListReportColHdrsEachRow.xslt
ListReportWithChart.xslt
NonDetailReport.xslt NonDetailReport_br.xslt
Release planning report stylesheets

The following stylesheets are used to create release planning reports. The stylesheet is automatically applied based on the report selected on the Report On tab in the Add Release Planning Report dialog box. Release planning report stylesheets are generally located in the Stylesheets/Custom directory in the TestTrack application directory. Report name Release Plan Stylesheet name ReleasePlanningReport.xslt Includes: Release planning folders and items in the folders. Displays the item number, summary, status, total number of man hours calculated for the release folder, estimated hours for each item and all items, target story points for the release folder, and actual story points entered for each item. A chart displays the number of man hours for the release versus the estimated effort, the number of story points for the release, or the number of items included in the release folder.
557
Re l e ase st at u s r e p or t st yl e sh e e t s
Report name Resource Allocation
Stylesheet name ResourceAllocationReport.xslt
Includes: Release planning folders and the items in the folders grouped by the assigned to user. Displays the item number, summary, status, story points entered for each item and totals for each user, man hours calculated for the release folder and each user, and estimated hours for each item and each user. A chart displays the number of estimated hours by user, the number of story points by user, or the number of assigned items by user.
Release status report stylesheets

The following stylesheets are used to create release status reports. The stylesheet is automatically applied based on the report selected on the Report On tab in the Add Release Status Report dialog box. Release status report stylesheets are generally located in the Stylesheets/Custom directory in the TestTrack application directory. Report name Burn Down Chart Stylesheet name BurnDownChartReport.xslt Includes: A chart that displays the work left for a release versus the time available in a project in hours or story points. Displays the burn down, remaining effort, actual effort, and estimated effort to complete. The backlog is generally displayed on the vertical axis and time is displayed on the horizontal axis. Requires a folder with release planning enabled. A chart that displays the work completed for a release versus the time available in a project in hours or story points. Displays the estimated and actual scope, actual hours, and predicted effort (trend). The effort is generally displayed on the vertical axis and time is displayed on the horizontal axis. Requires a folder with release planning enabled.
Burn Up Chart
BurnUpChartReport.xslt
558
Re l e ase st at u s r e p or t st yl e sh e e t s
Report name Cumulative Flow Chart
Stylesheet name CumulativeFlowChartReport.xslt
Includes: A chart that displays the estimated effort for completion of each item in a release grouped by each development phase (Not Started, In Progress, Done, and Accepted). Hours are displayed on the vertical axis and days, weeks, or months are displayed on the horizontal axis. Requires a folder with release planning enabled. A task board that displays columns and rows for each folder in an iteration. Items in folders are organized in columns based on their status in the current development phase (Not Started, In Progress, Done, and Accepted). Displays any available time tracking information for each item. Requires a folder with release planning enabled. A task board that displays columns and rows for each folder in an iteration. Items in folders are organized in configurable columns based on the workflow states mapped to each column in the report configuration. Displays any available time tracking information for each item. Requires a folder with release planning enabled. Items in release folders and the workflow events that affected time tracking information. Displays the story points, estimated hours, actual hours, remaining hours, percent complete, and difference in estimated versus actual hours for each item. Optionally includes a chart that displays the estimated time to completion, percent complete, or number of items. Requires a folder with release planning enabled. Requirements in a requirement document and any items linked to the requirements in hierarchical outline format. Tag, summary, status, and time tracking information (story points, estimated hours, actual hours, remaining hours, and percent complete) is also displayed for each item.
Folder Task Board
FolderTaskBoardReport.xslt
Folder Task Board Alternate Style Folder Task Board With Configurable Columns
FolderTaskBoardAlternateStyleReport.xslt
FolderTaskBoardWithConfigurableColumns.xslt
Release Status by Item
ReleaseStatusReport.xslt
Release Status by Specification Document
RequirementDocumentReleaseStatus.xslt
559
Time t r ackin g r e p or t st yl e sh e e t s
Report name Release Status by User
Stylesheet name ReleaseStatusByUserReport.xslt
Includes: Items in release folders grouped by user and workflow events that affected time tracking information. Displays the estimated hours, actual hours, remaining hours, percent complete, and difference in estimated versus actual hours for each item. Optionally includes a chart that displays the estimated time to completion, percent complete, or number of items. Requires a folder with release planning enabled. A chart that displays estimated hours, story points, and man hours for release folders and the average rate that teams are completing work for each iteration versus estimates. The chart includes the velocity or efficiency of estimated hours or story points. Hours or story points are displayed on the vertical axis and folders are displayed on the horizontal axis.
Velocity Chart
VelocityChartReport.xslt
Time tracking report stylesheets

The following stylesheets are used to create time tracking reports. The stylesheet is automatically applied based on the report selected on the Report On tab in the Add Time Tracking Report dialog box. Time tracking report stylesheets are generally located in the Stylesheets/Custom directory in the TestTrack application directory. Report name Time Tracking By Item Stylesheet name TimeTrackingByItem.xslt Includes: Time tracking workflow events entered on items grouped by item and user. Includes the item number, user who entered the event, event name, date the event was entered, item status, actual hours reported, and notes. Includes a chart that displays actual hours reported by item, the number of events by item, or the number of events by user for a specific item. Time tracking workflow events entered on items grouped by user and date. Includes the user who entered the event, date the event was entered, event name, item number, item status, actual hours reported, and notes. Includes a chart that displays actual hours reported by user, the number of items by user, or the number of events by date for a specific user.
Time Tracking By User
TimeTrackingByUser.xslt
560
Tr ace ab il it y r e p or t st yl e sh e e t s
Traceability report stylesheets

The following stylesheets are used to create traceability reports. The stylesheet is automatically applied based on the report selected on the Report On tab in the Add Traceability Report dialog box. Traceability report stylesheets are generally located in the Stylesheets/Custom directory in the TestTrack application directory. Report name Detailed Requirement Forward Traceability Report Stylesheet name RequirementForwardTraceabilityReportDetailed.xslt Includes: Requirements, test cases and test runs linked to each requirement, issues linked to each test case, other requirements and requirement documents each requirement is linked to, and any parent and child requirements in grid format. Requirement and test case summary information and issue status information is displayed. Requirements included in requirement documents by type, the test cases linked to each requirement, and the issues linked to each test case in grid format. Issue status is also displayed. All requirements in a requirement document and any items linked to the requirements in hierarchical outline format. Includes tag, summary, risk, difficulty, and status information. Information about test runs generated from test cases linked to requirements, organized by folder. Includes the total number of linked test runs, the test run completion status and results, and the folder. The report can be filtered by folder. A TestTrack TCM license is required to view the test runs. Requirements, test cases linked to each requirement, and issues linked to each test case in grid format. Requirement and test case summary information and issue status information is displayed.
Requirement Document Forward Traceability
RequirementDocumentForwardTraceabilityReport.xslt
Requirement Document Impact
RequirementDocumentImpactReport.xslt
Requirement Folder Coverage
RequirementFolderCoverageReport.xslt
Requirement Forward Traceability
RequirementForwardTraceabilityReport.xslt
561
Tr e n d r e p or t st yl e sh e e t s
Report name Requirement Test Case Coverage
Stylesheet name RequirementTestCaseCoverageReport.xslt
Includes: Information about each test case linked to requirements including test case steps and expected results, the total number of linked test runs, and the test run completion status and results. A TestTrack TCM license is required to view the test cases. Information about each test run generated from test cases linked to requirements Includes the total number of linked test runs, the test run completion status and results, and the test run set. The report can be filtered by test run set. A TestTrack TCM license is required to view the test runs. A list of test cases and the requirements the test cases are linked to in grid format. A TestTrack RM license is required to view the requirements.
Requirement Test Run Coverage
RequirementTestRunCoverageReport.xslt
Test Case Backwards Traceability
TestCaseBackwardsTraceabilityReport.xslt
Trend report stylesheets

The following stylesheets can be used to create trend reports. Trend report stylesheets are generally located in the Stylesheets/Trend directory in the TestTrack application directory. Name NonDetailReport.xslt Includes: Field data in columns with field names as column headings. Optionally includes a chart that displays items in a timeline.
List window report stylesheets

The following stylesheets can be used when printing detail reports from list windows. See Printing list window records, page 27. You can set the default stylesheet for each list window in local options. See Setting stylesheet options, page 344. List window Customers Stylesheet CustomerDetailReport.xslt Includes: All customer information including computer configurations, the number and percentage of reported issues, and the date of the last reported issue. See Detail report stylesheets, page 552.
Issues
Use any of the issue detail report stylesheets
562
List win d ow r e p or t st yl e sh e e t s
List window Filters
Stylesheet FilterDetailReport.xslt
Includes: All filter information including description, access, and restrictions. Details of items included in the selected folder including workflow events. Details of items included in the selected folder excluding workflow events. Report settings including the title, type, data reported on, stylesheet, and other selected options. See Detail report stylesheets, page 552.
Folders
FolderItemDetailReport.xslt
FolderItemSummaryReport.xslt
Reports
ReportDetailReport.xslt
Requirements
Use any of the requirement detail report stylesheets Use any of the requirement document detail report stylesheets UsersGroupDetailReport.xslt
Requirement Documents
See Detail report stylesheets, page 552.
Security Groups
All security group information including the users and customers in the group and enabled and disabled command security and field security options. See Detail report stylesheets, page 552
Test Cases
Use any of the test case detail report stylesheets TestConfigDetailReport.xslt
Test Configs
All test configuration information including CPU and peripherals data. See Detail report stylesheets, page 552.
Test Runs
Use any of the test run detail report stylesheets UserDetailReport.xslt
Users
All user information including computer configurations, last login date/time, the number and percentage of reported, currently assigned, and closed issues, and the date of the last reported issue. Details of tasks included in a user's workbook including workflow events for assigned items. Details of tasks included in a user's workbook excluding workflow events for assigned items.
Workbook
WorkbookDetailReport.xslt
WorkbookSummaryReport.xslt
Note: You can use any of the list report stylesheets when printing a list report from list windows. See List report stylesheets, page 557.
563
Appendix E: Security Commands

Command security limits the commands that users can access. See Managing Security, page 323 for information about creating security groups and setting up security. Commands are grouped in categories. This appendix provides the following information about each command security option:
n n
Command: The command name. Provides access to: The TestTrack Client menu command or other feature that users can access if the command is enabled. For example, Create > Issue indicates that users can choose the Issue command from the Create menu. Keep in mind that the navigation for accessing commands in TestTrack Web is different than the TestTrack Client, but command security enabled in the TestTrack Client applies to the same commands in TestTrack Web. Additional information: Other commands that must be enabled to use the command or other information about the command.
General
The following commands provide access to TestTrack clients and commonly used features. Command
Edit Own Notifications Allow Access Via Email Notification Hyperlink
Provides access to:

Notifications category in the User Options dialog box (Tools > User Options) Click a link in an email notification to display an issue in TestTrack Web
Lets users edit their own email notifications only. Requires the Allow Login Via Web Client command. The Enable controlled email notification hyperlinks option must be selected in the Hyperlinks category of the Project Options dialog box. Select the Require recipient to login option in the Hyperlinks category to prompt the user to log in to TestTrack Web before the issue is displayed. Lets users edit own Dictionary, Spell Check, and Notifications user options only.
Modify Own General User Settings Allow Login Via TestTrack Client Allow Login Via TestTrack Web
General category in the User Options dialog box (Tools > User Options)
Log in to the project using the TestTrack Client
Requires a TestTrack Pro, TestTrack RM, or TestTrack TCM license.
Log in to the project using TestTrack Web
Requires a TestTrack Pro license.
565
Ad min ist r at ion
Command
Allow Login Via Add-In DLL Allow Login Via SOAP Change Own List Columns Allow Spell Checking
Provides access to:

Log in to the project using the Visual Studio add-in or QA Wizard Pro add-in
Requires a TestTrack Pro license.
Log in to the project using a SOAP-based interface Display Settings tab in the Edit User window Lets users edit list columns in their own user profile
Edit > Spell Check Spell Check category in the User Options dialog box (Tools > User Options)
Allow User Dictionary Editing
Dictionary category in the User Options dialog box (Tools > User Options) Add button in the Spell Check dialog box
See Overview Tab
Overview tab in the Add Issue, Edit Issue, View Issue, Add Requirement, Edit Requirement, View Requirement, Add Requirement Document, Edit Requirement Document, View Requirement Document, Add Test Case, Edit Test Case, View Test Case, Edit Test Run, and View Test Run windows Overview Tab options in the Display category of the User Options dialog box (Tools > User Options) Edit > Edit Inline when an item is selected in the Issues, Folders, Requirements, Requirement Documents, Test Cases, and Test Runs list windows Toggle Inline Editing button in list windows
Requires the See Workflow Tab command to view workflow event information. Requires the See Email Tab command to view email. Fieldlevel security is enforced on the Overview tab.
Can Hide Overview Tab Allow Inline Editing in List Windows
Administration
Only enable the following commands for administrator security groups. Command
Edit Project Options
Provides access to:

Tools > Administration > Project Options
Controls options for the project the user is currently logged in to.
566
Ad min ist r at ion
Command
Setup Project Fields
Provides access to:

Tools > Administration > Custom Fields Tools > Configure List Values
Controls project configuration options including types, priorities, severities, products, components, disposition, reproduced names, test run sets, and custom fields. Version names are controlled by the Setup Version Field command.
Can Lock Project
Tools > Administration > Lock Project Tools > Administration > Unlock Project
Setup Version Field Configure Field Relationships
Tools > Configure List Values > Version Values Tools > Administration > Field Relationships
Configure Required Fields & Default Values Configure Requirement Types Rename Field Labels Configure Notification Rules
Tools > Administration > Required Fields & Default Values
Tools > Administration > Requirement Types
Tools > Administration > Rename Field Labels Notifications tab in the Configure Automation Rules dialog box (Tools > Administration > Configure Automation Rules) Triggers tab in the Configure Automation Rules dialog box (Tools > Administration > Automation Rules) Escalations tab in the Configure Automation Rules dialog box (Tools > Administration > Automation Rules) Run executable option in the Add Rule Action dialog box for triggers and escalation rules
Configure Trigger Rules
Configure Escalation Rules
Configure Run Executable Actions
567
Ad min ist r at ion
Command
Configure Email Templates Configure SCC DB Options
Provides access to:

Tools > Administration > Email Templates
Project Options and Project Paths categories in the Configure SCC Integration dialog box (Tools > SCC Integration) Tools > Administration > Link Definitions
Changing options in the Project Options and Project Paths tabs affects all project users.
Configure Link Definitions Configure Folder Types
Tools > Administration > Folder Types Configure Folder Types button in the Add Folder and Edit Folder dialog boxes
Configure Item Mapping Rules Manage Email Notification Hyperlinks Manage Orphaned Emails Show Logged In Users Log Out Other Users
Tools >Administration >Item Mapping Rules
Tools > Administration > Email Notification Hyperlinks
Tools > Administration > Orphaned Email
View > Show Logged In Users
Log Out Users button in the Show Logged In Users dialog box (View > Show Logged In Users) File > Import > Text File Import
Requires the Show Logged In Users command.
Import From Text File Export To Text File Import From XML File Export To XML File
Enable for administrative security groups only.
File > Export > Text File Export
Enable for administrative security groups only. Fieldlevel security is not enforced when you export data. Enable for administrative security groups only.
File > Import > XML Import
File > Export > XML Export
Enable for administrative security groups only. Fieldlevel security is not enforced when you export data.
568
Ad min ist r at ion
Command
Import From Microsoft Word File Export To Microsoft Word File
Provides access to:

File > Import > Microsoft Word Import
Enable for administrative security groups only.
File > Export > Microsoft Word Export when the Specification Document window for a requirement document is open File > Build Release Notes
Create Release Notes Output View Audit Log Configure Issue Workflow Rules Configure Requirement Workflow Rules Configure Requirement Document Workflow Rules Configure Test Case Workflow Rules Configure Test Run Workflow Rules Delete Issue Historical Actions Delete Requirement Historical Actions
Tools > Administration > View Audit Trail Tools > Administration > Workflow Select Issues as the record type to configure issue workflow rules.
Tools > Administration > Workflow
Select Requirements as the record type to configure requirement workflow rules.
Tools > Administration > Workflow
Select Requirement Documents as the record type to configure requirement document workflow rules.
Tools > Administration >Workflow
Select Test Cases as the record type to configure test case workflow rules.
Tools > Administration >Workflow
Select Test Runs as the record type to configure test run workflow rules.
Edit > Delete Event when the Workflow tab is selected in the Add Issue or Edit Issue windows Edit > Delete Event when the Workflow tab is selected in the Add Requirement or Edit Requirement windows
Requires the Edit Issues command.
Requires the Edit Requirements command.
569
Ad min ist r at ion
Command
Delete Requirement Document Historical Actions Delete Test Case Historical Actions Delete Test Run Historical Actions Delete Historical Issue Info
Provides access to:

Edit > Delete Event when the Workflow tab is selected in the Add Requirement Document or Edit Requirement Document windows
Requires the Edit Requirement Documents command.
Edit > Delete Event when the Workflow tab is selected in the Add Test Case or Edit Test Case windows Edit > Delete Event when the Workflow tab is selected in the Add Test Run or Edit Test Run windows Issues in the Delete historical information for list in the Delete Historical Info dialog box (Tools > Administration > Delete Historical Info) Requirements in the Delete historical information for list in the Delete Historical Info dialog box (Tools > Administration > Delete Historical Info) Requirement Documents in the Delete historical information for list in the Delete Historical Info dialog box (Tools > Administration > Delete Historical Info) Test Cases in the Delete historical information for list in the Delete Historical Info dialog box (Tools > Administration > Delete Historical Info) Test Runs in the Delete historical information for list in the Delete Historical Info dialog box (Tools > Administration > Delete Historical Info) Folders in the Delete historical information for list in the Delete Historical Info dialog box (Tools > Administration > Delete Historical Info)
Requires the Edit Test Cases command.
Requires the Edit Test Runs command.
Delete Historical Requirement Info
Delete Historical Requirement Document Info Delete Historical Test Case Info
Delete Historical Test Run Info
Delete Historical Folder Information
Requires the Edit Public Folders command.
570
Issu e s
Issues
The Add Issues and Edit Issues commands must be enabled to use many of the features controlled by the following commands. The See Tab commands are only useful if the Add Issues, Edit Issues, or View Issues commands are enabled. Command
Assign Issue Numbers Renumber Issues Add Issues
Provides access to:

Activities > Assign Issue Numbers Activities > Renumber Issues Create > Issue File > Import > Load SoloBug Files File > Import > Perform Server Import
Requires the Delete Issues and View Issues commands.
View Issues
Edit > View Issue
If the Edit Issues command is enabled, users can still view issues by choosing Edit > Edit Issue. Disable the Edit Issues command if you do not want users to view issues at all.
Edit Issues
Edit > Edit Issue Edit button in the View Issue window
Delete Issues Duplicate Issues Edit Closed Issues
Edit > Delete Issue Edit > Duplicate Issue Edit > Edit Issue when a closed issue is selected Edit button in the View Issue window if the issue is closed Requires the Edit Issues command.
571
Issu e s
Command
Edit Issues Assigned to Anyone
Provides access to:

Edit > Edit Issue when an issue assigned to another user is selected Edit button in the View Issue window if the issue is assigned to another user
Merge Issues Edit Own Historical Actions
Edit > Merge Issues Edit > Edit Event when the Workflow tab is selected in the Add Issue or Edit Issue window Edit > Edit Event when the Workflow tab is selected in the Add Issue or Edit Issue window Email tab in the Add Issue, Edit Issue, and View Issue windows Email on the Overview tab in the Add Issue, Edit Issue, and View Issue windows
Requires the Delete Issues and View Issues commands. Lets users edit their own workflow events only. Requires the Edit Issues command.
Edit Others Historical Actions
Lets users edit anyones workflow events. Requires the Edit Issues command.
See Email Tab
See Workflow Tab
Workflow tab in the Add Issue, Edit Issue, and View Issue windows Workflow event information on the Overview tab in the Add Issue, Edit Issue, and View Issue windows
572
Issu e s
Command
See SCC Tab
Provides access to:

Source Code tab in the Add Issue, Edit Issue, and View Issue windows
Lets users view SCC actions that have already been performed but not perform SCC actions. Enable the Perform SCC Actions command to enable the SCC buttons (e.g., Attach File, Get) on the Source Code tab. If a user does not have access to the See SCC Tab or Configure SCC Project Options commands, the Configure SCC Integration menu option is also disabled because these options do not apply.
See Links Tab
Links tab in the Add Issue, Edit Issue, and View Issue windows Folders tab in the Add Issue, Edit Issue, and View Issue windows History tab in the Add Issue, Edit Issue, and View Issue windows Attach, Paste, and Screen Capture buttons on the Attachments mini tab in the Add Issue and Edit Issue windows Remove button on the Attachments mini tab in the Add Issue and Edit Issue windows View and Extract buttons on the Attachments mini tab in the Add Issue, Edit Issue, and View Issue windows Add button on the Email tab in the Add Issue and Edit Issue windows Remove button on Email tab in the Add Issue and Edit Issue windows
See Folders Tab
See History Tab
Add Attachments
Remove Attachments
View/Extract Attachments
Add Notify User
Remove Notify User
573
Issu e s
Command
Add Reported by Record
Provides access to:

Activities > New Reported By when editing an issue Activities > Delete Reported By when editing an issue All buttons (e.g., Attach File, Get) on Source Code tab in the Add Issue and Edit Issue windows Activities > Bulk Field Changes Activities > Override Workflow Send Email button in the Add Issue, Edit Issue, and View Issue windows Reply To button on the Email tab in the Add Issue, Edit Issue, and View Issue windows Reply To button in the View Email dialog box
Requires the View Issues command.
Remove Reported by Record Perform SCC Actions
An issue must have at least one reported by record.
Requires the See SCC Tab command.
Bulk Change Issues Override Workflow Send Tracked Email
Enable for administrative security groups only. This command gives users the ability to permanently change all issues in the project. Requires the Delete Issues command.
Reply To Tracked Email
View Tracked Email
View button on the Email tab in the Add Issue, Edit Issue, and View Issue windows Delete button on the Email tab in the Add Issue, Edit Issue, and View Issue windows Mark Suspect button on the Links tab in the Add Issue, Edit Issue, and View Issue windows
Delete Tracked Email
Mark Linked Items as Suspect
574
Issu e e ve n t s
Command
Clear Suspect
Provides access to:

Clear Suspect button on the Links tab in the Add Issue, Edit Issue, and View Issue window Clear Suspect button in the Investigate Suspect Dependencies window when investigating issue dependencies
Investigate Suspect Dependencies
Activities > Investigate Suspect Dependencies Investigate button on the Links tab in the Add Issue, Edit Issue, and View Issue windows
See Workflow Diagram Tab
Diagram tab on the Workflow tab in the Add Issue, Edit Issue, and View Issue windows Entire workflow option in the Show list on the Diagram tab on the Workflow tab in the Add Issue, Edit Issue, and View Issue windows
See Entire Workflow from Workflow Diagram Tab
Issue events
The following commands control access to TestTrack Pros default issue tracking workflow events. Actual workflow events may vary depending on your workflow. For example, if you delete one of these default events, it is no longer available as a command security option. When you add a new event, a security command is also created, allowing you to control access to it. Note: These commands are only useful if the Add Issues or Edit Issues commands are enabled.
575
Re q u ir e me n t s
Command
Add Attachments
Provides access to:

Attach and Paste buttons on the Attachments tab in the Add Event or Edit Event dialog boxes Remove button on the Attachments tab of the Add Event in Edit Event dialog boxes View and Extract buttons on the Attachments tab in the Add Event or Edit Event dialog boxes Activities > Assign Activities > Estimate Activities > Enter Work Activities > Fix Activities > Verify Activities > Force Close
The Files can be attached option must be selected for each workflow event (Tools > Administration > Workflow > Events > Edit Event). The Files can be attached option must be selected for each workflow event (Tools > Administration > Workflow > Events > Edit Event). The Files can be attached option must be selected for each workflow event (Tools > Administration > Workflow > Events > Edit Event).
Remove Attachments
Assign Estimate Enter Work Fix Verify Force Close
Re-Open Release Notes Comment
Activities > Re-Open Activities > Release Notes
Activities > Comment
Requirements
The Add Requirements and Edit Requirements commands must be enabled to use many of the features controlled by the following commands. The See Tab commands are only useful if the Add Requirements, Edit Requirements, or View Requirements commands are enabled. Command
Assign Requirement Numbers Renumber Requirements
Provides access to:

Activities >Assign Requirement Numbers
Requires the Delete Requirements and View Requirements commands.
Activities >Renumber Requirements
576
Command
Add Requirements
Provides access to:

Create > Requirement Add button on the Specification Document toolbar when Document View is selected File >Import > Microsoft Word Import
View Requirements
Edit >View Requirement
If the Edit Requirements command is enabled, users can still view requirements. Disable the Edit Requirements command if you do not want users to view requirements at all.
Edit Requirements
Edit >Edit Requirement Edit > Edit Requirement in Detail Window when the Specification Document window is open Edit button in View Requirement window Double-clicking requirements for editing in the Specification Document window
Change Requirement Type Delete Requirements Duplicate Requirements Edit Closed Requirements
Edit >Change Requirement Type
Edit >Delete Requirement Edit >Duplicate Requirement Edit >Edit Requirement when a closed requirement is selected Edit button in the View Requirement window if the requirement is closed Requires the Edit Requirements command.
577
Command
Edit Locked Requirements
Provides access to:

Edit >Edit Requirement when a locked requirement is selected Edit button in the View Requirement window if the requirement is locked
Edit Requirements Assigned to Anyone
Edit > Edit Requirement when a requirement assigned to another user is selected Edit button in the View Requirement window if the requirement is assigned to another user
Edit Own Historical Actions
Edit > Edit Event when the Workflow tab is selected in the Add Requirement or Edit Requirement window Edit > Edit Event when the Workflow tab is selected in the Add Requirement or Edit Requirement window Detail tab in the Add Requirement, Edit Requirement, and View Requirement windows Detail event information on the Overview tab in the Add Requirement, Edit Requirement, and View Requirement windows
Lets users edit their own workflow events only. Requires the Edit Requirements command.
Edit Other's Historical Actions
Lets users edit anyones workflow events. Requires the Edit Requirements command.
See Detail Tab
578
Command
See Workflow Tab
Provides access to:

Workflow tab in the Add Requirement, Edit Requirement, and View Requirement window Workflow event information on the Overview tab in the Add Requirement, Edit Requirement, and View Requirement windows
See Versions Tab
Versions tab in the Add Requirement, Edit Requirement, and View Requirement windows Documents tab in the Add Requirement, Edit Requirement, and View Requirement windows Traceability tab in the Add Requirement, Edit Requirement, and View Requirement windows Files tab in the Add Requirement, Edit Requirement, and View Requirement windows Attachments tab on the Files tab in the Add Requirement, Edit Requirement, and View Requirement windows Source Code tab on the Files tab in the Add Requirement, Edit Requirement, and View Requirement windows Lets users view SCC actions that have already been performed but not perform SCC actions. Enable the Perform SCC Actions command to enable the SCC buttons (e.g., Attach File, Get) on the Source Code tab. If a user does not have access to the See SCC Tab or Configure SCC Project Options commands, the Configure SCC Integration menu option is also disabled because these options do not apply.
See Documents Tab
See Traceability Tab
See Files Tab
See Attachments Tab
See SCCTab
579
Command
See Email Tab
Provides access to:

Email tab in the Add Requirement, Edit Requirement, and View Requirement windows Email on the Overview tab in the Add Requirement, Edit Requirement, and View Requirement windows
See Folders Tab
Folders tab in the Add Requirement, Edit Requirement, and View Requirement windows History tab in the Add Requirement, Edit Requirement, and View Requirement windows Attach, Paste, and Screen Capture buttons on the Attachments tab in the Files tab in the Add Requirement and Edit Requirement windows Remove button on the Attachments tab in the Files tab in the Add Requirement and Edit Requirement windows View and Extract buttons on the Attachments tab on the Files tab in the Add Requirement, Edit Requirement, and View Requirement windows Activities > Bulk Requirement Changes Enable for administrative security groups only. This command gives users the ability to permanently change all requirements in the project.
See History Tab
Add Attachments
Remove Attachments
Bulk Change Requirements
580
Command
Override Workflow Perform SCC Actions
Provides access to:

Activities > Override Workflow All buttons (e.g., Attach File, Get) on Source Code tab in the Add Requirement and Edit Requirement windows Send Email button in the Add Requirement, Edit Requirement, and View Requirement windows Reply To button on the Email tab in the Add Requirement, Edit Requirement, and View Requirement windows Reply To button in the View Email dialog box
Requires the Delete Requirements command.
Send Tracked Email
Reply to Tracked Email
View Tracked Email
View button on the Email tab in the Add Requirement, Edit Requirement, and View Requirement windows Delete button on the Email tab in the Add Requirement, Edit Requirement, and View Requirement windows Requirement review events in Review Mode View in the Specification Document window Review events on the Overview tab in the Add Requirement, Edit Requirement, and View Requirement windows Lets users view review events entered by all users.
View All Review Events
581
Command
View Review Events Added By This Security Group
Provides access to:

Requirement review events in Review Mode View in the Specification Document window Review events on the Overview tab in the Add Requirement, Edit Requirement, and View Requirement windows
Lets users view only review events entered by other users in the security group.
Activities >Mark Suspects Mark Suspect button in the Links tab on the Traceability tab in the Add Requirement, Edit Requirement, and View Requirement windows
Clear Suspect
Clear Suspect button in the Links tab on the Traceability tab in the Add Requirement, Edit Requirement, and View Requirement windows Clear Suspect button in the Investigate Suspect Dependencies window when investigating requirement dependencies
582
Re q u ir e me n t e ve n t s
Command
Provides access to:

Activities >Investigate Suspect Dependencies Investigate button in the Links tab on the Traceability tab in the Add Requirement, Edit Requirement, and View Requirement window Investigate button in the Requirements Relationships tab on the Traceability tab in the Add Requirement, Edit Requirement, and View Requirement windows
Make Requirement Current
Make Current button on the Versions tab in the Add Requirement, Edit Requirement, and View Requirement windows Diagram tab on the Workflow tab in the Add Requirement, Edit Requirement, and View Requirement windows Entire workflow option in the Show list on the Diagram tab on the Workflow tab in the Add Requirement, Edit Requirement, and View Requirement windows
Requirement events
The following commands control access to TestTrack RMs default requirement workflow events. Actual workflow events may vary depending on your workflow. For example, if you delete one of these default events, it is no longer available as a command security option. When you add a new event, a security command is also created, allowing you to control access to it. Note: These commands are only useful if the Add Requirements or Edit Requirements commands are enabled.
583
Re q u ir e me n t Docu me n t s
Command
Add Attachments
Provides access to:

Attach, Paste, and Screen Capture buttons on the Attachments tab in the Add Event or Edit Event dialog boxes
The Files can be attached option must be selected for each workflow event (Tools > Administration > Workflow > Events > Edit Event).
Remove Attachments
Remove button on the Attachments tab in the Add Event or Edit Event dialog boxes
View and Extract buttons on the Attachments tab in the Add Event or Edit Event dialog boxes
Assign Estimate Enter Work Ready for Review No Changes Needed Review Note Ready for Approval Approve Reject Needs Change Mark Suspects Implemented Obsolete Re-Open Comment
Activities > Assign Activities > Estimate Activities > Enter Work Activities > Ready for Review
Activities > No Changes Needed
Activities > Review Note Activities > Ready for Approval
Activities > Approve Activities > Reject Activities > Needs Change
Activities > Mark Suspects
Activities > Implemented Activities > Obsolete Activities > Re-Open Activities > Comment
Requirement Documents
The Add Requirement Documents and Edit Requirement Documents commands must be enabled to use many of the features controlled by the following commands.
584
The See Tab commands are only useful if the Add Requirement Documents, Edit Requirement Documents, or View Requirement Documents commands are enabled. Command
Assign Requirement Document Numbers Renumber Requirement Documents Add Requirement Documents
Provides access to:

Activities >Assign Requirement Document Numbers
Requires the Delete Requirement Documents and View Requirement Documents commands.
Activities >Renumber Requirement Documents
Create >Requirement Document File >Import > Microsoft Word Import
View Requirement Documents
Edit >View Requirement Document Open Specification Document button in the Edit Requirement Document and View Requirement Document windows
If the Edit Requirement Documents command is enabled, users can still view requirement documents by choosing Edit > Edit Requirement Document. Disable the Edit Requirement Documents command if you do not want users to view requirement documents at all.
Edit Requirement Documents
Edit >Edit Requirement Document Edit button in View Requirement Document window
Delete Requirement Documents Duplicate Requirement Documents Create Requirement Document Snapshot
Edit >Delete Requirement Document
Edit >Duplicate Requirement Document
Create Snapshot button on the Snapshots tab in the Edit Requirement Document and View Requirement Document windows
585
Command
View Requirement Document Snapshot
Provides access to:

View, View Snapshot Details, View Differences, and View All Differences buttons on the Snapshots tab in the Edit Requirement Document and View Requirement Document windows Snapshots menu in the Specification Document window
Edit Closed Requirement Documents
Edit >Edit Requirement Document when a closed requirement document is selected Edit button in the View Requirement Document window if the requirement document is closed
Edit Locked Requirement Documents
Edit >Edit Requirement Document when a locked requirement document is selected Edit button in the View Requirement Document window if the requirement document is locked
Edit Requirement Documents Assigned to Anyone
Edit > Edit Requirement Document when a requirement document assigned to another user is selected Edit button in the View Requirement Document window if the requirement document is assigned to another user
Edit Own Historical Actions
Edit > Edit Event when the Workflow tab is selected in the Add Requirement Document or Edit Requirement Document window
Lets users edit their own workflow events only. Requires the Edit Requirement Documents command.
586
Command
Edit Other's Historical Actions
Provides access to:

Edit > Edit Event when the Workflow tab is selected in the Add Requirement Document or Edit Requirement Document window Detail tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows Detail event information on the Overview tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows
Lets users edit anyones workflow events. Requires the Edit Requirement Documents command.
See Detail Tab
See Workflow Tab
Workflow tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows Workflow event information on the Overview tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows
See Snapshots Tab
Snapshots tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows Links tab in the Add Requirement, Edit Requirement, and View Requirement windows
See Links Tab
587
Command
See Files Tab
Provides access to:

Files tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows Attachments tab on the Files Tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows Source Code tab on the Files tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows Email tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows Email on the Overview tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows
See Attachments Tab
See SCC Tab
See Email Tab
See Folders Tab
Folders tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows History tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows
See History Tab
588
Command
Add Attachments
Provides access to:

Attach, Paste, and Screen Capture buttons on the Attachments tab in the Files tab in the Add Requirement Document and Edit Requirement Document windows Remove button on the Attachments tab in the Files tab in the Add Requirement Document and Edit Requirement Document windows View and Extract buttons on the Attachments mini tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows Activities > Bulk Requirement Document Changes Activities > Override Workflow All buttons (e.g., Attach File, Get) on Source Code tab in the Add Requirement Document and Edit Requirement Document windows Send Email button in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows
Remove Attachments
Bulk Change Requirement Documents Override Workflow Perform SCC Actions
Enable for administrative security groups only. This command gives users the ability to permanently change all requirement documents in the project. Requires the Delete Requirement Documents command.
Send Tracked Email
589
Command
Reply to Tracked Email
Provides access to:

Reply To button on the Email tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows Reply To button in the View Email dialog box
View Tracked Email
View button on the Email tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows Delete button on the Email tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows Requirement document review events in Review Mode View in the Specification Document window Review events on the Overview tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows Lets users view all review events.
View All Review Events
View Review Events Added By This Security Group
Requirement document review events in Review Mode View in the Specification Document window Review events on the Overview tab in the Add Requirement, Edit Requirement, and View Requirement windows
Lets users view only review events entered by other users in the security group.
590
Command
Move Requirements In Requirement Documents Remove Requirements From Requirement Documents
Provides access to:

Arrows on the Specification Document window toolbar when Document View is selected Edit >Remove Requirement Remove button on the Specification Document window toolbar when Document View is selected Add Requirement button in the Specification Document window toolbar when Document View is selected Activities >Mark Suspects Mark Suspect button on the Links tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows Clear Suspect button on the Links tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows Clear Suspect button in the Investigate Suspect Dependencies window when investigating requirement document dependencies
Add Requirements To Requirement Documents Mark Linked Items as Suspect
Clear Suspect
591
Re q u ir e me n t d ocu me n t e ve n t s
Command
Provides access to:

Activities >Investigate Suspect Dependencies Investigate button on the Links tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows
Diagram tab on the Workflow tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows Entire workflow option in the Show list on the Diagram tab on the Workflow tab in the Add Requirement Document, Edit Requirement Document, and View Requirement Document windows
Requirement document events

The following commands control access to TestTrack RMs requirement document default workflow events. Actual workflow events may vary depending on your workflow. For example, if you delete one of these default events, it is no longer available as a command security option. When you add a new event, a security command is also created, allowing you to control access to it. Note: These commands are only useful if the Add Requirement Document or Edit Requirement Document commands are enabled. Command
Add Attachments
Provides access to:

Attach, Paste, and Screen Capture buttons on the Attachments tab in the Add Event or Edit Event dialog boxes
Remove Attachments
Remove button on the Attachments tab in the Add Event or Edit Event dialog boxes
592
Te st Case s
Command
View/Extract Attachment
Provides access to:

View and Extract buttons on the Attachments tab in the Add Event or Edit Event dialog boxes
Assign Estimate Enter Work Ready for Review No Changes Needed Review Note Ready for Approval Approve Reject Needs Change Implemented Obsolete Re-Open Comment
Activities > Assign Activities > Estimate Activities > Enter Work Activities > Ready for Review
Activities > No Changes Needed
Activities > Review Note Activities > Ready for Approval
Activities > Approve Activities > Reject Activities > Needs Change
Activities > Implemented Activities > Obsolete Activities > Re-Open Activities > Comment
Test Cases
The Add Test Cases and Edit Test Cases commands must be enabled to use many of the features controlled by the following commands. The See Tab commands are only useful if the Add Test Cases, Edit Test Cases, or View Test Cases commands are enabled. Command
Assign Test Case Numbers Renumber Test Cases
Provides access to:

Activities > Assign Test Case Numbers
Requires the Delete Test Cases and View Test Cases commands.
Activities > Renumber Test Cases
593
Te st Case s
Command
Add Test Cases
Provides access to:

Create > Test Case Generate Test Cases button on the Edit Requirement and View Requirement windows
View Test Cases
Edit > View Test Case
If the Edit Test Cases command is enabled, users can still view test cases by choosing Edit > Edit Test Case. Disable the Edit Test Cases command if you do not want users to view test cases at all.
Edit Test Cases
Edit > Edit Test Case Edit button in the View Test Case window
Delete Test Cases Duplicate Test Cases Edit Closed Test Cases
Edit > Delete Test Case
Edit > Duplicate Test Case Edit > Edit Test Case when a closed test case is selected Edit button in the View Test Case window if the test case is closed Requires the Edit Test Cases command.
Edit Test Cases Assigned to Anyone
Edit > Edit Test Case when a test case assigned to another user is selected Edit button in the View Test Case window if the test case is assigned to another user
Edit Own Test Case Historical Actions
Edit > Edit Event when the Workflow tab is selected in the Add Test Case or Edit Test Case windows Edit > Edit Event when the Workflow tab is selected in the Add Test Case or Edit Test Case windows
Lets users edit their own workflow events only. Requires the Edit Test Cases command.
Edit Others Test Case Historical Actions
Lets users edit anyones workflow events. Requires the Edit Test Cases command.
594
Te st Case s
Command
See Detail Tab
Provides access to:

Detail tab in the Add Test Case, Edit Test Case, and View Test Case windows Steps tab in the Add Test Case, Edit Test Case, and View Test Case windows Variants tab in the Add Test Case, Edit Test Case, and View Test Case windows Files tab in the Add Test Case, Edit Test Case, and View Test Case windows Scripts tab on the Files tab in the Add Test Case, Edit Test Case, and View Test Case windows Attachments tab on the Files tab in the Add Test Case, Edit Test Case, and View Test Case windows New file attachment and Existing file attachment options when clicking the Insert Attachment button on the Steps tab in the Add Test Case and Edit Test Case windows
See Steps Tab
See Variants Tab
See Files Tab
See Scripts Tab
See Attachments Tab
The New file attachment option is only enabled if the Add Attachments command is also enabled.
See SCC Tab
Source Code tab on the Files tab in the Add Test Case, Edit Test Case, and View Test Case windows
Lets users view SCC actions that have already been performed but not perform SCC actions. Enable the Perform SCC Actions command to enable the SCC buttons (e.g., Attach File, Get) on the Source Code tab. If a user does not have access to the See SCC Tab or Configure SCC Project Options commands, the Configure SCC Integration menu option is also disabled because these options do not apply. Requires the View Test Runs command.
See Test Runs Tab
Test Runs tab in the Add Test Case, Edit Test Case, and View Test Case windows
595
Te st Case s
Command
See Workflow Tab
Provides access to:

Workflow tab in the Add Test Case, Edit Test Case, and View Test Case windows Workflow event information on the Overview tab in the Add Test Case, Edit Test Case, and View Test Case windows
See Email Tab
Email tab in the Edit Test Case and View Test Case window Email on the Overview tab in the Add Test Case, Edit Test Case, and View Test Case windows
See Links Tab
Links tab in the Add Test Case, Edit Test Case, and View Test Case windows Folders tab in the Add Test Case, Edit Test Case, and View Test Case windows History tab in the Add Test Case, Edit Test Case, and View Test Case windows Add Variant button on the Variants tab in the Add Test Case and Edit Test Case windows Edit Variant button on the Variants tab in the Add Test Case and Edit Test Case windows Remove Variant button on the Variants tab in the Add Test Case and Edit Test Case windows
See Folders Tab
See History Tab
Add Test Variant
Edit Test Variants
Remove Test Variants
596
Te st Case s
Command
Add Attachments
Provides access to:

Attach, Paste, and Screen Capture buttons on the Attachments tab in the Add Test Case and Edit Test Case windows Select Scripts and Paste buttons on the Scripts tab on the Files tab in the Add Test Case and Edit Test Case windows New file attachment option when clicking the Insert Attachment button on the Steps tab in the Add Test Case and Edit Test Case windows Screen Capture button on the Steps tab in the Add Test Case and Edit Test Case windows Paste from Clipboard option on the shortcut menu when rightclicking the Attachments column on the Steps tab in the Add Test Case and Edit Test Case windows
Attaching scripts requires the See Scripts Tab command.
Remove Attachments
Remove button on the Attachments tab on the Files tab in the Add Test Case and Edit Test Case windows Delete Attachment option on the shortcut menu when rightclicking an attachment on the Steps tab in the Add Test Case and Edit Test Case windows
597
Te st Case s
Command
Provides access to:

View and Extract buttons in the Attachments tab on the Files tab in the Add Test Case, Edit Test Case, and View Test Case windows View option on the shortcut menu when right-clicking an attachment on the Steps tab in the Add Test Case and Edit Test Case windows
Requires the View Test Cases command.
Run Automated Script Bulk Change Test Cases
Run Script button on the Files tab in the Edit Test Run window Activities > Bulk Test Case Changes Enable for administrative security groups only. This command gives users the ability to permanently change all test cases in the project.
Override Workflow Perform SCC Actions
Activities > Override Workflow All buttons (e.g., Attach File, Get) on Source Code tab in the Add Test Case and Edit Test Case windows New SCC attachment option when clicking the Insert Attachment button on the Steps tab in the Add Test Case and Edit Test Case windows Requires the See SCC Tab command.
Send Tracked Email
Send Email button in the Edit Test Case and View Test Case windows Reply To button on the Email tab in the Edit Test Case and View Test Case windows Reply To button in the View Email dialog box
598
Te st Case s
Command
View Tracked Email
Provides access to:

View button on the Email tab in the Edit Test Case and View Test Case windows Delete button on the Email tab in the Edit Test Case and View Test Case windows Mark Suspect button on the Links tab in the Add Test Case, Edit Test Case, and View Test Case windows Clear Suspect button on the Links tab in the Add Test Case, Edit Test Case, and View Test Case windows Clear Suspect button in the Investigate Suspect Dependencies window when investigating test case dependencies
Clear Suspect
Activities >Investigate Suspect Dependencies Investigate button on the Links tab in the Add Test Case, Edit Test Case, and View Test Case windows
Diagram tab on the Workflow tab in the Add Test Case, Edit Test Case, and View Test Case windows Entire workflow option in the Show list on the Diagram tab on the Workflow tab in the Add Test Case, Edit Test Case, and View Test Case windows
599
Te st case e ve n t s
Test case events

The following commands control access to TestTrack TCMs default test case workflow events. Actual workflow events may vary depending on your workflow. For example, if you delete one of the default events, it is no longer available as a command security option. When you add a new event, a security command is also created, allowing you to control access to it. Note: These commands are only useful if the Add Test Case or Edit Test Case commands are enabled. Command
Add Attachments
Provides access to:

Attach, Paste, and Screen Capture buttons on the Attachments tab in the Add Event or Edit Event dialog boxes Remove button on the Attachments tab in the Add Event or Edit Event dialog boxes
Remove Attachments
View and Extract buttons on the Attachments tab in the Add Event or Edit Event dialog boxes Activities > Assign Activities > Estimate Activities > Enter Work Activities > Ready Activities > Ready For Review
Assign Estimate Enter Work Ready Ready for Review Needs Change Reviewed Hold Resume Obsolete Re-Open Comment
Activities > Needs Change
Activities > Reviewed Activities > Hold Activities > Resume Activities > Obsolete Activities > Re-Open Activities > Comment
Test Runs
The Edit Test Runs command must be enabled to use many of the features controlled by the following commands. The See Tab commands are only useful if the Edit Test Runs or View Test Runs commands are enabled.
600
Te st Ru n s
Command
Generate Test Runs
Provides access to:

Activities > Generate Test Runs when a test case is selected Activities > Regenerate Test Runs
View Test Runs
Edit > View Test Run
If the Edit Test Runs command is enabled, users can still view Test Runs by choosing Edit > Edit Test Run. Disable the Edit Test Runs command if you do not want users to view test runs at all.
Edit Test Runs
Edit > Edit Test Run Edit button in the View Test Run window Add workflow events on script result field on the Run Scripts dialog box
Delete Test Runs Duplicate Test Runs Edit Closed Test Runs
Edit > Delete Test Run
Edit > Duplicate Test Run
Edit > Edit Test Run when a Closed test run is selected Edit button in the View Test Run window if the test run is closed
Edit Test Runs Assigned to Anyone
Edit > Edit Test Run when a test run assigned to another user is selected Edit > Edit Event when the Workflow tab is selected in the Edit Test Run window Edit > Edit Event when the Workflow tab is selected in the Edit Test Run window Steps tab in the Edit Test Run and View Test Run windows
Edit Own Test Run Historical Actions
Lets users edit their own workflow events only. Requires the Edit Test Runs command.
Edit Others Test Run Historical Actions See Steps Tab
Lets users edit anyones workflow events. Requires the Edit Test Runs command.
601
Te st Ru n s
Command
See Variants Tab
Provides access to:

Variants tab in the Edit Test Run and View Test Run windows Files Tab in the Edit Test Run and View Test Run windows Scripts tab on the Files tab in the Edit Test Run and View Test Run windows Attachments tab on the Files tab in the Edit Test Run and View Test Run windows New file attachment and Existing file attachment options when clicking the Insert Attachment button on the Steps tab in the Edit Test Run window (detail grid view only)
See Files Tab
See Scripts Tab
See Attachments Tab
The New file attachment option is only enabled if the Add Run Result Attachments command is also enabled.
See SCC Tab
Source Code tab on the Files tab in the Edit Test Run and View Test Run windows
See Detail Tab
Details tab in the Edit Test Run and View Test Run windows Workflow tab in the Edit Test Run and View Test Run windows Workflow event information on the Overview tab in the Edit Test Run and View Test Run windows
See Workflow Tab
602
Te st Ru n s
Command
See Email Tab
Provides access to:

Email tab in the Edit Test Run and View Test Run windows Email on the Overview tab in the Edit Test Run and View Test Run windows
See Links Tab
Links tab in the Edit Test Run and View Test Run windows Folders tab in the Edit Test Run and View Test Run windows History tab in the Edit Test Run and View Test Run windows Add Variant Info button on the Variants tab in the Edit Test Run window Edit Variant Info button on the Variants tab in the Edit Test Run window Delete Variant Info button on the Variants tab in the Edit Test Run window View and Extract buttons on the Attachments tab on the Files tab in the Edit Test Run and View Test Run windows View option on the shortcut menu when right-clicking an expected results attachment on the Steps tab in the Edit Test Run window Requires the View Test Runs command.
See Folders Tab
See History Tab
Add Additional Test Variants
Edit Additional Test Variants
Delete Additional Test Variants View/Extract Test Case Attachments
603
Te st Ru n s
Command
Add Run Result Attachments
Provides access to:

Attach, Paste, and Screen Capture buttons on the Attachments tab on the Files tab in the Edit Test Run window New file attachment option when clicking the Insert Attachment button on the Steps tab in the Edit Test Run window (detail grid view only) Screen Capture button on the Steps tab in the Edit Test Run window (detail grid view only) Paste from Clipboard option on the shortcut menu when right-clicking the Attachments field on the Steps tab in the Edit Test Run window (detail grid view only)
Remove Run Result Attachments
Remove button on the Attachments tab on the Files tab in the Edit Test Run window Delete Attachment button when an actual result attachment is selected on the Steps tab in the Edit Test Run window (detail grid view only)
Attachments added to test cases cannot be removed.
View/Extract Run Result Attachments
View or Extract buttons on the Attachments tab on the Files tab in the Edit Test Run window View option on the shortcut menu when right-clicking an attachment in the actual results Attachments field on the Steps tab in the Edit Test Run window (detail grid view only)
604
Te st Ru n s
Command
Run Automated Script
Provides access to:

Activities > Run Scripts Run Script button on the Scripts tab in the Files tab in the Edit Test Run window Run Scripts button on the Test Runs tab in the Edit Test Case window
Bulk Change Test Runs
Activities > Bulk Test Run Changes
Enable for administrative security groups only. This command gives users the ability to permanently change all test runs in the project.
Override Workflow Insert Problem Statements
Activities > Override Workflow Problem Statement column and Insert Problem Statement button on the Steps tab in the Edit Test Run window (grid view) Add Problem Statement links on the Steps tab in the Edit Test Run window (detail grid view) To disable the Problem Statement text field in free form view, set the Problem statement field security to read only.
Perform SCC Actions
All buttons (e.g., Attach File, Get) on Source Code tab on the Files tab in the Edit Test Run window New SCC attachment option when clicking the Insert Attachment button on the Steps tab in the Edit Test Run window (detail grid view only)
Send Tracked Email
Send Email button in the Edit Test Run and View Test Run windows Reply To button on the Email tab in the Edit Test Run and View Test Run windows Reply To button in the View Email dialog box
605
Te st r u n e ve n t s
Command
View Tracked Email
Provides access to:

View button on the Email tab in the Edit Test Run and View Test Run windows Delete button on the Email tab in the Edit Test Run and View Test Run windows Mark Suspect button on the Links tab in the Add Test Run, Edit Test Run, and View Test Run windows Clear Suspect button on the Links tab in the Add Test Run, Edit Test Run, and View Test Run windows Clear Suspect button in the Investigate Suspect Dependencies window when investigating test run dependencies
Clear Suspect
Activities >Investigate Suspect Dependencies Investigate button on the Links tab in the Add Test Run, Edit Test Run, and View Test Run windows
Diagram tab on the Workflow tab in the Edit Test Run and View Test Run windows Entire workflow option in the Show list on the Diagram tab on the Workflow tab in the Edit Test Run and View Test Run windows
Test run events

The following commands control access to TestTrack TCMs default workflow events. Actual workflow events may vary depending on your workflow. For example, if you delete one of the default events, it is no longer available as a command security option. When you add a new event, a security command is also created, allowing you to control access to it.
606
Fol d e r s
Note: These commands are only useful if the Edit Test Run command is enabled. Command
Add Attachments
Provides access to:

Attach, Paste, and Screen Capture buttons on the Attachments tab in the Add Event or Edit Event dialog boxes Remove button on the Attachments tab in the Add Event or Edit Event dialog boxes
Remove Attachments
View and Extract buttons on the Attachments tab in the Add Event or Edit Event dialog boxes Activities > Assign Activities > Estimate Activities > Start Activities > Enter Work Activities > Enter Result
Assign Estimate Start Enter Work Enter Result
Pass Fail Unclear Hold Resume Comment Ignore Result Re-Open
Activities > Pass Activities > Fail Activities > Unclear Activities > Hold Activities > Resume Activities > Comment Activities > Ignore Result
Activities > Re-Open
Folders
The following commands control access to the options available from the Folders list window. Command Provides access to:
Add Public Folder Add button on the Folders list window when a public folder is selected
607
Fol d e r s
Command Provides access to:

View Public Folder View button on the Folders list window when a public folder is selected
If the Edit Public Folder command is enabled, users can still view public folders by clicking the Edit button on the Folders list window. Disable the Edit Public Folder command if you do not want users to view public folders at all.
Edit Public Folder
Edit button on the Folders list window when a public folder is selected Edit button in the View Folder window if the folder is public
Delete Public Folder Add Items to Public Folder
Delete button on the Folders list window when a public folder is selected
Issues, Requirements, Requirement Documents, and Test Cases when clicking the Add button on the Folders list window when a public folder is selected Add to Folder button on the Folders tab in the Edit Issue, Edit Requirement, Edit Requirement Document, Edit Test Case, and Edit Test Run windows when a public folder is selected
Remove Items from Public Folder
Remove button on the Folders list window when an item in a public folder is selected Remove from Folder button on the Folders tab in the Edit Issue, View Issue, Edit Requirement, View Requirement, Edit Requirement Document, View Requirement Document, Edit Test Case View Test Case, Edit Test Run, and View Test Run windows Drag public folders to private folders
Make Public Folders Private Work with Private Folders
Private folders in the Folders list window and other windows Rank Items button in the Folders list window when a private folder is selected
Share Public Folder with Security Groups
Share with security groups option in the Access drop-down list in the Add Folder and Edit Folder dialog boxes
Allows users to share top-level public folders with security groups.
608
Lin ks

See All Public Folders Public folders in the Folders list window and other windows
Enable for administrative security groups only. Provides access to all public folders, even folders shared with security groups that the user is not in.
Rank Public Folder Items
Rank Items button in the Folders list window when a public folder is selected
Links
The Add, Edit, or View commands for issues, requirements, requirement documents, test cases, and test runs must be enabled to use features controlled by the following commands. Command Provides access to:
Add Links Activities > Add Link Add Link button on the Links tab in the Edit Issue, Edit Requirement, Edit Requirement Document, Edit Test Case, and Edit Test Run windows Link duplicated with original check box on the Duplicate Issue Options, Duplicate Requirement Options, Duplicate Requirement Document Options, Duplicate Test Case Options, and Duplicate Test Runs Options dialog boxes Link regenerated test runs with the original test run check box on the Regenerate Test Runs dialog box Link new test cases options in the Generate Test Cases dialog box when generating test cases from requirements View Links View Link button on the Links tab in the Edit Issue, Edit Requirement, Edit Requirement Document, Edit Test Case, and Edit Test Run windows Activities > Traceability Matrix Edit Link button on the Links tab in the Edit Issue, Edit Requirement, Edit Requirement Document, Edit Test Case, and Edit Test Run windows Delete Link button on the Links tab in the Edit Issue, Edit Requirement, Edit Requirement Document, Edit Test Case, and Edit Test Run windows View Definition button in Add Link, Edit Link, and View Link dialog boxes
Edit Links
Delete Links View Link Definitions
Customers
The following commands control access to the options available from the Customers list window. Command
Add Customers
Provides access to:

Create > Customer
609
U se r s
Command
View Customers Edit Customers
Provides access to:

Edit > View Customer Edit > Edit Customer Edit button in the View Customer window
Delete Customers Duplicate Customers Make Customer a User Activate/Inactive Customer
Edit > Delete Customer Edit > Duplicate Customer Edit > Change to User Edit > Activate Customer Edit > Inactivate Customer
Users
The following commands control access to the options available from the Users list window. Command
Add Users View Users Edit Users
Provides access to:

Create > User Edit > View User Edit > Edit User Edit button in the View User window
Allows users to edit user information for every TestTrack user. The Edit Own General User Options and Edit Own Email Notifications commands allows users to set their own options only.
Delete Users Duplicate Users
Edit > Delete User Edit > Duplicate User
View User Login Info
Username, Password, and Confirm Password fields on the Info tab in the Add User, Edit User, Add Customer, and Edit Customer dialog boxes Security Group list on the Info tab in the Add User, Edit User, Add Customer, and Edit Customer dialog boxes Edit > Change to Customer
This command affects users and customers.
Edit Security Group Setting
Make User a Customer Activate/Inactive User
Edit > Activate User Edit > Inactivate User
610
U se r s
Command
View Company Information
Provides access to:

Company, Department, and Division fields on the Address tab in the Add User, Edit User, View User, Add Customer, Edit Customer, and View Customer dialog boxes Company, Department, and Division fields in the Advanced Search section of the Find Users dialog box Company, Department, and Division columns in the Find Users dialog box Company in the drop-down list in the Add Restriction and Edit Restriction dialog boxes when a user field is selected in the Restrict by list Ability to view or edit filters with user field restrictions based on Company when clicking the View or Edit buttons in the Add Filter, Edit Filter, and View Filter dialog boxes
611
S e cu r it y Gr ou p s
Command
View Security Group Information
Provides access to:

Security Group field in the Advanced Search area of the Find Users dialog box, and Add User, Edit User, View User, Add Customer, Edit Customer, and View Customer dialog boxes Security Groups column in the Find Users dialog box and Filters list window Groups columns in the User list window and Customer list window Security Groups in the drop-down list in the Add Restriction and Edit Restriction dialog boxes when a user field is selected in the Restrict by list Ability to view or edit filters with user field restrictions based on Security Groups when clicking the View or Edit buttons in the Add Filter, Edit Filter, and View Filter dialog boxes Shared with Security Groups option in the Share drop-down list and the corresponding security groups list in the Add Filter and Edit Filter dialog boxes Security groups list for the selected Shared with Security Groups option in the View Filter dialog box Security group information in XML exports Security group information in detail reports based on users
Creating filters requires the Add Filter command in the Filters category. Sharing private filters with security groups requires the Edit Private Filters and Mark Own Filters As Shared commands in the Filters category. Sharing shared filters with security groups requires the Edit Shared Filters and Mark Shared Filters As Shared commands in the Filters category. Viewing shared filters requires the View Shared Filters command in the Filters category.
Security Groups
The following commands control access to the options available from the Security Groups list window. Note: Edit Security Groups and See Security Tabs security must be enabled for at least one security group. You cannot remove yourself as a user from a security group with these commands enabled because it could result in no users with permissions to perform administrative tasks. Command
Add Security Groups
Provides access to:

Create > Security Group
612
Te st Con figu r at ion s
Command
View Security Groups Edit Security Groups
Provides access to:

Edit > View Security Group
Edit > Edit Security Group Edit button in the View Security Group window
This command must be enabled for at least one security group in the project.
Delete Security Groups Duplicate Security Groups See Security Tabs
Edit > Delete Security Group
Edit > Duplicate Security Group
Command Security and Field Security tabs on the Add Security Group and Edit Security Group windows
This command must be enabled for at least one security group in the project.
Test Configurations
The following commands control access to the menu available from the Test Configs list window. Command
Add Test Configs View Test Configs Edit Test Configs
Provides access to:

Create > Test Config Edit > View Test Config Edit > Edit Test Config Test Config Edit button in the View Test Config window
Delete Test Configs Duplicate Test Configs
Edit > Delete Test Config Edit > Duplicate Test Config
Filters
The following commands control access to the options available from the Filters list window. Command Provides access to:
Add Filters Create > Filter Create Filter button in dialog boxes
613
Fil t e r s

Mark Own Filters As Shared Options in the Share drop-down list in the Add Filter and Edit Filter dialog boxes when a private filter is selected
Allows users to share private filters with other users (everyone, users, customers, or security groups). Requires the Add Filters, Edit Private Filters, or Edit Shared Filters commands. Sharing with security groups requires the View Security Group Information command in the Users category.
Mark Shared Filters As Shared
Options in the Share drop-down list in the Add Filter and Edit Filter dialog boxes when a shared filter is selected
Allows users to share shared filters with other users (everyone, users, customers or security groups). Requires the Add Filters, Edit Private Filters, or Edit Shared Filters commands. Sharing with security groups requires the View Security Group Information command in the Users category.
Mark Filter as Published View Own Filters
Publish option in the Share drop-down list in the Add Filter and Edit Filter dialog boxes
Edit > View Filter when a private filter is selected Private filters in the Filter list in list windows and dialog boxes
View Shared Filters
Edit > View Filter when a shared filter is selected Shared filters in the Filter list in list windows and dialog boxes
Edit Own Filters
Edit > Edit Filter when a private filter is selected Edit button in the View Filter window if the filter is private Edit > Edit Filter when a shared filter is selected Edit button in the View Filter window if the filter is shared Edit > Edit Filter when a published filter is selected Edit button in the View Filter window if the filter is published Edit > Delete Filter when a private filter is selected
Edit Shared Filters
Edit Published Filters Delete Own Filters
614
Re p or t s

Delete Shared Filters Delete Published Filters Duplicate Own Filters Duplicate Shared Filters Duplicate Published Filters Edit > Delete Filter when a shared filter is selected
Edit > Delete Filter when a published filter is selected
Edit > Duplicate Filter when a private filter is selected Edit > Duplicate Filter when a shared filter is selected
Edit > Duplicate Filter when a published filter is selected
Reports
The following commands control access to the options available from the Reports list window. Command Provides access to:
Add Reports Mark Reports As Shared Create > Report
Adding external reports also requires the Add External Reports command. Allows users to share reports with other users (everyone, users, customers, or security groups). Requires the Add Reports, Edit Own Reports, or Edit Shared Reports commands.
Options in the Share dropdown list when a report is selected
View Own Reports View Shared Reports Edit Own Reports
Edit > View Report when a private report is selected Edit > View Report when a shared report is selected
Edit > Edit Report when a private report is selected Edit button in the View Report window if the report is private Edit button in the Live Charts pane in the Folders list window if the live chart is private
615
Wor kb ook

Edit Shared Reports Edit > Edit Report when a shared report is selected Edit button in the View Report window if the report is shared Edit button in the Live Charts pane in the Folders list window if the live chart is shared Delete Own Reports Delete Shared Reports Duplicate Own Reports Duplicate Shared Reports Run Own Reports Edit > Delete Report when a private report is selected
Edit > Delete Report when a shared report is selected
Edit > Duplicate Report when a private report is selected
Edit > Duplicate Report when a shared report is selected
Print and Preview buttons on Reports list window Private live charts in the Live Charts pane in the Folders list window
Lets users run reports and live charts they created only.
Run Shared Reports
Print and Preview buttons on Reports list window Shared live charts in the Live Charts pane in the Folders list window
Lets users run shared reports and live charts.
Add External Reports
Create > Report > <external report>
Requires the Add Report command.
Workbook
The following commands control access to the options available from the Workbook list window. Command
Add Tasks
Provides access to:

Create > Task Edit > Duplicate Task
616
Wor kb ook
Command
View Tasks Edit Tasks
Provides access to:

Edit > View Task Edit > Edit Task Edit button in the View Task window
Delete Tasks
Edit > Delete Task
617
Appendix F: Calculated Custom Field Functions

TestTrack includes the following functions that can be used in calculated field formulas to query item input data. See Adding calculated field formulas, page 398. These functions are extensions of the standard ECMAScript language. Common date, math,string, and global functions are also included. Refer to the ECMA-262 Standard Language Specification (http://www.ecma-international.org/publications/standards/Ecma-262.htm) for information about other supported functions.
Date functions
Date functions return numeric values based on dates.
now
Returns the current Coordinated Universal Time (UTC) date and time. Date.now()
parse
Returns the specified string as a date and time. Date.parse(string)
UTC
Returns the number of milliseconds in a universal date/time value since midnight of January 1, 1970. Requires year and month values. Can optionally include day, hours, minutes, seconds, and milliseconds values. Date. UTC(year, month, [day], [hours], [minutes], [seconds], [millisec])
DateTime functions
DateTime functions return a date/time value with the specified amount of time added.
addMinutes
Returns a date with the specified number of minutes added. DateTime.addMinutes(date, minutes)
addHours
Returns a date with the specified number of hours added. DateTime.addHours(date, hours)
619
It e m fu n ct ion s
addDays
Returns a date with the specified number of days added. DateTime.addDays(date, days)
addWeeks
Returns a date with the specified number of weeks added. DateTime.addWeeks(date, weeks)
addMonths
Returns a date with the specified number of months added. DateTime.addMonths(date, months)
addYears
Returns a date with the specified number of years added. DateTime.addYears(date, years)
Item functions
Item functions return TestTrack field values or values mapped to list items.
fieldValue
Returns a field value by the specified name. Returned value is a string, date, number, or Boolean. Item.fieldValue(field name)
mappedValue
Returns the mapped value for a selected list item. Note: You must configure the input list mappings for the field. See Adding calculated field formulas, page 398. Item.mappedValue(field name)
Item.Events functions
Item.Events functions return workflow event values from items.
at
Returns the event record using the specified index. Can optionally include an event name. Item.Events.at(index, [event name])
620
It e m.Re p or t e d B y fu n ct ion s
average
Returns the average value of event input values from the specified event field. Can only use in numeric output fields. Item.Events.average(event name, field name)
count
Returns the total number of events. Can optionally include an event name. Item.Events.count([event name])
first
Returns the first event record. Can optionally include an event name. Item.Events.first([event name])
last
Returns the last event record. Can optionally include an event name. Item.Events.last([event name])
max
Returns the largest value from the specified event field. Can only use in numeric output fields. Item.Events.max(event name, field name)
min
Returns the smallest value from the specified event field. Can only use in numeric output fields. Item.Events.min(event name, field name)
product
Returns the value from multiplying the event input values from the specified event field.Can only use in numeric output fields. Item.Events.product(event name, field name)
sum
Returns the sum from the specified event field. Can only use in numeric output fields. Item.Events.sum(event name, field name)
Item.ReportedBy functions
Item.ReportedBy functions return Reported by record information from a TestTrack Pro issue.
621
M at h fu n ct ion s
at
Returns the Reported by record using the specified index. Item.ReportedBy.at(index)
count
Returns the number of Reported by records. Item.ReportedBy.count()
first
Returns the first Reported by record. Item.ReportedBy.first()
last
Returns the last Reported by record. Item.ReportedBy.last()
Math functions
Math functions perform mathematical operations to return numeric values.
abs
Returns the absolute value of the argument. Math.abs(x)
acos
Returns the arccosine of the argument in radians. Math.acos(x)
asin
Returns the arcsine of the argument in radians. Math.asin(x)
atan
Returns the arctangent of the argument as a numeric value between -PI/2 and PI/2 radians. Math.atan(x)
622
M at h fu n ct ion s
atan2
Returns the arctangent of the quotient or arguments. Math.atan2(y, x)
ceil
Returns the argument rounded up to the nearest integer. Math.ceil(x)
cos
Returns the cosine of the argument. The argument is in radians. Math.cos(x)
exp
Returns the value of the mathematical constant e raised to the power of the argument. Math.exp(x)
floor
Returns the argument rounded down to the nearest integer. Math.floor(x)
log
Returns the natural logarithm (base E) of the argument. Math.log(x)
max
Returns the argument with the highest value. Math.max(x, [...])
min
Returns the argument with the lowest value. Math.min(x, [...])
pow
Returns the first argument raised to the power of the second argument. Math.pow(x, y)
623
S t r in g fu n ct ion s
random
Returns a random number between 0 and 1. Math.random()
round
Rounds the argument to the nearest integer. Math.round(x)
sin
Returns the sine of the argument. The argument is in radians. Math.sin(x)
sqrt
Returns the square root of the argument. Math.sqrt(x)
tan
Returns the tangent of an angle. Math.tan(x)
String functions
String functions return parts of text from strings.
fromCharCode
Converts Unicode values to characters. String.fromCharCode(code, [...])
Global functions
The following functions can be used with all ECMAScript and TestTrack objects.
decodeURI
Decodes a Uniform Resource Locator (URL) and returns a string value. Requires a Universal Resource Identifier (URI). decodeURI(uri)
624
Gl ob al fu n ct ion s
decodeURIComponent
Decodes a URL component and returns a string value. Requires a URI. decodeURIComponent(uri)
encodeURI
Encodes a URL and returns a string value. Requires a URI. encodeURI(uri)
encodeURIComponent
Encodes a URL and returns a string value. Requires a URI. encodeURIComponent(uri)
escape
Encodes a string. escape(string)
eval
Evaluates an expression or executes one or more JavaScript statements. eval(string)
isFinite
Returns True or False to indicate if a number is finite or legal. isFinite(value)
isNan
Returns True or False to indicate if a value is an illegal number. isNAN(value)
parseFloat
Parses a string and returns a floating point number. parseFloat(value)
parseInt
Parses a string and returns an integer. Can optionally include a base value. parseInt(value, [base])
625
Gl ob al fu n ct ion s
unescape
Decodes an encoded string. unescape(string)
626
Appendix G: Fields Affected by Administrative Changes

The following fields may change when administrative tasks are performed, such as updating project options or reconfiguring list values. If affected fields are used in calculated custom field formulas, values are only recalculated after individual items are modified and saved. Tip: You can also create an escalation rule to schedule field recalculations. See Adding escalation rules, page 449. Fields for all item types
n n n n n n n n n n n n n n
Actual Hours Closed By Created By Current Assignment By Currently Assigned To Estimated Hours Modified By Percent Done Remaining Hours State Attribute Status Story Points Type Variance
Issue fields
n n n n n n n n n
Component Computer Config Disposition Entered by Found by Found by Company Found by Department Found by Division Found by Group
627
Ap p e n d ix G: Fie l d s Affe ct e d b y Ad min ist r at ive Ch an ge s
n n n n
Priority Product Severity Version
Requirement fields
n n
Importance Tag
Test run fields

n n
Run Result Status Test Run Set
628
In d e x:Act ivat in g Assign in g
Index
A
Activating customers escalation rules folder types link definitions notification rules requirement types triggers user notification rules users workflow events workflow states Actual hours Adding additional issue reports automation rule actions built-in reports calculated field formulas calculated fields columns to list windows custom fields customers dictionary words email notification hyperlinks email templates escalation rules external reports field relationships filters folder types folders hyperlinks images issues item mapping rules 163 453 122 398 391 23 385 333 352 475 467 449 142 408 97 412 61 50 51 159 464 341 452 414 475 441 383 447 49 340 422 417 429
items to folders link definitions links list items notification rules release notes requirement documents requirement types requirements restrictions security groups stylesheets tables tabs to list windows tasks to workbook test cases test configs test variants triggers user notification rules users workflow events workflow states Additional issue reports adding deleting editing Address bar Advanced find adding restrictions deleting restrictions editing restrictions inserting restrictions viewing restrictions After save triggers Appending requirements to documents Assigning issue numbers requirement document numbers
66 472 77-78 380 439 178 181 382 183 99 324 551 51 32 33 255 177 386 444 47 330 418 416
163 175 173 13 38 99 118 117 118 31 443 194
174 228
629
In d e x:Assign me n t r u l e s Ch ar t in g
requirement numbers test case numbers Assignment rules Asterisk field labels marked with Attaching files files to test case steps files to test run steps screenshots source code files Audit trail records exporting report searching validating viewing Auto-assignment rule action Automated testing attaching test results checking status confirming tests work creating scripts from test cases recording test case steps running individual tests running multiple tests scheduling tests to run status viewing test results Automation rules adding actions configuring configuring actions deleting actions editing actions running executables Automation rules log deleting all entries deleting entries by date
200 321 424
exporting viewing
459 458
B
Before save triggers 443 99 196 85 88 87 86 181
410
Boolean operators Breaking requirement shares
54 263 288 55 499
Bulk changes excluded test variants included test variants test variants Business requirements
481 480 478 481 479 454
C
Calculated fields adding adding formulas configuring date/time output example 391 398 390 395
fields affected by administrative changes627 313 311 307 303 262 308 309 310 312 312 formula synatx code completion functions inserting functions in formulas list item output example mapping list item output values numeric output example recalculating testing formulas text output example time span output example 453 436 453 458 458 437 troubleshooting understanding formula syntax Certification and testimony message Change reports Changing bulk fields requirement types 460 459 Charting adding charts to reports 139 85 200 401 619 401 395 402 393 404 403 394 397 405 400 369 45
630
In d e x:Ch e ck in op t ion s De l e t in g
creating live charts Check in options SCC settings Clearing suspect items Column filters list windows Columns adding to list windows changing list window contents moving list window removing list window sorting list window totaling in list windows Command-level security issues requirement documents requirements test cases test runs Company adding for customers adding for users Compliance setting enhanced for test runs Connecting to different TestTrack Server TestTrack Server Copying requirements to documents Correcting test case steps Create snapshot action Creating field relationships RSS feeds text file export templates text file import templates user-defined views Custom fields adding configuring
143
creating drafts deleting
387 390 389 162 526 388 404 386 386
498 84
editing entering environment variables
24
pop-up menu recalculating field values
23 24 24 24 24 24 324-325, 565 571 584 576 593 600
test variants types Customers activating adding
341 333
adding company, division, department 335 adding to fields deleting duplicating editing finding inactivating making user 39 342 340 339 39 341 341 338 337 339
335 332
promoting retrieving global viewing
371
D
Defects SeeIssues
6 7 194 265 457
Deleting additional issue reports automation rule actions custom fields customers dictionary words 175 458 390 342 352 76 476 470 452 409 118 414
408 153 95 97 28
email email notification hyperlinks email templates escalation rules field relationships filters
385 384
folder types
631
In d e x:De p ar t me n t Du p l icat in g
folders historical log information issues link definitions links list items live charts notification rules orphaned email reports requirement documents requirement types requirements restrictions security groups server connections test cases test configs test runs triggers user-defined views user notification rules users workbook tasks workflow events workflow events from items workflow states Department adding for customers adding for users Detaching source code files Detail reports creating stylesheets Diagramming item workflow history links workflows
70 482 175 475 81 380 152 441 157 152 229 383 201 118 330 9 322 178 316 447 29 49 341 34 423 42 417
Dictionary adding words deleting words editing words Differences requirement documents requirements Differences report changing display options requirement documents requirements Distribution reports creating stylesheets Division adding for customers adding for users Document View adding existing requirements adding new requirements appending requirements removing requirements toolbar Draft custom fields creating promoting to active replacing active fields Duplicating 387 387 388 335 332 188, 191 193 193 194 196 189 349 234 238 119 125 556 233-234 238 352 352 352
335 332 512 119 123 552
customers filters issues live charts reports requirement documents requirements
340 118 173 152 152 226 199 330 320 178 315
43 79 427
security groups test cases test configs test runs
632
In d e x:Ed it in g Email t e mp l at e s
users workbook tasks
340 34
triggers user-defined views user notification rules users
447 29 48 339 33 42 422 424 416 423
E
Editing additional issue reports automation rule actions custom fields customers default field values dictionary words email templates escalation rules field relationships filters folder types folders issues items in folders items in list windows link definitions links list items live charts notification rules reports required fields requirement documents requirement review notes requirement types requirements 173 458 389 339 407 352 470 451 409 117 413 68 172 68 26 474 81 380 151 440 151 407 225 224 383 198
workbook tasks workflow event details workflow events workflow resulting states workflow states workflow transitions Electronic signatures certification and testimony message entering requiring for events Email adding recipients attaching orphaned to records deleting deleting orphaned issues managing orphaned replying requirement documents requirements sending from TestTrack test cases test runs viewing viewing orphaned Email notification hyperlinks adding deleting viewing Email templates adding adding hyperlinks to customizing deleting editing
369 477 420
74 156 76 157 171 155 76 229 229 73 317 317 75 155
requirements in Specification Document 195 restrictions SCC files screenshots security groups test cases test configs test runs 117 502 55 326 319 178 314
475 476 476
467 475 466 470 470
633
In d e x:En t e r e ve n t r u l e act ion Fie l d r e l at ion sh ip s
using field codes viewing Enter event rule action Environment variables custom fields file attachments issues requirement documents requirements source file attachments test cases test runs workflow events Errors resolving test run generation Escalation rules activating adding configuring deleting editing examples inactivating running manually Estimated hours Evaluating workflows Events activating adding configuring customizing toolbar deleting deleting from items editing editing details inactivating viewing details viewing history
469 470 454
Excel exporting traceability matrix opening items Exporting 248 26
526 526 517 521 519 527 522 524 526
audit trail records automation rules log item mapping rules requirement documents to text files to XML files traceability matrix External reports adding
481 459 465 253 93 90 248
142
F
282 Failing test runs Field-level security 452 449 448 452 451 449 452 452 429 426 hidden read only read/write Field codes custom fields issue label requirement requirement document test case test run 422 418 417 421 423 42 422 42 422 41 41 using in email templates Field labels marked with asterisk renaming restoring original Field relationships adding configuring deleting editing parent-child 408 407 409 409 407 410 409 411 550 529 540 533 532 535 537 469 298 325 324 324 324
634
In d e x:Fie l d s Fol d e r s l ist win d ow
Fields adding custom adding list items adding test variants adding users and customers configuring custom value lists defining default values defining required deleting custom deleting list items editing custom editing default values editing list items editing required hiding renaming restoring original labels time tracking File attachments inserting in test cases inserting in test run steps Filters accessing RSS feeds adding deleting deleting restrictions duplicating editing editing restrictions inserting restrictions Interactive Filter Wizard list window columns publishing using viewing viewing restrictions Finding advanced customers 38 39 154 97 118 118 118 117 117 118 30 24 153 29 31 31 385 380 386 39 388 406 406 390 380 389 407 380 407 329 409 411 429, 431 54 263 288
records users using quick find using type ahead searching Folder types activating adding changing for folders configuring deleting editing inactivating Folders adding adding items changing type deleting editing editing items entering details entering release planning information issues moving items ranking items removing items requirement documents requirements setting default Web page sharing test cases test runs viewing viewing history viewing items Folders list window Details pane Folders tree hiding panes Items pane
34 39 36 25
414 412 68 411 414 413 413
61 66 68 70 68 68 63 64 171 66 69 69 230 230 64 62 317 317 67 67 68 58 60, 63 58 58 59
635
In d e x:For mat t in g t e xt In se r t in g
Live Chart pane moving panes Release Planning pane Web View pane Formatting text Formatting toolbar setting options Functional requirements Functions for calculated fields Date DateTime global Item Item.Events Item.ReportedBy Math String
60 58 60, 64 61, 64 49 49 346 181 619 619 619 624 620 620 621 622 624
Hyperlinks adding to email templates 475
I
Icons list windows Specification Document window Ignoring test run results Impact analysis Importing item mapping rules requirement documents SoloBug files automatically SoloBug files manually text files XML files Inactivating customer escalation rules folder types 341 452 413 475 441 383 447 49 340 422 417 466 249 485 485 95 92 23 188 299 244-245
G
Generating built-in reports external reports test cases from requirements test runs Go to location record number 14 36 70 70 241 280
link definitions notification rules requirement types triggers user notification rules users workflow events workflow states
H
Has Calculation Error field Hiding fields Historical logging deleting information Historical requirement versions History change reports folders items links workflow events 45 67 44 81 41 482 236 405 324, 329
Indicators list windows Informational workflow events Initial workflow state Inline editing Inserting hyperlinks images restrictions screenshots shared test case steps 50 51 118 55 264 23 419 423 26
636
In d e x:In t e r act ive Fil t e r Wiz ar d List win d ows
stamps tables Interactive Filter Wizard Interface Investigating suspect dependencies Issues adding adding links assigning numbers creating from requirements creating from test runs creating requirements from creating test cases from custom fields default workflow assign comment enter work estimate fix force close verify deleting deleting additional reports details duplicating editing email folders links merging renumbering reopening viewing viewing history viewing workflow history workarounds Item mapping rules adding
53 51 30 11 83
configuring default settings editing exporting importing Item types
460 462 465 465 466 19
159 77 174 243 299 176 175 162
L
Last Error Date column Link definitions activating adding configuring default deleting editing 475 472 470 471 475 474 475 77 78 84 81 79 81 170 239 240 318 313 80 81 405
163 168 165 164 166 167 167 175 175 160 173 172 171 171 170 174 174 168 172 44 169 162
inactivating Links adding items to clearing suspect items deleting diagramming editing issues requirement documents requirements test cases test runs viewing viewing history List items adding deleting editing List reports creating stylesheets List windows adding tabs
380 380 380 119 126 557 21 32
464
637
In d e x:Live ch ar t s N ot ificat ion r u l e s
applying user-defined views changing column contents changing font settings closing tabs column filters customizing finding records indicators inserting columns moving columns opening printing removing columns renaming tabs report stylesheets saving reports as text selecting records sorting columns totaling columns using type ahead searching Live charts configuring X-axis configuring Y-axis copying creating deleting duplicating editing font settings printing toolbar types viewing viewing in the Folders list window Loading text file templates export import Local options formatting settings
28 24 23 32 24 23 36 23 23 24 22 27 24 32 562 152 22 24 24 25
general settings help and browser path settings live chart settings SCC integration settings stylesheet settings TestTrack TCM settings view file settings Locking projects requirement documents requirements viewing lock information Logged in users viewing Logging in Logging out other users
343 344 346 495 344 347 345
354 220 220 221
354 5 9 354
M
Mark up codes test cases test runs 259 260 82 174 455
146 148 73 143 152 152 151 346 73 72 145 71 72
Marking items as suspect Merging issues Modify rule action Moving items between folders list window columns requirements across documents
66 24 196
N
Non-functional requirements Notification rules activating adding system configuring 441 439 438 46 441 440 441 181
95 97
configuring user deleting editing
346
inactivating
638
In d e x:Or p h an e d e mail Re cal cu l at in g fie l d val u e s
O
Orphaned email attaching to records deleting managing viewing Outlook add-in attaching an email to a TestTrack item configuring settings connecting to a different server connecting to a TestTrack Server 514 513 514 513 156 157 155 155
hyperlinks import mail issue compliance issues reports required fields requirement document compliance requirement documents requirements requirements compliance send mail setting SCC integration SoloBug SoloSubmit test case compliance test cases test run compliance test run enhanced compliance test runs 407 298
360 362 369 361 377 374 369 368 367 369 361 497 364 364 369 366 369 371 366 375
creating TestTrack items from an email 514 disconnecting installing switching projects Overriding workflows Overview tab 514 513 513 428 12
P
Parent-child field relationships Passing test runs Passwords changing Percent done Prevent rule action Printing records Problem statements adding Process management Project options client compliance dictionary email field relationships fields file attachments folder compliance general 356 368 378 359 375 373 358 369 355 286 477 353 432 453 27
time tracking Project paths setting SCC Projects locking selecting switching unlocking Promoting customers users Promoting draft custom fields Publishing filters
497
354 5 6 354
338 337 387 153
Q
Quick find opening toolbar 36 36
R
Ranking items in folders Recalculating field values 69 404
639
In d e x:Re cor d in g t e st case st e p s Re q u ir e me n t d ocu me n t s
Recording test case steps Records finding printing selecting list window Regenerating test runs Release notes adding building Release planning creating reports entering information report stylesheets reports Release status reports creating stylesheets Remaining hours Removing items from folders list window columns requirements from documents Renaming field labels tabs Renumbering issues requirement documents requirements test cases Reopening issues Replying to tracked email Reports adding external charting data copying hyperlinks creating audit trail creating built-in creating detail
262
creating distribution creating list
125 126 130 133 327 152 135 138 128 551 152 119 119 152 151 70 70 119 285 551 120 120 121 121 119 119 152 151
34 27 22 282
creating release planning creating release status creating security group comparison creating text file templates creating time tracking
178 179
creating traceability creating trend customizing stylesheets
130 64 557 120 120 133 558 429
deleting detail distribution duplicating editing generating built-in generating external list manual testing
69 24 196
refreshing stylesheets release planning release status time tracking
409 32
traceability trend types
174 228 200 321 168 76
using text file templates viewing settings Required fields defining editing Requirement documents adding
406 407
181 193 77 193 192 222 194
142 139 70 480 122 123
adding existing requirements adding links adding new requirements adding requirements adding review notes appending requirements
640
In d e x:Re q u ir e me n t t yp e s Re q u ir e me n t s
assigning numbers creating snapshots custom fields default workflow approve assign comment enter work estimate implemented needs change no changes needed obsolete re-open ready for approval ready for review reject review note deleting duplicating editing email entering details exporting folders importing links locking removing requirements renumbering saving as PDF viewing viewing all differences viewing differences viewing from requirements viewing history viewing lock information viewing snapshot details viewing snapshots
228 230 183
viewing workflow history Requirement types activating adding
219
383 382 200 381 181 383 383 383
216 211 218 213 212 217 214 214 217 218 215 213 216 222 229 226 225 229 183 253 230 249 239 220 196 228 254 225 234 233 197 44 221 233 231
changing configuring default deleting editing inactivating Requirements adding
183
adding existing to requirement documents193 adding links 77
adding new to requirement documents 193 adding review notes adding to requirement documents appending to requirement documents assigning numbers breaking shares business changing types creating from issues creating issues from custom fields default workflow approve assign comment enter work estimate implemented needs change no changes needed obsolete re-open ready for approval ready for review reject 207 202 209 203 203 208 205 205 208 209 206 204 207 223 192 194 200 196 181 200 176 243 185
641
In d e x:Re se t t in g wor kfl ows Ru n e xe cu t ab l e r u l e act ion
review note deleting duplicating editing editing in Specification Document email entering details folders functional generating test cases impact analysis links locking making current modifying in Document View non-functional
223 201 199 198 195 229 185 230 181 241 244-245 240 220 237 191 181
folder inserting integer multiple list selection requirement documents security group single list selection string range test variant value text user viewing Resulting state for events Retrieving global customers global users Review Mode View toolbar Review notes adding to requirement documents adding to requirements editing Rolling back requirements RSS feeds accessing creating subscribing Rule actions auto assignment create snapshot enter event modify
113 118 105 109 115 111 108 102 116 100 111 31 419
337 336 190, 221 191
removing from requirement documents 196 renumbering reviewing in Review Mode View rolling back unsharing viewing viewing differences viewing historical versions viewing history viewing lock information viewing related documents viewing relationships viewing workflow history Resetting workflows Restoring field labels Restrictions adding company condition date range decimal number deleting editing 99 111 110 104 106 118 117 200 221 237 196 197 238 236 44 221 197 244 210 428 411
222 223 224 237
154 153 154
454 457 454 455 453 456 456 456
prevent run executable send email Run executable rule action
642
In d e x:S CC in t e gr at ion S ol oS u b mit
SCC integration attaching changelists attaching files changelists committing viewing check in options checking in files checking out files configuring creating file labels detaching files diffing files disabling editing files getting files local options project options rolling back files setting project paths setting user options undoing check out viewing file history viewing files Screenshots capturing Scripts creating from test cases Searching audit trail records examples Security command field structure Security commands issues requirement documents requirements 571 584 576 324, 565 324 323 478 38 303 55 510 511 498 508 503 495 507 512 506 512 502 501 495 497 510 497 496 511 504 502 500 499
test cases test runs Security groups about adding comparison reports deleting duplicating editing viewing Selecting list window records users and customers Send email rule actions Server connections adding deleting editing Sharing requirements between documents test cases steps Snapshots creating using automation rules to create viewing viewing details SoloBug customizing distributing importing files automatically importing files manually SoloSubmit customization notes customizing pages customizing static pages default fields default page names drop-down field codes enabling
593 600
323 324 327 330 330 326 326
22 39 456
8 9 9
194 264
230 457 231 233
483 483 485 485
489 490 490 490 489 492 487
643
In d e x:S or t in g l ist win d ow col u mn s Tab s
field codes finding project ID installing text field codes turning off cookies user field codes Sorting list window columns Source code files attaching detaching Specification Document window adding existing requirements adding new requirements adding requirements appending requirements changing field width columns customizing displaying numeric columns Document View editing requirements hiding field labels hiding formatting toolbar hiding numeric column totals hiding requirement summary in tree icons moving requirements removing requirements Review Mode View setting default width showing field labels showing formatting toolbar showing requirement summary in tree Spell check Stamps inserting Starting TestTrack
492 489 487 493 491 493 24
TestTrack Server Linux Mac Windows States activating adding configuring
7 7 7 7
417 416 415 417 416 417 423
499 512 186 193 193 192 194 187 188 186 186 188, 191 195 187 186 186 187 188 196 196 190, 221 346 187 186 187 52
deleting editing inactivating initial Stylesheets adding adding images to customizing default for printing list windows detail reports distribution reports list reports list window reports refreshing release planning reports release status reports time tracking reports traceability reports trend reports Subscribing to RSS feeds Suspect items clearing investigating dependencies marking marking all System notifications configuring
551 551 551 344 552 556 557 562 551 557 558 560 561 562 154
84 83 82 82
438
53
T
Tabs
adding to list windows
32
644
In d e x:Tag n u mb e r s Te st r u n s
closing renaming Tag numbers assigning to requirements Test cases adding adding excluded test variants adding included test variants adding links assigning numbers attaching automated tests attaching files in steps attaching scripts bulk field changes excluded test variants included test variants test variants correcting step errors creating automated scripts creating from issues default workflow assign comment enter work estimate hold needs change obsolete ready ready for review reopen resume reviewed deleting duplicating editing editing excluded test variants editing included test variants email
32 32
entering details entering steps detail grid view
256 257 260 257 260 317 241 264 318
200
free form text view grid view
255 269 268 77 321 305 263 305
folders generating from requirements inserting shared steps links managing test variants excluded included mark up codes recording steps
269 267 259 262 300 270 269 321 264 266 319 44 278
88 87 86 265 303 175 271 271 277 272 272 275 275 276 273 274 277 276 274 322 320 319 270 268 317
related test runs removing excluded test variants removing included test variants renumbering sharing steps test variants viewing viewing history viewing workflow history Test configs adding deleting duplicating editing viewing Test results entering in detail grid view entering in free form view entering in grid view Test run sets creating Test runs adding links adding problem statements adding run-time variants
177 178 178 178 178
286 289 285 281 279
77 286 291
645
In d e x:Te st var ian t s Time t r ackin g
attaching files in steps creating issues from default workflow assign comment enter result enter work estimate fail hold ignore result pass re-open resume start unclear deleting
288 299 292 292 296 297 293 293 298 294 299 298 295 295 293 299 316
viewing workflow history Test variants adding adding excluded to test cases adding included to test cases adding to test runs deleting from test runs editing excluded in test cases editing in test runs editing included in test cases excluded included removing excluded from test cases removing included from test cases TestTrack integrations Outlook third-party development tools TestTrack Server connecting to starting Text file import/export creating export templates creating import templates using export templates
296
386 269 268 291 291 270 291 268 269 267 270 269
513 515
deleting additional test variant information291 duplicating editing 315 314
7 7
editing additional test variant information291 email entering overall results entering results detail grid view free form text grid view failing folders generating indicating unclear results links passing regenerating resolving errors status test variants viewing viewing history 286 289 285 298 317 280 299 313 298 282 282 300 290 284 44 317 297
95 97 95 97
using import templates Text file report templates creating using Text files exporting to importing Time tracking built-in event field calculating totals capturing values choosing a field type creating reports default fields entering release planning information
152 152
93 95 429 429 431 429 430 135 433 64
646
In d e x:Tool b ar s U se r op t ion s
event custom fields report stylesheets reports selecting for event setting project options viewing data viewing work items Toolbars customizing customizing events quick find Totaling list window columns Traceability creating reports impact analysis report stylesheets reports requirement links requirement relationships Traceability matrix exporting to Excel icons toolbar using Transferring customers to users list users to customers list Transitions configuring editing initial state Trend reports creating stylesheets Triggers activating adding adding default after save
430 560 121 419 375 433 44
before save configuring deleting editing examples inactivating ttpubdata.exe ttstudio addresses
443 441 447 447 443 447 361 14 360 25
16 421 36 24
ttweb.exe Type ahead searching
U
Unlocking projects 354 220 196
138 244-245 561 121 240 244 247 248 247 248 246
requirements Unsharing requirements User-defined views applying to list windows creating deleting editing User interface mode changing User notification rules activating adding
28 28 29 29
16
49 47 46 49 48 49
341 341
creating deleting editing
423 423 423 119 128 562
inactivating User options add multiple items settings dictionary settings differences display settings display settings general settings
348 351 349 348 347 350 496 350
447 444 446 443
overview tab settings SCC integration settings search settings
647
In d e x:U se r s Wor kfl ow comp on e n t s
setting spell check views settings Users activating adding
347 353 351
logged in users orphaned email report settings requirement document snapshots
354 155 151 231 225 197 31 326 319 178 300 284 75 339 44 33 41 41
340 330
requirement documents requirements restrictions security groups test cases test configs test run status test runs tracked email users work items workbook tasks workflow event details workflow event history Views
adding company, division, and department332 adding to fields deleting duplicating editing finding inactivating logging out making customers promoting retrieving global viewing 39 341 340 339 39 340 354 341 337 336 339
V
Validating audit trail records Value lists configuring custom lists modifying lists Variance Versions viewing historical requirements Viewing audit trail records automation rules log customers email notification hyperlinks email templates filters folders historical requirement versions issues items in folders links 479 458 339 476 470 31 67 236 172 68 80 236 388 379 432 481
applying deleting editing
28 29 29
W
Work items viewing Workbook tasks adding deleting duplicating editing viewing Workflow assignment rules Workflow components assignment rules events states transitions 414 414 414 414 33 34 34 33 33 424 44
648
In d e x:Wor kfl ow e ve n t s X M L
Workflow events activating adding custom tab fields tab adding details allow attachments assignments option include notes informational event Make event visible in review mode mark dependent items as suspect require signatures resulting state time tracking option configuring customizing toolbars deleting deleting from items editing editing details inactivating viewing details viewing history Workflow states activating adding configuring deleting editing inactivating Workflow transitions configuring editing initial state Workflows diagramming diagramming item history editing resulting state 427 43 424 423 423 423 417 416 415 417 416 417 420 419 420 419 420 420 420 419 419 417 421 423 42 422 42 422 41 41 422 418 420 421
evaluating overriding resetting time tracking viewing event history viewing work items
426 428 428 429 41 44
X
XML exporting to importing files 90 92
649

Ttuserguide

Uploaded by

Copyright:

Available Formats

Ttuserguide

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ttuserguide

Uploaded by

Copyright:

Available Formats

TestTrack

Learning the Basics

Using Advanced Features

152 152 152 152 153 154 155

Using TestTrack Pro

Using TestTrack TCM

470 475 476 477 477 477 482

Integrating with Source Control Tools

Using the Outlook Add-in

Appendix A: Third-Party Development Tool Integrations Appendix B: Environment Variables

526 526 526 527

Appendix C: Field Codes

Appendix D: Report Stylesheets

Appendix E: Security Commands

Appendix F: Calculated Custom Field Functions

Appendix G: Fields Affected by Administrative Changes Index

Before you start

Connecting to a different server

Starting the TestTrack Server

Connecting to the TestTrack Server

The Setup Server Connections dialog box opens.

Adding a server connection

Editing a server connection

Deleting a server connection

About the TestTrack interface

U sin g t h e Ove r vie w t ab

Quick find toolbar

Workflow events toolbar

Using the Overview tab

Using the Address bar

Opening items using ttstudio addresses

Entering ttstudio addresses

To open a list windowttstudio://ServerAddress:Port//ProjectName/ItemType To open a specific item ttstudio://ServerAddress:Port//ProjectName/ItemType?Parameter&Parameter

To open a specific: Customer

Use an item type parameter: cust

number recordID historyID

path recordID historyID

number recordID historyID

name recordID historyID

Security group Specification document Task

To open a specific: Test case

Use an item type parameter: tstc

Use the specific item parameter: number recordID historyID

number recordID historyID

username (global users only) recordID

Changing the user interface mode

Ch an gin g t h e u se r in t e r face mod e

Learning the Basics

U sin g List Win d ows

Using List Windows

U sin g List Win d ows

Opening list windows

U sin g List Win d ows

About list window indicators

Customizing list windows

Changing font settings

U sin g List Win d ows

Changing column contents