Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Example testling test fails with unhandled error

See original GitHub issue

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

Issue Analytics

State:
Created 10 years ago
Comments:15 (4 by maintainers)

Top GitHub Comments

2reactions

shapeshedcommented, Jan 15, 2020

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

2reactions

gsfcommented, Jun 28, 2014

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.