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
Use browser-launcher2. #6
Conversation
if this makes it work for you and still works for me, I'm all 👍 But, this doesn't pass the tests locally (either), so i'm investigating |
this is weird:
|
hm, weird. |
maybe different phantomjs versions? |
I actually couldn't get phantom to build at the time of this PR, due to yosemite changes. I'll look into this again soon |
Hi folks! 👋 I just tried using browser-run on an existing smokestack/tap suite and ran into this issue where the (chrome) browser window doesn't close. @juliangruber wanna kick off the travis build again and see if it passes? I tried locally but couldn't get tests to pass, even on the master branch: #102 |
@zeke the browser-run part seems to work for me: ∴ browser-date-formatter ((HEAD detached at c8558b6)) : ./node_modules/.bin/browserify test/index.js | browser-run
TAP version 13
# formatter
ok 1 uses a relative date string by default
not ok 2 supports custom strftime formats
---
operator: equal
expected: |-
'2016-04-07'
actual: |-
'2016-04-08'
at: Test.assert [as _assert] (http://localhost:52352/bundle.js:16353:17)
...
∴ browser-date-formatter ((HEAD detached at c8558b6)) : |
@zeke when I change the data assert, it finishes as it should: ∴ browser-date-formatter ((HEAD detached at c8558b6)) : ./node_modules/.bin/browserify test/index.js | browser-run
TAP version 13
# formatter
ok 1 uses a relative date string by default
ok 2 supports custom strftime formats
∴ browser-date-formatter ((HEAD detached at c8558b6)) : |
Closing this as slightly stale |
I've kinda just changed this with a quick fix to make it work for me, I'll probably just bundle it into my app if you don't accept this, so whatever. browser-launcher2 resolves the aforementioned browsers not closing on OS X issue.
browser-launcher2 (in yellow) also seems to have far more activity.