Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
30
contributors
Commits on Dec 28, 2018
Commits on Dec 31, 2018
Commits on Jan 1, 2019
-
-
chore: remove support for node 6 (#3246)
Set node 8 as minimal supported version. Closes #3151 BREAKING CHANGE: Drop Support for Node 6, to make it possible to use async/await in karma codebase.
Commits on Jan 4, 2019
Commits on Jan 18, 2019
-
fix(client): fix issue with loaded on safari 10 (#3252)
Safari 10 supports type=module but ignores nomodule which causes loaded() to execute twice. Fixes #3198
Commits on Jan 22, 2019
-
refactor(watcher): Make watcher injectable to support 3rd-party watch…
…ers (#3254) Over the years, there has been several suggestions to make the default watcher in Karma (that uses chokidar) dependency injectable so that Karma could work well with third-party watchers. Prior issues: 1. #1468 2. #2895 Candidate third-party watchers include: 1. Watcher for Broccoli 2. Watcher for Bazel 3. Watcher for Blaze (used internally at Google) This commit makes the change to allow other Karma plugins to specify the 'watcher' value in the di system and Karma would use the supplied watcher instead.
Commits on Jan 23, 2019
Commits on Jan 25, 2019
Commits on Feb 4, 2019
-
fix(launcher): Debug Child Processes exit signal (#3259)
The Child Processes Event: 'exit' has two parameters: code and signal (https://nodejs.org/api/child_process.html#child_process_event_exit). One of the two will always be non-null. This helps debugging cases where code is null.
Commits on Feb 13, 2019
-
fix(browser): allow updating total specs count (#3264)
* fix(browser): allow updating total specs count This change allows providing the total specs count after the tests have been started. The count will be updated in case it has been provided already. This can be uselful for some adapters where the total specs count can not be determined before starting the first test. fix onInfo test case, add new test for total update
Commits on Feb 19, 2019
Commits on Feb 20, 2019
-
fix: remove vulnerable dependency combine-lists (#3273)
Remove `combine-lists` as a dependency. Use `_.union` instead now. Fixes #3265
Commits on Feb 21, 2019
-
fix(filelist): correct logger name. (#3262)
Append the state of the browser if it gets lost.
Commits on Feb 28, 2019
Commits on Apr 5, 2019
Commits on Apr 12, 2019
-
fix(client): Enable loading different file types when running in pare…
…nt mode without iframe (#3289) * fix(client): Includes attributes like type in script tags when running in parent mode without iframe Back in #2542, a third option to run tests without iframe is implemented, mostly for lightweight browser. It only allows script element to be loaded dynamically. This fix includes file type like .css to be loaded properly. Fixes #3289
Commits on Apr 15, 2019
Commits on Apr 23, 2019
-
fix(server): Add error handler for webserver socket. (#3300)
Some times connection arrive, are given 404 responses, then disconnect, resulting in ECONNRESET errors on the socket. After we began monitoring UncaughtExceptions, these errors show up. Suppress them with a handler that ignores errors.
Commits on May 15, 2019
-
chore: update braces and chokidar to latest versions (#3307)
This results in a significant dependencies reduction. New version of chokidar also promises significant memory and performance improvements.
Commits on May 17, 2019
-
* chore: remove unused devDependencies * chore: update some devDependencies
Commits on May 23, 2019
-
chore(test): fix flaky test cases (#3314)
* fix(test): fixed flaky reconnecting test cc2eff2 introduced different behavior depending on whether socket reconnected or browser reconnected after reload. This lead to the reconnecting test being flaky as, depending on the timing, it will trigger second test run and result in unexpected output. * fix(test): remove broken monitor action for Cucumber The issue is that it resulted in the following sequence of actions: - run karma start - run karma run - and then instantly kill karma start command This resulted in flaky tests because the kill could race, resulting in incomplete output. In fact test was unnecessary complicated as it was enough to use runOut, which asserts output of the karma run command. * fix(test): guard from repeated executions of the karma run 'data' event handler may be called multiple times, which will result in multiple calls to karma run. To take it even further, its execution is delayed by setTimeout, which means that subsequent executions will run while next test scenario is in progress and may mess it up. To prevent this make sure that karma run is executed only once independently of how many time 'data' event is fired.
Commits on May 25, 2019
-
chore: revert back to Mocha 4 (#3313)
Mocha 5+ dropped support for IE 8 and IE 9. This leads to failing BrowserStack tests, so reverting back to version 4 until Karma decides to drop support for the mentioned browsers.
Commits on Jun 3, 2019
Commits on Jun 4, 2019
Commits on Jun 17, 2019
-
fix(reporter): format stack with 1-based column (#3325)
Columns in original stack are 1-based, but SourceMapConsumer.prototype.originalPositionFor(generatedPosition) accepts 0-based column and returns 0-based column too. This change converts columns from 1-based to 0-based forth and back. Closes #3324
Commits on Jul 1, 2019
Commits on Jul 12, 2019
-
fix(logging): Util inspect for logging the config. (#3332)
While flatten is accruate and works with circular data, it's too hard to read.
-
-
Commits on Jul 17, 2019
Commits on Jul 26, 2019
-
fix(test):
test:clientsilently failing on Travis (#3343)* fix(test): ensure that grunt test:client exits with non-zero code Apparently it is not enough to check `code`, because when process crashes `code` is set to `null` and `err` is passed instead. Example of failing tests, which didn't fail build: https://travis-ci.org/karma-runner/karma/jobs/537027667#L1046 * fix(test): adjust assertions to work in latest Chrome
Commits on Jul 30, 2019
-
* feat(runner): Return emitter that forwards server data Allow the consumer to decide whether to echo the runner progress or not. This might be the case when Karma.run() is called inside the same process/terminal as the server is running in (e.g. development servers). Fixes #2121, #2799 * feat(cli): Echo the runner progress event, don't echo in runner The CLI shall echo the progress, not the runner itself. Fixes #2121, #2799
-
Commits on Aug 13, 2019
Commits on Aug 21, 2019
-
feat(preprocessor): preprocessor_priority execution order. (#3303)
Between 3.x and 4.x we moved from combineLists to underscore.union in preprocessor. Apparently combineLists was incorrect: the order of preprocessing changed in some cases. Conceptually the order ought to depend upon the preprocessor, not the file. Implement config.preprocessor_priority['preprocessor-name'] = priority, higher means run earlier. Default priority is 0. Add back compat API for karma-browserify. Update docs.
Commits on Aug 26, 2019
-
fix(server): Simplify 'dom' inclusion. (#3356)
The karma preprocessor caches file content: no need to read it async in the server loop.
There are no files selected for viewing