Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add ability to mark a Test as skipped or incomplete

See original GitHub issue

Past discussion: #434

Would a PR adding the ability to skip tests be a welcome change? On a custom fork of TinyMCE we’re modifying the functionality and as such certain tests are failing. We want to keep the tests in the codebase and are currently forced to comment them out. Having the ability to skip tests would be the best solution in this case.

The syntax would be test.skip(func...).

I’ll gladly make a PR for this, just looking for approval before I start working.

Issue Analytics

State:
Created 9 years ago
Comments:21 (18 by maintainers)

Top GitHub Comments

1reaction

JamesMGreenecommented, Aug 27, 2014

Perhaps we could add a generic status property to the test result data? e.g.

“passed”
“failed”
“skipped”/“inconclusive”
“pending”/“not implemented”/“future”/“incomplete”

0reactions

JamesMGreenecommented, Sep 17, 2014

For anyone else who wants the Mocha-style “pending” syntax, I created this little plugin to build on top of @leobalter’s QUnit.skip implementation: JamesMGreene/qunit-pending

Since QUnit core v1.16.0 isn’t released yet, it is currently depending (from a dev/Node perspective) on a personal branch I created that is a copy of the latest specific commit in the master branch. I’ll be sure to update the dependencies in the “package.json” when QUnit core v1.16.0 is published.

P.S. I fully admit this syntax is harder to search for.