Skip to content

Releases: joeljeske/karma-parallel

v0.2.9

10 May 14:06
Compare
Choose a tag to compare

Fixes

  • Fixed a bug that would occur when using an aggregated reported like code-coverage or junit when using karma in watch mode, on subsequent test runs. Thanks @ben8p!

v0.2.6

10 May 13:47
Compare
Choose a tag to compare

New

  • Support running a top-level describe in all browser instances by inserting the prefix '[always]' at the beginning of the describe block's name.

v0.2.5

10 May 13:46
Compare
Choose a tag to compare

Fixes

  • afterAll was not being called in all specs, instead of just the shared specs.

v0.2.4

14 Feb 20:34
Compare
Choose a tag to compare

New

  • Support the aggregating results for the Junit reporter by default

v0.2.3

14 Feb 20:33
Compare
Choose a tag to compare

Fixes

  • Make sure mocha can properly focus tests (it.only)

v0.2.2

13 Feb 15:26
Compare
Choose a tag to compare

Fixes

  • Officially mark lodash v4 as a dependency to avoid version collisions

v0.2.1

13 Feb 15:25
Compare
Choose a tag to compare

Fixes

  • Ensure we exit properly for coverage reporters not implementing onExit (such as karma-istanbul-coverage-reporter)

v0.2.0

02 Feb 23:26
Compare
Choose a tag to compare

New

  • Supports Code Coverage! Tested with karma-coverage and karma-istanbul-coverage-reporter. Should work with any standard karma coverage reporter. Compliant with ng-cli projects.

Fixes

  • Fixes a bug where if CPU cores is 1, sharding would not work correctly.

v0.1.2

23 Jan 15:53
Compare
Choose a tag to compare

New

  • Support focusing a block or spec and get expected results in every browser instance
  • Ensures at least one spec per browser instance to ensure karma does not fail due to 0 tests

Breaking Changes

  • The 'parallel' framework must be the first framework in the list

v0.1.1

23 Jan 15:53
Compare
Choose a tag to compare

New

  • Add support for Mocha & Jasmine (previously only supported jasmine)