This repository has been archived by the owner on Oct 30, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 8
Mocha support in the runner #299
Labels
enhancement
New feature or request
Comments
Dropping this here to track progress! TODO:
|
This was referenced Feb 12, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, unmock hardcodes Jest error catching in the runner, which means that the runner will not work in mocha and other frameworks.
It would be great if the runner had conditionals for different frameworks, which would require testing different test failure cases for different packages and handling them in a similar manner.
The ugly thing about the way we do it is that we catch a
JestAssertionError
and treat that as the runner failing.JestAssertionError
is an internal, undocumented way thatjest
causes tests to fail, so essentially we are creating a dependency on an internal API that could change in subsequent versions. It would be nice to address that to, and part of that could be asking the jest team to exposeJestAssertionError
in their external API so that it becomes a bit more sticky and less subject to change.The text was updated successfully, but these errors were encountered: