Headless tests stopped working after mocha-phantomjs update

Hi there. New guy on the block. Been hacking with Meteor 1.3.1 past 2 weeks. Great platform.

Now, my unit tests were working great under CI. I had the following package versions…

practicalmeteor:chai@2.1.0_1
practicalmeteor:loglevel@1.2.0_2
practicalmeteor:mocha@2.1.0_8
practicalmeteor:mocha-core@0.1.4
practicalmeteor:sinon@1.14.1_2

dispatch:mocha-phantomjs@0.0.6
dispatch:phantomjs-tests@0.0.4

Now I get the following error running headless unit tests, after some package updates…

20160415-18:55:15.311(-4)? (STDERR) /Users/Starman/.meteor/packages/meteor-tool/.1.3.1.mkpqju++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:267
W20160415-18:55:15.311(-4)? (STDERR) throw(ex);
W20160415-18:55:15.311(-4)? (STDERR) ^
W20160415-18:55:15.311(-4)? (STDERR) TypeError: Object [object Object] has no method 'execFile’
W20160415-18:55:15.312(-4)? (STDERR) at startPhantom (packages/dispatch:phantomjs-tests/server.js:20:37)
W20160415-18:55:15.312(-4)? (STDERR) at Object.start (packages/dispatch:mocha-phantomjs/server.js:73:3)
W20160415-18:55:15.312(-4)? (STDERR) at nextSlot (packages/meteor.js:1022:27)
W20160415-18:55:15.312(-4)? (STDERR) at /private/var/folders/jd/ll7z42ts7yb5b78y_xlxzr_00000gn/T/meteor-test-runxujpj9/.meteor/local/build/programs/server/boot.js:290:5

Can’t pinpoint the cause of the update (other package? non-deterministic optimizing dep mgmt?) but, now I am with the following…

practicalmeteor:chai@2.1.0_1
practicalmeteor:loglevel@1.2.0_2
practicalmeteor:mocha@2.4.5_1
practicalmeteor:mocha-core@0.1.4
practicalmeteor:sinon@1.14.1_2

dispatch:mocha-core@0.0.1
dispatch:mocha-phantomjs@0.0.8
dispatch:phantomjs-tests@0.0.4

Just saw that Meteor 1.3.2 is out while writing this. I’ll give it a try. But, any idea about this error?

Also, what are the best practices around shrinkwrap or shrinkpack to get some stability when I get a stable setup?

Thank you for any help offered.

Remy

OK, upgrading Meteor to 1.3.2.1 solved this for me. I was never able to find the root cause though. Too bad.

Remy