shuup / shuup / 3175

92%

Pull #1171

travis-ci

Fix browser tests

* Update all related packages
* Run admin and front tests in separate builds to prevent
build time to rise
* Do not run notify tests with Travis since not business
critical
* Split few tests to avoid individual tests take too much
time. This caused issues with Travis.

There are some problem spots which get fixed with some extra
waiting. Also it seems to be good practice to initialize
database before initializing tests, otherwise there might
be some random database locks happening.

There is still few inconcistency issues with Travis so
keep Travis still disabled until those are fixed.

Refs EE-240

6207 of 8482 branches covered (73.18%)

28655 of 32678 relevant lines covered (87.69%)

4.38 hits per line