<![CDATA[Gurock Software Support Forum - Test Run Test Status; Request for Additional Status or Customization]]>2009-11-06T19:08:38ZPunBBhttp://forum.gurock.com/topic/303/test-run-test-status-request-for-additional-status-or-customization/<![CDATA[Re: Test Run Test Status; Request for Additional Status or Customization]]>Thanks for the suggestion. Allowing test status customizations is currently not planned but I can certainly see how this additional test status (and a few others maybe as well) would come in handy. We will think about that (and about supporting customizations) and I added it to our feature request list, thanks!
Regards, Tobias
]]>http://forum.gurock.com/user/4/2009-11-06T19:08:38Zhttp://forum.gurock.com/post/946/#p946<![CDATA[Test Run Test Status; Request for Additional Status or Customization]]>We'd like a test status of "Blocked" (rather than or in addition to "Retest"). We are tending to create Test Plans composed of a Run of Suites of Test Cases for a specific Test Milestone which corresponds to a weekly or bi-weekly build schedule. When a test fails that impacts our ability to test subsequent or dependent functionality we'd like to mark those blocked. In reality, we'd seldom "patch" or do an interim build during the test run where "Retest" would tend to get used in our environment. I'd rather just mark the tests "Blocked" without implying either a "Fail" or "Retest".]]>http://forum.gurock.com/user/31/2009-11-06T00:27:01Zhttp://forum.gurock.com/post/941/#p941