Skip to content

test: Avoid misleading diagnostic when some tests are skipped

Simon McVittie requested to merge smcv/dbus:tap-skip into master

If we have 7 test-cases, of which we ran 3 and skipped 4, then it's misleading to say "7 tests passed". Diagnose this as "3 tests passed (4 skipped)" instead.

We can either skip tests by putting a specific test name on the test command-line, or programmatically (for example the fd-passing test is always skipped on Windows, because Windows cannot implement Unix fd-passing).

Resolves: #363 (closed)

This is an alternative to !234 (closed), which I think is more in the spirit of the TAP specification, but hopefully resolves the confusing output reported as #363 (closed). It's consistent with the output we get when we pass -s or -x to the tests that use GLib's test framework.

Merge request reports