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