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
Testing: Actually invoke mocha instead of mocking it out #83
Comments
Merged
gabegorelick
added a commit
to gabegorelick/mocha-junit-reporter
that referenced
this issue
May 10, 2020
See michaelleeallen#83 for rationale. In the future, it would be useful if we could test against multiple versions of mocha instead of just the one listed in `devDependencies`. Closes michaelleeallen#83
I've taken a stab at this in #120. So far it's highlighted a few potential bugs and some issues where the tests were making assumptions that weren't true. |
gabegorelick
added a commit
to gabegorelick/mocha-junit-reporter
that referenced
this issue
May 10, 2020
See michaelleeallen#83 for rationale. In the future, it would be useful if we could test against multiple versions of mocha instead of just the one listed in `devDependencies`. Closes michaelleeallen#83
gabegorelick
added a commit
to gabegorelick/mocha-junit-reporter
that referenced
this issue
May 25, 2020
See michaelleeallen#83 for rationale. In the future, it would be useful if we could test against multiple versions of mocha instead of just the one listed in `devDependencies`. Closes michaelleeallen#83
gabegorelick
added a commit
to gabegorelick/mocha-junit-reporter
that referenced
this issue
May 25, 2020
See michaelleeallen#83 for rationale. In the future, it would be useful if we could test against multiple versions of mocha instead of just the one listed in `devDependencies`. Closes michaelleeallen#83
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It was suggested, and would be a good idea, to actually invoke mocha from inside our tests to ensure that we conform to mocha's API.
Ironically, it may be necessary to use a separate test driver in order to actually accomplish this.
The text was updated successfully, but these errors were encountered: