Glob expansion in shell prevents running all intended tests

[Schoonology]

If you run teenytest test/**/*.js in a terminal, the shell will expand that glob automatically, and the argvOptions function will pull the first from that list to run. This is surprising, though there's a workaround: prevent shell expansion with single quotes: teenytest 'test/**/*.js'. This allows the prepare function to expand the glob as intended.

[Schoonology]

More throwing this here to keep track of it; it looks like more of a fix than I have time for this morning.

[searls]

Yes! (I believe the same is true for double-quoting in, at least, bash)

Is there an action to be taken in this issue?

[searls]

In general, IME, there's not much a CLI can do if the shell has expanded the arg before the receiving program runs and is provided ARGV, so I think this ticket is probably a no-op aside from scanning documentation?

[Schoonology]

Do we expect teenytest to take other kinds of positional arguments, or could we accept any number of files or patterns from argv? If we do that, it doesn't matter where expansion happens.

[searls]

Can you give an example of what ARGV looks like after your shell has expanded it? My understanding is it'll often just be the first match, as opposed to something like an array of lots of items.

To answer your question more directly: teenytest currently only supports a single pattern of test files. I'd love if it accepted multiple globs (and exclude patterns), though!

[Schoonology]

Instead of ['test/**/*.js'], you get an array: ['test/lib/parser.js', 'test/integration/index.js'].

[searls]

Cool, in that case "supporting multiple globs" should fix this on its own one would think

[searls]

Let's track this in #32