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
FEI-3775: Configure wallaby #152
Conversation
|
"!<rootDir>/node_modules/", | ||
"!packages/**/node_modules/", | ||
"packages/*/src/**/*.js", | ||
"packages/*/src/**/*.jsx", |
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.
These files were being missed so I wasn't seeing any coverage squares in the gutter for the implementation file.
return { | ||
autoDetect: true, | ||
runMode: "onsave", | ||
trace: true, | ||
}; |
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.
I didn't really notice a difference overriding files
and tests
so I went with this minimal config.
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.
Wallaby picks up our Jest config so the files
and tests
will come from there and should be correct. You can see the derived settings if you use the override
key like we have in webapp and the console.log
the incoming filePatterns
or testPatterns
Summary:
I'm having troubles figuring out some of the test failures we're seeing in some of the widget tests so I thought I'd set up wallaby to help with continued debugging.
Issue: FEI-3775
Test plan: