testling: Example testling test fails with unhandled error

The example test in ./example fails with an unhandled error.

Setup

node -v
v0.10.25
npm -v 
1.3.23
npm install -g testling # installs 1.5.9
npm install -g browserify # install 3.23.1
git clone git@github.com:substack/testling.git
cd testling && npm install

Test

browserify example/test.js | testling                                                                       

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:988:11)
    at Process.ChildProcess._handle.onexit (child_process.js:779:34)

Expected results are a the output in the README

About this issue

  • Original URL
  • State: closed
  • Created 10 years ago
  • Comments: 15

Most upvoted comments

Not resolved but the ticket has been open for 4.5 years. If you would like to reopen please do so.

Confirmed on Arch Linux as well, where a pacman -S xorg-server-xvfb allows the command to run.

Should xvfb be listed as a requirement in the README? Or is there a way to fork out to the browser without it? Note that without xvfb, testling -u works (as has been mentioned), as does testling -x chromium.

I’ve only taken over maintaining the package for a few weeks 😃 I’ll get to it.