tag:blogger.com,1999:blog-231283624605213780.post258872815949888786..comments2021-11-17T13:39:43.457-08:00Comments on GOSHtastic - Game shows, Options, Software, & Hardware!: Angular + Protractor + Sauce Connect, launched from Gulp, all behind a corporate firewall!GOSHtastic - Game shows, Options, Software, and Hardwarehttp://www.blogger.com/profile/16590401405065119990noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-231283624605213780.post-50355592633500312892015-05-01T09:38:59.659-07:002015-05-01T09:38:59.659-07:00Hi Jeff,
In exports.config, try setting the “sauc...Hi Jeff,<br /><br />In exports.config, try setting the “sauceSeleniumAddress" parameter to “:/wd/hub” (remember that this was localhost:4445 with a local sc instance), and then also set the “tunnelIdentifier” parameter to the name of the tunnel as specified when that instance of sc was launched. Hopefully that system’s administrator can tell you what it is if you can’t see it from the Sauce Labs control panel in “Account" -> "Active Tunnels.” If this doesn’t do the trick, try just tunnelIdentifier.<br /><br />The other thing is if your company has multiple Sauce Labs accounts that are supposed to share the same tunnel, you need to ditch the “sauceSeleniumAddress” and “tunnelIdentifier” fields and simply use the “parent-tunnel” field inside the “capabilities” or “multiCapabilities” object in your configuration data structure. The contents of parentTunnel should be the username of the parent account who owns the tunnel, as a string (see this link https://docs.saucelabs.com/reference/sauce-connect/#can-i-reuse-a-tunnel-between-multiple-accounts-).<br /><br />Note that to also get this working through a proxy, you should install the Node module http-proxy-agent and add the following to your node-modules/selenium-webdriver/http/index.js file:<br /><br />var sendRequest = function(options, callback, opt_data) {<br />+ var HttpProxyAgent = require('http-proxy-agent’);<br />+ var proxy = process.env.http_proxy || ‘’;<br />+ var agent = new HttpProxyAgent(proxy);<br /><br />+ options.agent = agent;<br /><br /> var request = http.request(options, function(response) {<br /><br />And then for accessing HTTPS sites, modify node_modules/saucelabs/lib/SauceLabs.js to contain:<br /><br />- base: ‘rest/v1'<br />+ base: '/rest/v1/‘,<br />+ port: '443'<br /><br />Hopefully one of these solutions works for you! P.S. I guess it's time for me to turn on comment integration in G+ so I actually see these in the future. :-PGOSHtastic - Game shows, Options, Software, and Hardwarehttps://www.blogger.com/profile/16590401405065119990noreply@blogger.comtag:blogger.com,1999:blog-231283624605213780.post-2364234553367586502015-04-23T10:43:59.572-07:002015-04-23T10:43:59.572-07:00Hi Stephen,
Have you tried using Protractor when ...Hi Stephen,<br /><br />Have you tried using Protractor when Sauce Connect is running on a different server (Not Localhost). My company has it on a central server so we can use firewall controls to restrict access. I've tried and tried, but cannot get it to work. Any advice?Jeffhttps://www.blogger.com/profile/17004212388903915950noreply@blogger.comtag:blogger.com,1999:blog-231283624605213780.post-29468406834661819402015-04-17T14:47:02.036-07:002015-04-17T14:47:02.036-07:00Sergii, looks like your pull request was merged; t...Sergii, looks like your pull request was merged; thanks for handling that! It's easy enough to use the "agent" from exports.config inside a Protractor test, correct?GOSHtastic - Game shows, Options, Software, and Hardwarehttps://www.blogger.com/profile/16590401405065119990noreply@blogger.comtag:blogger.com,1999:blog-231283624605213780.post-91596959493880861102015-04-14T02:12:45.666-07:002015-04-14T02:12:45.666-07:00Hi,
I made a PR to the protractor repository and ...Hi,<br /><br />I made a PR to the protractor repository and hopefully it will be merged soon: https://github.com/angular/protractor/pull/2040Anonymoushttps://www.blogger.com/profile/00163196932065223859noreply@blogger.com