| Age | Commit message (Collapse) | Author |
|---|
|
Refactoring so that it's easier to use both SL/BS just depending on a global switch.
|
|
Instead of parallelization on a single Travis VM, we use two VMs.
- output is nicer (we don't have to buffer e2e tests and then show it at the end)
- you can easily see faster the result of unit tests (as it's basically a separate build)
We should also make sure we only do the necesary stuff (for install we don't need to do `grunt
package` for unit tests, we only need to generate the docs for e2e tests.
|
|
|
|
For some reason it's broken on SL.
|
|
I think we are pretty close to be able to use both.
The xhr-polling seems to be pretty stable, but I'm having problems with multiple SSH tunnels (on BS), so let's try to switch back to SL.
|
|
Switch the build to use BrowserStack instead of SauceLabs.
This also adds IE11 to our build.
|
|
This updates karma-sauce-launcher plugin, which fixes the issue we were having (it uses the latest version of wd).
This reverts 1c18c93be138c59b5c1b73cae99cc52383272146
|
|
I can't get it allocated on SauceLabs and so this is failing all the builds, making our Travis build useless.
I contacted folks from SL. Once we figure it out, I will revert this change.
|
|
|
|
Also instead of running everything in parallel, there are only two parallel tasks:
- e2e tests running in the background (only on Chrome)
- all the unit tests running sequentially
|
|
|
|
|
|
|
