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…
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.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponWe published several TestTrack sample projects a while back, but we didn’t do much documentation on them and they were buried way down in Seapine Labs. We’ve taken some steps with the 2010.1 release to improve those samples and make them more visible.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponRSS feeds are a great way to expose your issues, test cases, and requirements to external users. You can provide a feed of critical issues to the product management team, give the product owner a feed of all stories in the current sprint, or give customers access to their feature requests.
RSS feeds are based on filters you set up for specific item types. The key is to set sharing to Publish.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
Do you commonly write test cases for project requirements only to find out that you were looking at the requirement from last week and now the edit boxes are drop-downs and the radio buttons were turned into check boxes? So you have to go back and re-work the test but of course time isn’t in the schedule so you’re spending your evenings updating stale test cases. This huge headache is caused by a simple lack of communication. If someone had told you the requirements changed, you could have easily tracked down the latest copy and avoided the re-work.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponTestTrack 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…
When you’re ready to share your Surround SCM evaluation with your team, it’s relatively straightforward to enable access for those users. The following steps will walk you through the process.
Note that by default the administrator user (no password) is the only account that can access Surround SCM. The following steps will let you add additional users to your Surround SCM installation. Also, be sure to open port 4900 (default for the Surround SCM server) on the machine running the server so the rest of your team can connect from their desktops.
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
