id,summary,reporter,owner,description,type,status,priority,component,severity,resolution,keywords,cc,release
7486,Customizable test case outcomes (aka verdicts),seccanj,seccanj,It would be cool_ if one could define a set of possible verdicts. \r\n\r\nYou have "Successful"_ "Untested"_ and "Failed"_\r\n  which is OK for many purposes. But if you do tests\r\n  according to one of the many standards_ you might have\r\n  different needs. E.g. ISO-9646 has five verdicts:\r\n\r\n  None = no result yet_ untested\r\n  Pass = good_ successful\r\n  Inconc = inconclusive_ unclear\r\n  Fail = bad_ failed\r\n  Error = there was an error in performing the test\r\n\r\n  If you test according to POSIX 1003.3 you have the verdicts:\r\n\r\n  PASS = good_ successful\r\n  FAIL = bad_ failed\r\n  UNRESOLVED = inconclusive_ unclear\r\n  UNTESTED = no result yet_ untested\r\n\r\n  Some testing frameworks add XFAIL (= expected fail)_ UPASS\r\n  (= unexpected pass) and UNSUPPORTED (= the implementation\r\n  under test doesn't support a feature) to the POSIX verdicts.,enhancement,closed,normal,TestManagerForTracPlugin,normal,fixed,,rjollos_ manolowolder,0.11