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

How to configure testem to run with xvfb? #537

Closed
toranb opened this issue Apr 10, 2015 · 6 comments
Closed

How to configure testem to run with xvfb? #537

toranb opened this issue Apr 10, 2015 · 6 comments
Labels

Comments

@toranb
Copy link

toranb commented Apr 10, 2015

It appears you can run testem w/ xvfb but what is the syntax to add this as a browser (testem.json) ?

xvfb-run testem -l firefox
xvfb-run testem -l chrome
@toranb
Copy link
Author

toranb commented Apr 10, 2015

It looks like I can run it manually from the cli like so

xvfb-run ember test

The (better) question is - can I configure launch_in_dev to do this without the prefix ?

@jayphelps
Copy link

@toranb are you running Jenkins? I ran into the same, solved by using https://wiki.jenkins-ci.org/display/JENKINS/Xvfb+Plugin so things are already setup and running

@toranb
Copy link
Author

toranb commented Apr 29, 2015

@jayphelps actually this was for local dev (fighting w/ phantomjs 1.x had me looking for headless alternatives as I'm doing tdd)

@jayphelps
Copy link

@toranb ah okay, linux guy. On local Mac, it works fine without needing to be headless. Any reason headless is requirement, or just don't want the window popping up? This isn't answering your issue, just curious.

I feel your pain though, same issues with phantomjs 1.x and lack of 2.0 for linux (jenkins).

@toranb
Copy link
Author

toranb commented Apr 29, 2015

Honestly I prefer to work in tmux/vim 100% of the time and having to use chrome to get output (for testem and ember-cli) is painful when you are pairing.

I still didn't have great luck w/ firefox headless like this but it was fun to play around w/ for local dev anyway. The biggest issue I have is how testem seems to swallow errors (or not show them via phantom/firefox when I have them configured). I'm often forced to open chrome just to find out an import blew up / some xhr had an error I didn't anticipate / etc

I'm still in search for a better solution for pure tdd / pairing / tmux / vim

@stefanpenner
Copy link
Contributor

Since chrome and FF support headless now, I think we don't need this anymore

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

No branches or pull requests

4 participants