Uh oh!
There was an error while loading. Please reload this page.
Add more browser testing with Sauce Labs. - #2
Conversation
| sauceUser: process.env.SAUCE_USERNAME, | ||
| sauceKey: process.env.SAUCE_ACCESS_KEY, | ||
| directConnect: false, |
There was a problem hiding this comment.
Instead of trying to override an existing with an Object.assign, could we instead do something like:
var defaultConfig = require('./protractor.conf.js').config;
defaultConfig.directConnect = undefined;
defaultConfig.seleniumAddress = undefined;
defaultConfig.sauceUser
...
exports.config = defaultConfig;
There was a problem hiding this comment.
Also, defaultConfig.capabilities = undefined to get rid of the warning
There was a problem hiding this comment.
Turns out the problem was I was using an old Sauce Labs account, which didn't have any VM minutes for automated testing. Instead of throwing an error, Sauce would just hang forever waiting to launch.
Also, this uncovered a bug in Protractor. The way 'beforeLaunch' is used to set up ts-node doesn't actually work with multiCapabilities, because of the way we fork in the launcher. I suspect that if you used test sharding, that would also break.
4953489 to
e9c713aCompareThere seems to be an issue with 'beforeLaunch' and multicapabilities that breaks ts-node when launching.
e9c713a to
d97b02fCompare
Here's a simple example of one way to add support for testing on Sauce Labs. No need to actually merge this, it's just intended as an example.