• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

qunitjs / qunit
90%

Build:
DEFAULT BRANCH: main
Repo Added 29 Jan 2014 03:09PM UTC
Files 37
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH main
branch: SELECT
CHANGE BRANCH
x
  • No branch selected
  • 2.x
  • main
  • next

10 Oct 2025 01:53AM UTC coverage: 90.446%. Remained the same
18394266389

push

github

Krinkle
CLI: Fix TAP compliance for colon in unquoted YAML diag

When an assertion message contained a colon followed by a space,
and otherwise is a single line of ASCII characters, we formatted it
as an unquoted string. This is invalid in YAML 1.2, and thus tap-parser
would ignore the diagnostic block.

This does not affect the TAP result itself (the test name and failure
status are separate from this), and it does not affect the QUnit CLI
output where the information is shown either way.

When passing the CLI output to tap-parser (such as in QTap), it
silently ignored the "diag" block containing the assertion
message/actual/expected value, because it is not valid YAML.

Note that YAML 1.2 does allow literal colons and hash tags in unquoted
strings, when they are not followed by or preceded by a space, but
I'm keeping our version simpler by erring toward quoted strings when
these appear. Just because we could squeeze one more edge case with
plain unquoted strings, doesn't mean we have to. This way keeps our
format a bit more intuitive by making it predictable and easy to
deduce why a string is quoted or not, based solely on the chars used
and not based on obscure YAML internals.

Ref https://yaml.org/spec/1.2.2/#733-plain-style

1 of 1 new or added line in 1 file covered. (100.0%)

1865 of 2062 relevant lines covered (90.45%)

3291.82 hits per line

Relevant lines Covered
Build:
Build:
2062 RELEVANT LINES 1865 COVERED LINES
3291.82 HITS PER LINE
Source Files on main
  • Tree
  • List 37
  • Changed 1
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
18394266389 main CLI: Fix TAP compliance for colon in unquoted YAML diag When an assertion message contained a colon followed by a space, and otherwise is a single line of ASCII characters, we formatted it as an unquoted string. This is invalid in YAML 1.2, and t... push 22 Feb 57744 06:55AM UTC Krinkle github
90.45
18309593312 main Docs: Fix iframe width on homepage Ref https://github.com/qunitjs/jekyll-theme-amethyst/commits/v2.10.1/ push 16 Nov 57736 12:59AM UTC Krinkle github
90.45
18308995170 main Build: Update hydra-link-checker for tightened rate limits push 30 Oct 57736 10:34PM UTC Krinkle github
90.45
18307485275 main Docs: Import link posts * https://fosstodon.org/@qunit * https://twitter.com/qunitjs * https://bsky.app/profile/qunitjs.com push 19 Sep 57736 11:07AM UTC Krinkle github
90.45
18250595875 main Docs: Fix links in imported posts Follows-up 331e0e7f70. push 04 Feb 57730 03:29AM UTC Krinkle github
90.45
18249717200 main Docs: Move migration guide down on `assert.expect()` page It was a bit too prominent, making it seem like it might be about the method in general rather than just when used with `assert.step()`. push 01 Dec 57729 02:00PM UTC Krinkle github
90.45
18249443540 main Docs: Fix grammar in 2025-stacktrace post, update assert.throws() push 14 Nov 57729 12:03AM UTC Krinkle github
90.45
14563096078 main Docs: New blogpost "Test lifecycle diagram" push 04 Aug 57272 09:48PM UTC Krinkle github
90.45
14562142272 main Docs: Add "Sharing hooks" example to Test lifecycle Ref https://stackoverflow.com/a/79571790/319266 push 03 May 57272 11:56AM UTC Krinkle github
90.45
14545098983 main Docs: Fix typo in lifecycle.md push 13 Nov 57267 01:01AM UTC Krinkle github
90.45
See All Builds (3211)
  • Repo on GitHub
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc