Prospective customers often ask me if there is a way to approve all the requirements in a requirement document at once.
I usually ask a few questions before responding:
One of the many advantages of using a fully integrated suite like TestTrack is the ability to connect artifacts from different parts of the development process. When we first released TestTrack RM, I blogged about the complete traceability that you get with TestTrack.
TestTrack provides two ways to connect artifacts:
Sometimes it is easy to get these two confused and know when each one is used.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponSurround SCM 2011 includes the ability to track changes across branches. This feature allows you to easily find out if a change made it to a specific branch. It also gives you a level of traceability that should help streamline your development efforts and save time.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
Make plans to join us when the Seapine ALM Tour 2010 stops in Huntsville, Alabama on September 23. Meet some of our product management team, see the upcoming Seapine ALM 2011 release, and learn ways to boost agility, collaboration, and traceability! It’s all free!
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.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
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 . StumbleUponDo 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 . StumbleUponWe 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…
Last week, Seapine Software presented a webinar called “Transparent Traceability in Life Sciences: A practical approach to compliance in your development lifecycle”. The program was presented by Paula Rome, Sr. Product Manager, and myself and was moderated by Jay Luis, VP of Marketing. Preparing for these webinars is harder than I thought but we’re all very happy with the result.
Continue reading…
Before I worked for Seapine Software, I was employed by a now defunct software company in the Cincinnati area. It was a small company, with about 25 employees or so. I did many jobs at this company. My main duty was customer support, but I also did things like testing, managing our bug tracking system, putting together our releases, and other things.
Reading Matt’s post on his co-op where he tracked tests on a spreadsheet made me reminisce about my old employer. You see, our defects were written down on paper. Screenshots were physically attached (I mean we used a stapler) and notes, comments, and anything else were usually handwritten all over the place.
Continue reading…
Page optimized by WP Minify WordPress Plugin
