Skip to content
This repository has been archived by the owner on Dec 28, 2023. It is now read-only.

Expose 'pending' status #109

Closed
segrey opened this issue Aug 11, 2016 · 1 comment · Fixed by #122
Closed

Expose 'pending' status #109

segrey opened this issue Aug 11, 2016 · 1 comment · Fixed by #122

Comments

@segrey
Copy link

segrey commented Aug 11, 2016

Mocha has pending tests which are marked with test.pending boolean property. Currently, these tests are reported as skipped to karma reporters (https://github.com/karma-runner/karma-mocha/blob/v1.1.1/src/adapter.js#L110).
The problem is that karma-jasmine reports both pending and disabled (or non focused) tests as skipped too (corresponding issue karma-runner/karma-jasmine#129).

It'd be great if reporter could differentiate pending tests somehow. Luckily, pending tests from karma-jasmine and pending tests from karma-mocha are basically the same thing and there is no need to distinguish them in a reporter (I guess).

@maksimr maksimr self-assigned this Nov 7, 2016
@maksimr maksimr closed this as completed Nov 7, 2016
@maksimr maksimr reopened this Nov 7, 2016
karmarunnerbot pushed a commit that referenced this issue Apr 14, 2020
# [2.0.0](v1.3.0...v2.0.0) (2020-04-14)

### Features

* **ci:** enable semanitic-release ([5a5b6d5](5a5b6d5))
* Expose 'pending' status ([e847121](e847121)), closes [#109](#109)

* Update Node.js versions ([fd64f5b](fd64f5b))

### BREAKING CHANGES

* drop support for node 8
@karmarunnerbot
Copy link
Member

🎉 This issue has been resolved in version 2.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants