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
Comments
It looks like I can run it manually from the cli like so
The (better) question is - can I configure launch_in_dev to do this without the prefix ? |
@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 |
@jayphelps actually this was for local dev (fighting w/ phantomjs 1.x had me looking for headless alternatives as I'm doing tdd) |
@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). |
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 |
Since chrome and FF support headless now, I think we don't need this anymore |
It appears you can run testem w/ xvfb but what is the syntax to add this as a browser (testem.json) ?
The text was updated successfully, but these errors were encountered: