November 10, 2014

3 Essential Widgets for Monitoring Product Testing

Helix ALM
Note: This blog post refers to TestTrack 2015 and earlier. The home page was replaced with dashboards in TestTrack 2015.1.   Home page widgets in TestTrack are a great way to monitor important metrics or KPIs related to your product development process. If you're just getting started with widgets, here's a post on general best practices when using widgets and here are tips for using widgets to monitor product requirements. This post is going to cover widgets for monitoring product testing. widget0  

#1 - Watch for Suspect Test Cases

With built-in traceability, TestTrack makes it easy to link requirements and system specifications with test cases. When a requirement or spec changes, all related test cases can optionally be flagged as "Suspect" which just means that they should be reviewed. The design change could be minor, in which case the associated test cases don't need to be updated. On the other hand, change could be a complete overhaul of the design, in which case the existing test cases will need to be re-written. Either way, flagging test cases as "Suspect" ensures that testing stays in sync with product design and development. The first widget will call attention to any test case flagged as "Suspect" and make it easy for the team to quickly identify and update test cases that need a review. Remember that creating a widget is a two-step process. First you create a filter, then you create a widget to use the filter. For this widget, you just need to create a simple filter with criteria of "Is Marked as Suspect" is true. Once the filter is saved, create the widget by going to Tools > Administration > Home Widgets and clicking the + button. For this example, I’m going to tag testing widgets in green but you could use a 2-color mapping if you want to highlight when the number of suspect test cases hits a certain threshold. widget1 By clicking the widget from the Home Page, the team will see the full list of suspect test cases and can start to conduct their reviews to make sure testing stays in sync with product design changes.

#2 - Remaining Test Runs

Looking for a way to make it easy for testers to come into the office, grab an outstanding test, and get right to work? This widget can do just that, providing testers with a complete list of tests that still need to be run. This widget's filter is meant to be changed over time, to point to the the latest set of tests. As an example, let's pretend we're in early stages of developing the 1.0 version of Wysi CRM. I'm going to point the at the Wysi CRM 1.0 Sprint 1 folder, which is where all of my active tests are right now. I'm also going to filter on workflow state so it shows only tests that haven't been run. When we move on to sprint 2, I would update this filter to show the team tests in sprint 2. widget2 Again, I'm using green to denote testing widgets so I'm sticking with a single color mapping for this widget. By clicking this widget, anyone on the team can get a list of tests that need to be run, and get to work! widget3

#3 - Approved Requirements With No Test Coverage

The third widget is focused on helping team members quickly identify what they need to work on next. In this case, we're watching for requirements to be approved and then the team can jump in and develop test cases. For the filter, create a Requirements filter that looks for Approved requirements that don't have a "Requirement Tested By" link. Keep in mind that the link type will depend on how you've configured TestTrack; in the Sample Project this link type denotes tests that verify a specific requirement. widget4 Setting up the widget itself is straightforward, I'll stick with using green to denote testing widgets. Now anyone on the team can click this widget, grab an approved requirement, and start writing test cases. widget5 So there you have it—3 widgets to help your team monitor product testing and grab whatever work needs to be done next. If you’ve created some cool widgets for your team, leave a note in the comments below. I’d love to hear the details!