We've been using magellan to parallelize our nightwatch runs on Saucelabs. After bumping the version of saucelabs executor to 4.10.0 from 1.0.5, we noticed that failing runs were no longer exiting with a status code of 1 to indicate a failure. This meant that failed test runs were actually reporting as successful in our buildkite pipelines, which rely on this exit code being accurate.
Here is example output running a simple magellan command with a test that is designed to fail. I should also note that we are not actually using the saucelabs executor to define the browser but are rather using a locally-defined browser from our nightwatch.json file.
Here is the browser definition in nightwatch.json:
Hi there,
We've been using magellan to parallelize our nightwatch runs on Saucelabs. After bumping the version of saucelabs executor to 4.10.0 from 1.0.5, we noticed that failing runs were no longer exiting with a status code of 1 to indicate a failure. This meant that failed test runs were actually reporting as successful in our buildkite pipelines, which rely on this exit code being accurate.
Here is example output running a simple magellan command with a test that is designed to fail. I should also note that we are not actually using the saucelabs executor to define the browser but are rather using a locally-defined browser from our nightwatch.json file.
Here is the browser definition in nightwatch.json:
And this is the command I'm using to run the test:
With Saucelabs executor at 1.0.5
With Saucelabs executor at 4.10.0