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

What should be the default specifier when htest is ran with no arguments? #20

Open
LeaVerou opened this issue Mar 16, 2024 · 0 comments

Comments

@LeaVerou
Copy link
Owner

Currently if the htest command is used with no arguments, it defaults to the CWD, which is not super useful.
Perhaps it would be more useful to default to test? Or test if it exists and the CWD if not?

From a quick look, it appears that there is no established convention. Some testing frameworks to test (e.g. Mocha), others to many different patterns (e.g. Jest, AVA), others to CWD, and others don't have a default at all.

However, given how hTest is structured, with tests hierarchically importing other tests, we probably wouldn't want to do something like **/test/**.js because then you'd be importing the same test multiple times (e.g. once by itself, and then once via the index.js that imports it. Perhaps something like **/test/index.js, **/tests/index.js might be a good default?

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

1 participant