You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a whole test is skipped using test.skip(), there is nothing in the TAP output indicating that fact. (only skipped assertions show up as # SKIP in TAP out)
I am not sure if putting SKIP directive on the test line is valid TAP, I think it is not, so maybe we can output something like this for an skipped tests:
# MyTest
# ok 1 # SKIP MyTest has been skipped.
This can help skipped tests "not get lost" since CI reporters can report on number of skipped tests and set builds to failed or at least unstable when there are skipped tests.
The text was updated successfully, but these errors were encountered:
Also a question: if I have an assertion that I want to skip temporarily, what's the way to do it? I expected either t.equal(foo, bar).skip('skipped until baz is ready') or t.skip('skipped until baz is ready').equal(foo, bar) to work but neither seem to do it.
+1 for this as not having reporting of skipped tests seems a bit odd. I'm doing QA with a team where I'll skip tests I know fail, so that the devs can pick them up later and fix them up.
When a whole test is skipped using
test.skip()
, there is nothing in the TAP output indicating that fact. (only skipped assertions show up as # SKIP in TAP out)I am not sure if putting SKIP directive on the test line is valid TAP, I think it is not, so maybe we can output something like this for an skipped tests:
This can help skipped tests "not get lost" since CI reporters can report on number of skipped tests and set builds to failed or at least unstable when there are skipped tests.
The text was updated successfully, but these errors were encountered: