Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reporter: Recognise "Todo" tests from QUnit #140

Merged
merged 1 commit into from
Jun 6, 2021
Merged

Conversation

Krinkle
Copy link
Member

@Krinkle Krinkle commented Jun 6, 2021

This wasn't previously done because versions that support this feature also have a jsreporters-compatible event emitter built-in, but this isn't always used (such as in browserstack-runner). So for completion support it here as well just in case.

Ref qunitjs/qunit#1622.

This wasn't previously done because versions that support this feature
also have a jsreporters-compatible event emitter built-in, but this
isn't always used (such as in browserstack-runner). So for completion
support it here as well just in case.

Ref qunitjs/qunit#1622.
@Krinkle Krinkle merged commit 83bce59 into main Jun 6, 2021
@Krinkle Krinkle deleted the handle-qunit-todo branch June 6, 2021 20:45
Krinkle added a commit to qunitjs/qunit that referenced this pull request Jun 6, 2021
It is hard to believe, but we actually never had a `QUnit.todo()`
test as part of the main index.html test suite that we run in browsers.

There were secondary tests that only run in Headless Chromium via
grunt-contrib-qunit, and CLI tests, but none that we run cross browser.

In commit -- I added test/main/each.js to index.html, not realizing
it was the first such case, and this broke the CI build for all
browsers.

* js-reporters 2.1 adds support for QUnit.todo in the adapter
  so that it correctly emits the `runEnd` event to count these toward
  `testCounts.todo` instead of toward `testCounts.failed`.
  qunitjs/js-reporters#140.

* browserstack-runner 0.9.5-qunitjs.1 updates its copy of js-reporters
  to this version, and also updates its error formatter to not print
  details for error objects from non-failed tests.
Krinkle added a commit to qunitjs/qunit that referenced this pull request Jun 6, 2021
It is hard to believe, but we actually never had a `QUnit.todo()`
test as part of the main index.html test suite that we run in browsers.

There were secondary tests that only run in Headless Chromium via
grunt-contrib-qunit, and CLI tests, but none that we run cross browser.

In commit -- I added test/main/each.js to index.html, not realizing
it was the first such case, and this broke the CI build for all
browsers.

* js-reporters 2.1 adds support for QUnit.todo in the adapter
  so that it correctly emits the `runEnd` event to count these toward
  `testCounts.todo` instead of toward `testCounts.failed`.
  qunitjs/js-reporters#140.

* browserstack-runner 0.9.5-qunitjs.1 updates its copy of js-reporters
  to this version, and also updates its error formatter to not print
  details for error objects from non-failed tests.
Krinkle added a commit to qunitjs/qunit that referenced this pull request Jun 7, 2021
It is hard to believe, but we actually never had a `QUnit.todo()`
test as part of the main index.html test suite that we run in browsers.

There were secondary tests that only run in Headless Chromium via
grunt-contrib-qunit, and CLI tests, but none that we run cross browser.

In commit 47576c1 I added test/main/each.js to index.html, not
realizing it was the first such case, and this broke the CI build for
all browsers.

* js-reporters 2.1 adds support for QUnit.todo in the adapter
  so that it correctly emits the `runEnd` event to count these toward
  `testCounts.todo` instead of toward `testCounts.failed`.
  qunitjs/js-reporters#140.

* browserstack-runner 0.9.5-qunitjs.1 updates its copy of js-reporters
  to this version, and also updates its error formatter to not print
  details for error objects from non-failed tests.

Fixes #1622.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant