errors running backstop commands

I’ve got a backstopjs (version 1.3.5)) running perfectly on my own machine, I can run the npm run reference command to generate the reference screenshots, and I can run the npm run test command without any issues, and it passes or fails when expected (e.g. fails successfully when I modify the CSS for a page)

So I’ve committed the backstop.json file, the bitmaps_reference folder, the bitmaps_test folder, (but only the compare.json file in here, not the test screenshots) and the capser_scripts directories in the backstop_data folder, to Git.

However, my colleagues are not able to run backstop. My colleague has pulled, and has the files/folders specified above. They have run npm install and have Backstop installed. When they try to run the npm run test command, they see this output:

npm run test

backstopjs@1.3.5 test fakepath\node_modules\backstopjs gulp test

BackstopJS Config loaded at location fakepath\backstop.json [11:14:55] Using gulpfile fakepath\node_modules\backstopjs\gulpfile.js [11:14:55] Starting ‘init’… [11:14:55] Finished ‘init’ after 82 μs [11:14:55] Starting ‘test’… gulp.run() has been deprecated. Use task dependencies or gulp.watch task triggering instead. [11:14:55] Starting ‘bless’… [11:14:55] Finished ‘bless’ after 5.05 ms

Running CasperJS with: [ ‘capture/genBitmaps.js’ ] [11:14:55] Finished ‘test’ after 16 ms

Testing script failed with code: 1

Looks like an error occured. You may want to try running $ npm run echo. This will echo the requested >test URL output to the console. You can check this output to verify that the file requested is indeed being received in the expected format.

They also see similar out if trying the npm run reference command.

Any ideas why this would work on my machine, but not work on an identical colleague’s machine?

[DigitalKrony]

EDIT Base python install was crap. Adding it into the PATH variables did the trick.

[garris]

@danwellman thanks for the update! Cheers. Garris