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

{folder name} is not a test file #2231

Closed
tony-kerz opened this issue Aug 28, 2019 · 1 comment
Closed

{folder name} is not a test file #2231

tony-kerz opened this issue Aug 28, 2019 · 1 comment

Comments

@tony-kerz
Copy link

bash-4.4$ node -e "var os=require('os');console.log('Node.js ' + process.version + '\n' + os.platform() + ' ' + os.release())"
Node.js v10.16.3
darwin 18.6.0
bash-4.4$ npx ava --version
2.3.0
bash-4.4$ find test
test
test/ava
test/ava/test.js
bash-4.4$ npx ava


  1 test passed
bash-4.4$ npx ava test

✖ test is not a test file.

pre 2.x release i used to be able to specify:

ava {folder name}

and ava would recurse down finding tests and executing them, but now, it chokes, apparently thinking i'm trying to feed it a specific test file...?

@novemberborn
Copy link
Member

Yes, this behavior changed in v2. You now need to provide file paths. Luckily the default file selection has also improved so you may be able to run npx ava itself. Or else you could use a glob pattern with your shell, e.g. npx ava folder/**/test/*.js.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants