fixes bug with enableAutomock when automock is set to false#3624
Merged
cpojer merged 1 commit intojestjs:masterfrom May 23, 2017
Merged
Conversation
cpojer
pushed a commit
that referenced
this pull request
Jun 1, 2017
cpojer
pushed a commit
that referenced
this pull request
Jun 1, 2017
tushardhole
pushed a commit
to tushardhole/jest
that referenced
this pull request
Aug 21, 2017
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR causes the jest-runtime to build out the unmocked module list even when automock is set to false. This makes it possible for jest tests to enableAutomock and still keep certain modules unmocked as expected.
Test plan
yarn testcomes back clean.Plus, I added a test to verify the module was built. Running the test before the change fails. Running after passes.