cross-browser-tests-runner / cross-browser-tests-runner

93%

push

travis-ci

SauceLabs tests through Native Runner

Included SauceLabs platform in Factory, Native Runner as needed.
Minimum changes were required in server with Platform abstraction
unchanged to support SauceLabs.

Functional tests for native runner now includes SauceLabs browsers in
the test conf it uses.

Changes in SauceLabs abstractions:
- The long wait for getting a job in Job abstraction led to the scene
  where test results are reported and native runner has not even got
  the jobs created. Had to remove this wait to make native runner work
  without any changes in its state machine.
- SauceLabs needs to support 'framework' capability, which is vital to
  support Jasmine 1. SauceLabs automatically stops the session in case
  the framework is set to any known one include "jasmine". This breaks
  native runner irrecoverably, as the session is deleted before the
  test data reaches native runner. The only solution is to use "custom" as
  framework for all tests using SauceLabs with Jasmine 1 (and possibly
  for all other frameworks unless some kind of hooks are possible to
  have to help native runner get test data back).

Samples:
- Browser yml and resultant cbtr json samples were added for SauceLabs.
  This includes both JS and Selenium, though Selenium testing is not yet
  available for SauceLabs.

Fixes:
- Scrutinizer fixes

6 of 9 branches covered (66.67%)

Branch coverage included in aggregate %.

48 of 49 relevant lines covered (97.96%)

1.31 hits per line