Summary 'No tests found'

[dszakallas]

>cat test
1..1
ok 1 Description
# tests 1
# pass 1
# fail 0
> cat test | node_modules/.bin/tap-spec
    ✔ Description


  ✖ No tests found

Why does tap-spec give this misleading summary?

[dszakallas]

The output is from mocha run with the tap reporter.

[scottcorgan]

Does it do the same thing when you using tap or tape?

Also, if you're using mocha, maybe try the spec reporter that comes with mocha. tap-spec is based off of that.

[dszakallas]

No, tape works alright.
The problem is that the test cases (describe blocks) don't print a diagnostic messages with their name, like tape tests do, so the problem is that the assertions are just there unorganized. The problem with the spec reporter is that I want to run test in child processes and pipe them back to the parent and this creates a complete mess with that reporter.

[scottcorgan]

Have you checked out ava? Runs tests in parallel

[dszakallas]

Currently mocha is the standard in my team, but for this project I eventually came to the decision to use it alongside with tape for these kind of tests, because of the TAP support. Test times is not yet of a concern in this project, if that's the major improvement in ava. Anyways, will check it out, thanks.

[scottcorgan]

Nice.

I started a follow up to tap-spec called @tap-format/spec. You can try that out if you'd like while this is looked into.

[matt-mcmahon]

I noticed this issue today, too, using Node v6.5.0, tape v4.6.0, and tape-spec v4.1.1.

I uploaded a minimal test case to my GitHub, the repo is here.

[scottcorgan]

@lostcreation, do you mind trying @tap-format/spec to see if you get the same error. It's the same kind of package, just better formatting. I've been meaning to add docs.

[matt-mcmahon]

Just tried it. @tap-format/spec works fine. I didn't see any problems with the test names that were tripping up tap-spec.

[scottcorgan]

@lostcreation I'd recommend using that package over this one. Eventually this one will be replaced by @tap-format/spec

[matt-mcmahon]

Good to know. Thanks, Scott!

[MegaArman]

Interestingly, I've found if my test have three or more words (ex: 'mov 1 test') I get this error. That's the only time I get it from what I've found. I'm using tape to test on centos7 (if that matters).

[drschwabe]

Had this problem too. Pinpointed it to having an integer in the name of test. Ie: test("Explode 3 apples") will cause this issue however test("Explode three apples") is AOK

[maxlutay]

Probably fix #60

[scottcorgan]

#60 has been merged. Can y'all confirm this is fixed now?

[scottcorgan]

Going to close this now as this is probably fixed now.