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

Define test directory by command-line flag #290

Closed
h2non opened this issue Mar 4, 2015 · 5 comments
Closed

Define test directory by command-line flag #290

h2non opened this issue Mar 4, 2015 · 5 comments

Comments

@h2non
Copy link

h2non commented Mar 4, 2015

Configuration files are great, specially for branding benefits, but for most small libraries, creating a new file in the repository it's just an unnecessary boilerplate.

Could it would be possible to pass the test root directory via command flag? Or even inferring via file system the proper directory would be great!

I don't know why you have chosen using the __test__ directory by default, which is outside of the community conventions

@indigo0086
Copy link

would also like to know, I keep my tests next to the actual js files they are testing usually.

@cpojer
Copy link
Member

cpojer commented Mar 11, 2016

We won't be adding this as a command line flag, but we will be adding a config option in the future. This is tracked in separate issues. #10 and #637 for example.

@aaronabramov
Copy link
Contributor

@cpojer
Copy link
Member

cpojer commented Apr 14, 2016

@DmitriiAbramov the problem currently is that it only allows you to specify a directory. I'd like to deprecate this option and add a testPattern option where you can also make it a regex, for example to match "test.spec.js". Some people prefer having tests next to their files rather than a __tests__ folder. If you'd like to take this on, that would be great :)

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants