The Seapine View

Time tracking in TestTrack is a feature that has been written about on this blog here and there. Time tracking is a pretty straightforward concept. You estimate how long it will take to complete a task and, as you progress, you report on how much effort you have put in and how much time you think there is left to complete the task.

However, time tracking in TestTrack TCM can be tricky because there are two objects, the test case and the test run, to track time for. It can be confusing to know which object you are placing an estimate on and what it really means.

Continue reading…

One question I get every now and then is how to implement a test sequence in TestTrack TCM.  The concept of “before you test Y, you must test X first”.

There isn’t a specific feature in TestTrack to address this but there are actually several ways to implement test sequences. Following is one way.
Continue reading…

Recently, a customer asked the following question: “How can you filter the list of test runs based on the test variants it contains?”

The reason the question came up is because, while you can display a “Test Variant” column in the Test Runs list window, you can only filter the column between runs that have variants and those that do not.

Continue reading…

TestTrack TCM includes support for running and monitoring automated test scripts. If you’re using QA Wizard Pro, that support is ready out of the box. We also have a plug-in for TestComplete and instructions for integrating other tools into the TCM framework. Don’t hesitate to ask support how to best connect TestTrack TCM to your existing automated tool set.
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…

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…

Back when I was a co-op in college, I had a dedicated machine where I did all of my testing. I meticulously followed a (usually very long) checklist to make sure that the latest and greatest feature worked as expected. Excel was our bug tracker and we certainly didn’t have anything to handle the testing work itself. The great thing was, we just installed the app and started testing!
Continue reading…

The following example illustrates how you can automatically generate test runs based on changed files in Surround SCM.

The program first queries Surround SCM for changes in a specified repository in a specified branch within a specified time range.

If there are files that have changed, the program then checks the TestTrack project for any test cases that have any of the files attached in the source code tab.

For any test case that has a changed source code file attached, a test run is generated for every combination of “included” test variants.
Continue reading…

A common request of Technical Support is how to show Test Runs and only the defects created by that Test Run. The following is an example of a new TestTrack report template that provides this information.
Continue reading…

QA Wizard Pro’s Text View allows you to create more complex and flexible scripts than is possible with Grid View. In Text View, you have direct access to the scripting language and code. You can create and edit statements, modify scripts, and add advanced logic to scripts.

You may want to work in Text View if you have experience working with VBScript-like statements and have some programming knowledge. If you are new to QA Wizard Pro, you may want to use Text View as you become more familiar with the program. Many testers find that they can work faster and more efficiently in Text View.
Continue reading…