Seapine recently held an event in Huntsville Alabama for military contractors and government employees. The focus of the event was Seapine’s quality-centric approach to application lifecycle management (ALM), and this was an audience where quality mattered.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponQuality
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…
If you use Surround SCM or any other robust software configuration management tool (gasp!), chances are you are using branches to manage your software development process. Depending on your branch strategy, you may find yourself with a defect that exists across multiple branches. There are many ways to manage this situation, the best one for you will depend on your environment and needs.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
I worked with a developer once who was troubleshooting a defect I found, and after trying to duplicate it his response was “it works fine on my machine.” He was technically correct (it did work fine on his machine), and he wasn’t trying to avoid solving the problem, he was merely commenting that the code was functioning properly on his system. After working on it for some time, we found that at one point in the past he had an older version of the software on his machine which included a library file that was missing from the new version. Hence, when he ran the program it functioned properly, yet on a new install it would fail.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
