-
Notifications
You must be signed in to change notification settings - Fork 47.4k
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
Update to Jest 12. Codemod to new Jest APIs. #6620
Conversation
The unit test expectation matches what the browser does, so it looks like a jsdom bug. |
This is just the jest update, not the Jasmine 2 update correct? |
yes. Waiting for the jsdom fix here: jsdom/jsdom@236caae |
@cpojer updated the pull request. |
@cpojer updated the pull request. |
@cpojer updated the pull request. |
7b190ad
to
9fe5895
Compare
@@ -77,7 +77,7 @@ function writeTempConfig(callback) { | |||
function run(done, configPath) { | |||
grunt.log.writeln('running jest (this may take a while)'); | |||
|
|||
var args = ['--harmony', path.join('node_modules', 'jest-cli', 'bin', 'jest')]; | |||
var args = ['--harmony', path.join('node_modules', 'jest-cli', 'bin', 'jest'), '--runInBand']; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cpojer updated the pull request. |
Update to Jest 12. Codemod to new Jest APIs. (cherry picked from commit d07b554)
There is one test failing right now. Pretty sure it is because we updated to jsdom 8. Will look into this tomorrow unless anyone has some ideas – seems like the multiple defaultValues test is failing in ReactDOMSelect – is this a bug in React or jsdom?