wct Saucelabs configuration

436 views
Skip to first unread message

Jen Carlile

unread,
Feb 5, 2015, 5:59:58 PM2/5/15
to polym...@googlegroups.com
I'm trying to configure wct to run with Saucelabs, but my tests seem to only run locally.  Is there any further documentation or examples beyond the readme file on github related to saucelabs setup? my wct.conf.js file looks like (with username/access key removed):

module.exports = {
    verbose: true,
    testTimeout: 30 * 1000,
    suites: [
        'flux-*/*.test.html'
    ],
    plugins: {
        sauce: {
            "username": **my user name**,
            "access-key": **my access key**,
            "browser": "chrome",
            "browser-version": "39"
        }
    },

    root: 'client/components',
};

Thanks!
Jen

Jen Carlile

unread,
Feb 5, 2015, 6:38:21 PM2/5/15
to polym...@googlegroups.com
problem #1 identified -- "access-key" should be "accessKey" in config file
problem #2 identified -- needed to include remote: true as a configuration attribute.  

config file now looks like 
module.exports = {
    remote: true,
    verbose: true,
    testTimeout: 30 * 1000,
    suites: [
        'flux-*/*.test.html'
    ],
    plugins: {
        sauce: {
            "username": **my user name**,
            "accessKey": **my access key**
        }
    },

    root: 'client/components',
};

I'm still running into a problem specifying which OS and which browsers to run.  I've tried a combination of setting attributes in the sauce plugin, setting activeBrowsers, and setting browserOptions.  None seem to have the desired effect.  Any help/examples in this area is appreciated.

Thanks!

Jen Carlile

unread,
Feb 5, 2015, 8:24:51 PM2/5/15
to polym...@googlegroups.com
ok, solved.  Syntax for specifying remote browsers is different than for local browsers.  Also 'remote' was the wrong approach (it sets up test with all remote browsers).

Final config file looks like:
module.exports = {

    verbose: true,
    testTimeout: 30 * 1000,
    suites: [
        "flux-*/*.test.html"
    ],

    plugins: {
        sauce: {
            disabled: false,
            "username": **my user name**,
            "accessKey": **my access key**
            browsers: [
                "OS X 10.9/chrome@39",
                "OS X 10.9/firefox",
                "OS X 10.9/safari",
                "Windows 8.1/internet explorer",
                "Windows 8.1/chrome@39"
            ],
        }
    },

    root: 'client/components',

};

sirisha.a...@gmail.com

unread,
Jun 13, 2016, 12:57:54 PM6/13/16
to Polymer
Hi Jen,

I am getting the below error can you please suggest what might been missing:

Could not find WCT plugin named "sauce"


Your help is greatly appreciated.


Thanks




On Thursday, February 5, 2015 at 2:59:58 PM UTC-8, Jen Carlile wrote:

sree....@gmail.com

unread,
Oct 13, 2016, 12:57:23 PM10/13/16
to Polymer, sirisha.a...@gmail.com
I am getting the error Could not find WCT plugin named "sauce"
 could you help me how to fix the config file 
Reply all
Reply to author
Forward
0 new messages