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

build: Allow using jest as a test framework #1955

Merged
merged 2 commits into from
Mar 6, 2019

Conversation

RomainMuller
Copy link
Contributor

If a package's package.json file contains a jest entry (used for
configuring the behavior of jest), assert the package uses jest
instead of nodeunit as it's test harness (and fail if there are any
nodeunit tests - based on file name).

This is going to make it easier to migrate away from nodeunit.

If a package's `package.json` file contains a `jest` entry (used for
configuring the behavior of `jest`), assert the package uses `jest`
instead of `nodeunit` as it's test harness (and fail if there are any
`nodeunit` tests - based on file name).

This is going to make it easier to migrate away from `nodeunit`.
@RomainMuller RomainMuller requested a review from a team as a code owner March 5, 2019 16:28

if (useJest) {
if (testFiles.length > 0) {
throw new Error(`Jest is enabled, but ${testFiles.length} nodeunit tests were found!`);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So a package must be entirely jest or nodeunit to work?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. We could allow both but would have to merge coverage data & the likes, which is possible but ugly as heck. I don't need this right now so not getting into this... We can do that later if there is a real value to it.

@RomainMuller RomainMuller merged commit aa08b95 into master Mar 6, 2019
@RomainMuller RomainMuller deleted the rmuller/allow-using-jest branch March 6, 2019 08:28
@NGL321 NGL321 added the contribution/core This is a PR that came from AWS. label Sep 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution/core This is a PR that came from AWS.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants