In addition to PASS & FAIL, also add test result class SKIPPED (or similar)?

[GoogleCodeExporter]

We are using GTEST for very many tests, however all test in our test case 
definition are linked together and executed. Unfortunately, some tests can 
only be executed if the environment is correctly set up (must be done 
manually). Therefore these tests are always failing, but in fact they could 
not be executed.

Would it be possible to the test case result "SKIPPED" as a new class to a 
test case (maybe colored yellow ;-) to abort a test if it determines it 
cannot be executed in this environment?

Original issue reported on code.google.com by [email protected] on 2 Jul 2009 at 5:30

[GoogleCodeExporter]

(sorry, should not be classified "defect" but "enhancement" proposal)

Original comment by [email protected] on 8 Jul 2009 at 9:12

[GoogleCodeExporter]

We need to hear what other users think about this.  Could you start a 
discussion in
the discussion group?  Thanks.

Original comment by [email protected] on 16 Jul 2009 at 7:46

• Changed state: Accepted
• Added labels: OpSys-All, Type-Enhancement, Usability
• Removed labels: Type-Defect

[GoogleCodeExporter]

We also need to coordinate this change with existing test runners such that 
they can understand the new SKIPPED status.

Original comment by [email protected] on 27 Sep 2010 at 7:02

[GoogleCodeExporter]

+1 -- this would be awesome. Typical use case would be testing a library that 
might do things that require administrative privileges. If the tests are run as 
a limited user, then the requiring-root tests would have a guard marking the 
test as skipped if administrative privileges are absent.

Other xUnit style testing frameworks often call this state 
"Assert.Inconclusive()" or similar.

Original comment by [email protected] on 3 Jan 2013 at 5:43