« Excel truncating imported data | Main | Can I assign multiple people to a test plan? »
Mapping requirements to test cases
June 1, 2009
A common feature request from customers is to have Test Run support an additional field that allows them to associate a functional test ID with a test case. Understandable considering so many other tools support that field - any a million others. But supporting additional fields goes against the design philosophy of Test Run.
Test Run was design to have a much more adaptable schema by using "tags" - which provide a more free form way for each individual user to structure and organize their test cases.
Therefore, within Test Run the base way is develop a naming and tagging convention for requirements. For example, I could easily associate one more test cases with the same functional requirement identified by the string "UI-4522.2" by adding the tag "req-ui-4522.2" to each of the related cases. Because it exists as a tag, I can now easily filter and search by that tag to pull up all relevant cases.
About Byrne Reese
Byrne Reese is a product manager by day and an engineer by night.
He conceived of Test Run to help project managers like him stay up to date and informed of what his team was working on.