As a consultant, I have been exposed to many different development methodologies and processes. In most cases, assignments are performed by a person that is aware of staff resources and distributes tasks according to the availability of these resources.
Continue reading…
TestTrack Pro
If you are a loyal reader of this blog, chances are that you read Gerhard Kruger’s post about our Visual Studio Integration. In this article, Gerhard talks about accessing TestTrack Pro items and Surround SCM actions from within Visual Studio. I’d like to present a different angle to this integration, specifically, the TestTrack Pro integration.
Continue reading…
Filtering is a great way to slice data on a daily basis. They really form the basis for working efficiently with your development and QA artifacts. It’s typical for a customer to have 10,000+ issues/bugs/feature requests in a TestTrack project – filters allow users to narrow that list of data to what is relevant to them at any given moment. In this post I want to highlight the filter run time feature that makes creating and maintaining a usable list of filters much easier.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponBeing able to easily and quickly segregate data by various criteria is a requirement of any product that claims to be “easy to use.” For example, product management is interested in commonly reported issues and feature requests during product planning, but nearing the end of a release cycle they’re focused on critical issues that could delay the release. QA wants to see test runs yet to be executed or those that need to be re-run and development wants to see approved requirements that are ready for implementation. All of these scenarios create the need for distinct and re-usable “views” of the artifacts in TestTrack. This is where TestTrack’s tabbed views can make life much simpler for you as a user.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponThe list report grouping stylesheets, introduced in TestTrack 2009, have been tremendously helpful to customers looking to slice data by various attributes, such as hours worked by product/component.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
Using TestTrack’s automation rules is a great way to populate field values, move an object through the workflow, interface with another system, and notify the right people about what is happening in their project. Some of these rules can get complicated and often some tracing and debugging is necessary to make sure the rule is working as you designed it.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon A common question I hear from TestTrack users is how to display a value that was entered as part of a workflow event on the main issue/test case/requirement window. As some of you may know, this is not “out of the box” functionality. However, this can be configured rather easily using automation rules and custom fields.
The only requirement is that the field on the main window has to be of type “String”.
Continue reading…
Escalation rules allow you to evaluate a certain condition on a continuous, scheduled basis. The most common use for escalation rules is to prevent inactivity on items. For example, every day at midnight, check for any items that have not been modified in the last 3 days. Escalation rules also allow you to configure an action or actions to perform on any item that matches the criteria, which is specified in the form of a filter.
Continue reading…
Our support group is commonly contacted with email notification problems. This can be tricky to troubleshoot because there are many moving pieces and it is difficult to isolate the cause. This post includes some troubleshooting tips I learned as a member of the support group.
Continue reading…
I posted a simple tutorial in the Seapine Labs on setting up the workflow in TestTrack. The tutorial shows how to implement a TestTrack Pro workflow from scratch and explains the various components of the workflow and how they work together. Plenty of screenshots are attached, including several workflow diagrams that show how the workflow evolves as states and event are added.
If you have any comments or questions, feel free to leave a comment.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
