Skip to content

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

Open
@LeaVerou

Description

@LeaVerou

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions