Skip to content
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

--tap option does not work when used in combination with --browser #39

Open
aghassemi opened this issue Sep 23, 2014 · 2 comments
Open

Comments

@aghassemi
Copy link
Contributor

--tap works fine in node mode but has no effect when I run with --browser, I just get the regular "x passed assertions" instead of the tap output on stdout.

It would be awesome to get the raw tap output without any extras like the browser version, etc.. on stdout so test results can be interpreted by CI systems.

@azer
Copy link
Owner

azer commented Sep 23, 2014

Good idea, could you give an example of the output you expect ?

@aghassemi
Copy link
Contributor Author

I think the exact output that is generated by --tap option when used without --browser would be perfect. so when running

prova test.js --tap --browser --quit

I would like to see

TAP version 13
# test 1
ok 1 (unnamed assert)
# test 2
ok 2 (unnamed assert)

1..2
# tests 2
# pass  2

# ok

instead of

 prova:browser Visit http://0.0.0.0:7559 with a browser to start running the tests. +0ms

  2 passed assertions.
  Browser: Chrome v37 Engine: WebKit v537.36 OS: Linux vx86_64

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants