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

Having browser send down raw TAP output as well #42

Closed
wants to merge 3 commits into from

Conversation

aghassemi
Copy link
Contributor

Fixes #39 by allowing browser to send down raw TAP output so --tap can now work with --browser.

@aghassemi
Copy link
Contributor Author

Calling tape.createStream() twice as I have in this PR seems to have a side-effect where for the very first test in the suite, the state of whether it has ended or not is ignored making t.plan(x) not work properly in the first test. Probably related to how tape dequeues on every createStream() call. I am closing this PR until I find a solution either here or in tape for this problem.

@aghassemi aghassemi closed this Oct 1, 2014
…ice creating weird side-effects. For now accesssing the private stream directly. Bug to be filed with TAPE
@aghassemi aghassemi reopened this Oct 1, 2014
@aghassemi
Copy link
Contributor Author

Found a work-around for the tape behavior where calling createStream() more than once causes weird side-effects on the very first test in the suite. The work-around is not ideal as it accesses private tape variables however.

@aghassemi
Copy link
Contributor Author

tape-testing/tape#105 tape.

@aghassemi aghassemi mentioned this pull request Oct 2, 2014
@aghassemi
Copy link
Contributor Author

Closing in favour of #45

@aghassemi aghassemi closed this Oct 2, 2014
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 this pull request may close these issues.

--tap option does not work when used in combination with --browser
1 participant