You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the parentheses in the path that make up the <rootDir> later passed to Jest's testMatch option by create-react-app's config are being interpreted by Jest as grouping characters. I've filed this as an issue with Jest jestjs/jest#4838 as well.
The text was updated successfully, but these errors were encountered:
If escaping is an option and can be done reliably, then that would be great. However, I'm not sure it is an option. I don't know how things work pre-eject, but post-eject, the jest config section of package.json will include the <rootDir> template variable in the values of testMatch. At that point, I don't believe that there would be anything that could be done to tests to run.
Is this a bug report?
Yes
Can you also reproduce the problem with npm 4.x?
Yes
Which terms did you search for in User Guide?
Environment
node -v
: v6.10.3npm -v
: v3.10.10yarn --version
(if you use Yarn): N/Anpm ls react-scripts
(if you haven’t ejected): [email protected]Then, specify:
Steps to Reproduce
mkdir with-\(parens\)
cd with-\(parens\)
create-react-app parens
cd parens
npm install
npm test
Expected Behavior
The tests in
src/app.test.js
should be run.Actual Behavior
A message about no tests being found will be shown.
Reproducible Demo
https://github.com/rimunroe/create-react-app-parens-in-test-path
It looks like the parentheses in the path that make up the
<rootDir>
later passed to Jest'stestMatch
option by create-react-app's config are being interpreted by Jest as grouping characters. I've filed this as an issue with Jest jestjs/jest#4838 as well.The text was updated successfully, but these errors were encountered: