-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some info from failed spec is lost (v4.0.0) #34
Comments
Fixed in version |
Actually no, this is an issue with v4.0.0. Read it carefully. |
Sorry for such a delay. Do you have sample code I can run to reproduce? |
Sorry for such a delay as well :) I haven’t run into the issue again until today. To reproduce: git clone [email protected]:studio-b12/doxie.append
cd doxie.append
git checkout 324619f
npm install; npm test Raw output from tape:
Output from tap-spec (the And here’s the same output live on travis: https://travis-ci.org/studio-b12/doxie.append/jobs/71742577 |
Until scottcorgan/tap-spec#34 is resolved
It’s fine with v2 by the way: git checkout b3dba33
npm install; npm test Or just peek here: https://travis-ci.org/studio-b12/doxie.append/jobs/71743643 |
Until scottcorgan/tap-spec#34 is fixed.
Hi! I’ve just checked it with v4.1.0. The OP case is now ok, but the latter (#34 (comment)) still isn’t. The
To reproduce just paste everything up to and including the closing |
Hey @scottcorgan - @tomekwi's latest comment looks like its a duplicate issue of #28. (Its not properly passing the multiline YAML value - the stack value). I think if @tomekwi is happy that v4.1.0 fixes his original issue (undefined values not being reported), then this issue can be closed, as the stack issue is - as I say, a dupe of #28. |
Yeah, thanks for taking the time to look into this @keithamus! |
And thanks for the great tool @scottcorgan!!! |
Raw output from tape:
Here’s how tap-spec v2.x displayed that:
tap-spec v4.0.0 has better looks, but loses the
actual: …
part:It’d be great to have it back :)
The text was updated successfully, but these errors were encountered: