detro/jasmine-jsreporter — pull request #14 by hhelwich (2014-05-06 19:00:28+00:00)
Title: Workaround for sauce labs bug

There is a bug in sauce labs which avoids using it in combination with jasmine2/JSReporter2. I created a workaround for this bug as suggested by the saucelabs support. If you think this could be helpful to others you might put it in a branch (and delete it if this bug is fixed).

I created an issue on [saucelabs](http://support.saucelabs.com/requests/11376), but i think it is not public. This is the answer from saucelabs support:

> Right now, Sauce Labs stores all the test data passed to it by the Jasmine JSReporter, and stores it in the job data. Not originally intended for this, the custom-data field has a maximum length. It's possible that when running all 55 of your unit tests, the data is too large to fit our format and the data gets dropped. (That would be why removing some tests lets it work).

> We're working to fix this issue. In the meantime, there are two work-arounds:

> 1. Change the way you are using the Jasmine JSReporter to only report failing jobs. Most of the time, users aren't as concerned about recording all the data for tests which passed.

> 2. Break your test suite into two test pages. Doing it this way, the data is split into two chunks.

The workaround in this commit implements solution 1.