Convention for naming spec files?

[assaf]

vows --watch assumes a convention for naming spec files, but generally it loads all the files it finds in spec/test, not just those with test-/spec- in their name.

If it filtered and only loaded files that follow the convention (when not giving explicit file names), it would be easier to work with vows and have unrelated JavaScript files in the spec directory.

My test suite includes JS files that should not be required (I load them separately), but are part of the data used for testing.

[cloudhead]

Fixing this.

[martypdx]

Any chance you can clearly document how the watch is intended to work? I have not been able to set it up in any useful manner.

[indexzero]

@cloudhead Is this fixed?

[silkentrance]

Watch mode looks out for either

coffee-script+javascript: specFileExt = /.(-|_).(js|coffee)$/;
or just javascript: specFileExt = /.(-|_).js$/;

Besides that, in bin/vows 381ff testing the specFileExt against file will always result in all tests being run with #337 being in place, heck 👯 - I will look into this ASAP.

AFAIC #337 will not break the existing behavior.

[mmhansen]

Looks like vows is picking up all files ending in .coffee or .js in the test or spec dir.
line 218

I'll put command line option for test file pattern in the feature list.
Everyone else has the ability to do this, so we should as well.