qunitjs / qunit / 2591

89%

main: 90%

push

travis-ci-com

Core: Decide "No tests" based on test count, not assert count

If a test has no assertions, that is generally by itself another
unrelated error. But more importantly, it is configurable, and
also something that we support on a per-test basis via
assert.expect(0) for which there are several use cases such
as when the tests only purpose is not to throw, either from
your source code, or from another helper library (e.g. Sinon
assertion's throwing).

Previously, if your test suite composed only of such tests,
or if you selective run such test only, it wrongly caused
the test runner to report a global error for "No tests."

Fixes https://github.com/qunitjs/qunit/issues/1405.
Closes https://github.com/qunitjs/qunit/pull/1449.

901 of 1910 branches covered (47.17%)

1693 of 3052 relevant lines covered (55.47%)

151.07 hits per line