Skip to content
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.
base repository: karma-runner/karma Loading
base: v2.0.4
Choose a base ref
...
head repository: karma-runner/karma Loading
compare: v2.0.5
Choose a head ref
  • 10 commits
  • 20 files changed
  • 6 contributors

Commits on Jun 21, 2018

  1. Configuration menu
    Copy the full SHA
    7b66e18 View commit details
    Browse the repository at this point in the history

Commits on Jun 22, 2018

  1. Configuration menu
    Copy the full SHA
    ad820a1 View commit details
    Browse the repository at this point in the history

Commits on Jul 11, 2018

  1. Configuration menu
    Copy the full SHA
    850a90b View commit details
    Browse the repository at this point in the history
  2. fix: remove circular reference in Browser

    After migrating the the `browser.js` file to ES2015, the `Browser` class has now fields with circular references (like `emitter`),
    which breaks the Karma JSON reporters available starting with Karma 2.0.1.
    This commit removes the circular dependencies by adding a `toJSON()` method to the `Browser` class,
    which produces a similar result to the browser object before the migration.
    
    Fixes #3075
    cexbrayat authored and lusarz committed Jul 11, 2018
    Configuration menu
    Copy the full SHA
    518cb11 View commit details
    Browse the repository at this point in the history

Commits on Jul 12, 2018

  1. fix(middleware): Obey the Promise API.

    Rather than catching and discarding the error if no error handler is passed, let the promise package chain it. This allows use to have a .catch() follow the then().
    johnjbarton authored and lusarz committed Jul 12, 2018
    Configuration menu
    Copy the full SHA
    93ba05a View commit details
    Browse the repository at this point in the history

Commits on Jul 16, 2018

  1. Configuration menu
    Copy the full SHA
    a701732 View commit details
    Browse the repository at this point in the history

Commits on Jul 17, 2018

  1. Configuration menu
    Copy the full SHA
    7617279 View commit details
    Browse the repository at this point in the history

Commits on Jul 23, 2018

  1. fix(browser): ensure browser state is EXECUTING when tests start (#3074)

    * fix(browser): ensure browser state is EXECUTING when tests start
    
    Browser state is EXECUTING when it actually started to execute tests. This state change is triggered by client on actual tests execution start.
    
    Introduced an additional browser state CONFIGURING
    
    The CONFIGURING state means that the browser is not just CONNECTED for tests, but someone has requested tests execution (and provided a config file). But the provided config file is not yet processed, configuration is not applied or the tests execution is not yet started and we have not received the first event from the remote browser, so the browser object is not yet at EXECUTING state.
    
    Refactored browser state names: renamed READY -> CONNECTED
    
    Fixes #1640
    Alexei authored and johnjbarton committed Jul 23, 2018
    Configuration menu
    Copy the full SHA
    dc7265b View commit details
    Browse the repository at this point in the history

Commits on Jul 24, 2018

  1. Configuration menu
    Copy the full SHA
    02dc1f4 View commit details
    Browse the repository at this point in the history
  2. chore: release v2.0.5

    johnjbarton committed Jul 24, 2018
    Configuration menu
    Copy the full SHA
    0018947 View commit details
    Browse the repository at this point in the history
Loading