This repository has been archived by the owner on Aug 15, 2019. It is now read-only.
Use karma's dots reporter instead of progress for travis log #1075
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DEV Using dots reporter in Travis cleans up the log (see this PR's log) and makes it easier to see the failed tests. Also switch BrowserStack tests to High Sierra (10.3.x)
Also since karma 3.x, the tests run in randomized order. This caused some tests to look flaky (e.g. some local storage tests were changing a global state and not resetting it properly). I'm reverting the order of tests to a non-random behavior by adding the following to karma.conf.js
We should do the same in other repos.
This change is