The Seapine View

QA Wizard Pro’s AddDefect statement can be used to automatically add a defect to a TestTrack project. The AddDefect’s statement parameters are used to populate the Summary, Description, Steps to Reproduce and Hardware fields of the defect. This statement is commonly used with an If statement to add defects to TestTrack Pro if a condition that causes the script to fail is not met.

Note: Use Tools > TestTrack > Configure TestTrack to connect to a TestTrack project. Keep in mind that you can configure the TestTrack project to email confirmations to a designated user.

Following are two examples of a script that tests a web site to ensure seven different choices appear in a drop-down list when a web browser page is accessed. The first script creates a defect in TestTrack that includes basic information about the failure. The second shows how you can pull information about the failure and send that data to the TestTrack defect to help with reproducing and validating the defect.  Continue reading…

I was recently on-site with a customer. Aside from the usual tasks, like conducting training classes and configuring workflows, there was one interesting challenge. The customer wanted to integrate TestTrack RM and TestTrack TCM with ClearQuest. The customer did not want to use the ClearQuest API because they were using a very old version of ClearQuest and were planning on upgrading. The risk of changes in the API between the versions was high.

Continue reading…

We recently released version 2010.1 of TestTrack, which contains many new exciting new features. One new feature that I would like to give some love to is Item Mapping Rules. This feature will benefit users who have more than one TestTrack applications, as it allows you to configure how field values are mapped from one application to another.

Continue reading…

With Seapine License Server 2010.1.1 and later, you can configure license pools to manage access to floating licenses.  This gives you the ability to maximize use and distribute floating licenses across business units, divisions, or geographic locations. It can also help ensure that specific users, such as developers or testers, always have access to a license.

Continue reading…

I prefer using Mac OS X as my operating system. However, I often need to connect to multiple projects at once. This is a problem because Mac OS X only supports running one instance of an Application Bundle, so you can only run one instance of TestTrack at a time.

Continue reading…

I got a call from a TestTrack TCM user who asked if you could schedule scripts to run on a continuous scheduled basis, rather than just once. I responded that you couldn’t, mainly because each test run represents a single execution of a test, not a continuous one.

I asked the user for more details in order to better understand the need. He revealed that his group does automated builds and wanted to launch tests after each build and log those results in TestTrack TCM. He wanted to incorporate TestTrack TCM with the automated build process and did not know how to.  So how do you do it? Well the answer will vary depending on your process.
Continue reading…

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.

Continue reading…

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…

We recently released a new requirements management product, TestTrack RM.

The early feedback on the product has been great. TestTrack RM is proving to be a valuable addition to the TestTrack family, which also includes TestTrack Pro (defect management) and TestTrack TCM (test case management).

While TestTrack RM provides many benefits on its own, the real power comes when it is used as an integrated solution with the other TestTrack applications. For example, you can easily determine if you have proper test coverage by ensuring that a test case has been created for every requirement. You can easily flag a test case if a requirement has changed, avoiding testing stale data and wasting time and money. For this post, I want to focus on one of the biggest benefits: complete traceability.
Continue reading…