May 16, 2012

5 Features You Should Consider Using In TestTrack

Helix ALM
TestTrack is an excellent tool for managing any project, especially a software development project. There are several features that I find particularly useful in my role as a senior software developer, and I'm going to talk about those features now. 1.  Tabs Tabs are something I use every time I log into TestTrack, specifically for Issues. I am often in a situation where I have to keep track of multiple development efforts at the same time. While filters help with allowing me to look at a subset of Issues on which I need to focus, being able to switch quickly between tabs where my different lists are displayed is an incredible time saver. I configure my first tab to show all the Issues currently assigned to me. I have other tabs to display Issues I have created and Issues I have addressed. I also configure other tabs to display Issues involved with current tasks that I’m currently working on. Finally, I have a tab that will show me only Issues created within the last couple of days, so that I can see if there are any new Issues that I might need to address. 2.  Workbook The Workbook list is a feature that is often overlooked. Its primary use is to store Task records, which can be used to record things that need to be done that are not related to an Issue, Test Run, or a Requirement. However, another feature of the Workbook list is that it will show all items that are assigned to you, regardless of their type. If you are working on several different things at once, including Issues, Test Runs, Requirements, and Requirement Documents, you can view all your current assignments in this list. This is incredibly useful for me to see what items need my immediate attention. 3.  Links Linking items is a terrific way of relating items that have some relationship that you want to document. I often see where different users find multiple Issues that on the surface seem unrelated, but after examination they are found to originate from the same original problem. In these situations I prefer not to merge all of these Issues, but instead create links between the Issues. I usually link Issues as related items. However if I find that one particular Issue is the primary problem, I can set it up as as the Parent in the relationship, and the other Issue as children. This helps establish the relationship between the Issue. 4.  Screen Capture This feature may be one of my favorite recent additions to TestTrack. Screen capture allows you to take a snapshot of your current monitor display and save it as a file attachment or an inline image in a text field. It also provides some basic image editing tools to mark up the image. I find this very useful when developing or testing an application. I can immediately move to TestTrack when I want to create an Issue, write up the description, then capture the screen shot within the client. I also like to use the editing tools to mark up the image to point to the problem I am trying to describe. 5.  Insert Stamp This is a smaller but still useful feature depending on how you implement TestTrack.  In our TestTrack projects, it is common for people to edit descriptions and events to add additional details or notes. Insert Stamp offers a quick way to enter a quick indication of who and when an additional bit of information is added. This feature has the nice benefit of giving the user a quick way of adding the date or your name to a comment you added. In addition, if all the users of a project use the feature consistently, it creates a standard way to annotate text in your project. And it can be configured to meet your project needs. Those are my top 5 TestTrack features. If you're not using them currently, take a few minutes to check them out. What are you favorite features?