grunt-saucelabs
grunt-saucelabs copied to clipboard
axemclion
Grunt task for running all your browser tests using Sauce Labs
I recently upgraded to grunt-saucelabs 8.1.1 because the previous version (4.0.4) I was running seems to no longer be compatible with the Saucelabs endpoint. Unfortunately, I can no longer seem...
I have a number of a tests that I'm attempting to run via SauceLabs. At first one of the problems I had was when a single browser failed, any other...
Every now and then a test fails, and the retry logic attempts to DELETE the failing test. And every so often, the DELETE command _itself_ throws a 500 error. In...
Hi, I may be doing something wrong, but my jasmine based tests seem to not finish ever in internet explorer (until they timeout). They do in fact pass. Similarly when...
Example: https://travis-ci.org/twbs/bootstrap/jobs/18113236 ``` Tested http://127.0.0.1:3000/js/tests/index.html Platform: undefined >> Test Error Url undefined ``` (I had to use process of elimination to determine that this error was from OS X Chrome.)
Would be a big help to see a high-level summary of changes from version-to-version, especially when it comes to potentially breaking changes, or new APIs available. Thanks! _Edit_ Changed from...
I noticed that if you do not set the options.testname optional parameter, the output will include the proper operating system and browser (http://cl.ly/image/0e3I3D3Q3j19) while rendering the web-based output's 'session' column...
Every so often, this plugin fails on Travis, with no particular error: ``` Running "saucelabs-mocha:all" (saucelabs-mocha) task Verifying property saucelabs-mocha.all exists in config...OK File: [no files] => Connecting to Saucelabs...
Rather than repeating the host/port combination in the `urls` object, what about supporting the default Grunt multiTask files object. ``` js 'saucelabs-qunit': { all: { options: { host: 'http://localhost', port:...
When running `saucelabs-mocha` and SAUCE_ACCESS_KEY or SAUCE_USERNAME is not defined, the task fails without telling the user what is wrong: ``` $ grunt test Running "connect:server" (connect) task Started connect...
