Making a QA Analyst’s Life Easier: Linking Requirements and Tests in TestTrack
It’s no secret that we also use the products we develop at Seapine Software. Earlier this week, I was running some tests and had a flashback to the (dark) days before requirements management was introduced in TestTrack. It quickly dawned on me the importance of managing requirements alongside test cases, test runs, and other artifacts in TestTrack. Plus, it was a good example of how linking and traceability in TestTrack makes everyone’s job much easier.
I was running some test runs from a regression suite and came across one that didn’t make sense to me. I decided to check the functional design to see how the feature was actually supposed to work. Since we link test runs with the test case they are generated from, it was easy to go directly from the test run to the related test case. However, when looking at the test case, I realized it was written before we managed requirements in TestTrack. So, I had to hunt for the Microsoft Word design document in Surround SCM. Then, I had to take the time to comb through the Word document to find the specific requirement that described the functionality. Not fun and kind of time-consuming.
Later that same day, I had a similar experience with another test run. However, this time I opened the test case and was happy to see that the test was written after we started managing requirements with TestTrack. Because the test case was linked to the requirement, it was easy to go directly to the exact requirement the test case was written for. I was then able to correct the test case and get back to testing quickly. Wow, that was so much easier!
Linking test cases to their originating requirements really does make a QA analyst’s life easier. I saw first hand how much time is saved when researching questionable tests. Not to mention the frustration eliminated since it was easy to find exactly what I needed.