William Chargin 2d4acf62c5

test: check that JS tests describe their filenames (#802) ...

Summary:
Resolves #800. The newly added test takes about 2ms per file.

Test Plan:
Run `yarn sharness`, and note that it passes.

Then, edit (say) `src/main/test.js` to change the top-level describe
block from `"cli/main"` to something else, or to remove it altogether.
Re-run `yarn sharness` and note that it fails with a helpful message:

```
test_js_tests_have_top_level_describe_block_with_filename.t .. 1/?
not ok 31 - test file: cli/main.test.js
test_js_tests_describe_filename.t .. Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/65 subtests
```

wchargin-branch: describe-test

2018-09-06 20:44:59 -07:00

..

.gitignore

Add a .gitignore for Sharness (#673)

2018-08-15 16:31:00 -07:00

aggregate-results.sh

Add sharness for shell-based testing (#597)

2018-08-06 12:56:25 -07:00

dummy.t

Add sharness for shell-based testing (#597)

2018-08-06 12:56:25 -07:00

Makefile

Add sharness for shell-based testing (#597)

2018-08-06 12:56:25 -07:00

SHARNESS_LICENSE

Add sharness for shell-based testing (#597)

2018-08-06 12:56:25 -07:00

sharness.sh

Add sharness for shell-based testing (#597)

2018-08-06 12:56:25 -07:00

test_build_static_site.t

test: invoke yarn backend only once (#784)

2018-09-05 12:47:54 -07:00

test_js_tests_have_top_level_describe_block_with_filename.t

test: check that JS tests describe their filenames (#802)

2018-09-06 20:44:59 -07:00