dmitryshindin / karma-jasmine-order-reporter

Karma plugin that reports Jasmine order seed that was used to randomize specs in Karma Runner

karma-jasmine-order-reporter

Reports Jasmine order seed that was used to randomize specs in Karma Runner

Use this plugin to get information about Jasmine generated seed. It reports seed info twice:

1. When Jasmine started:

JASMINE ORDER REPORTER: Started with seed 12345

2. When Jasmine finished spec run:

JASMINE ORDER REPORTER: Done with seed 12345

This plugin can be useful in scenarios when you have flaky tests, that are failing only on specific seeds. Also it will report seed on Jasmine start regardless of Karma or browser crash while tests run.

Installation

$ npm install karma-jasmine-order-reporter --save-dev

or

$ yarn add karma-jasmine-order-reporter --dev

Usage

Update your karma.conf.js file as follows:

module.exports = function(config) {
  config.set({
    // code omitted for brevity
    plugins: [
      // other Karma Plugins
      'karma-jasmine-order-reporter' or `require('karma-jasmine-order-reporter')`
    ],
    reporters: [
      // other Karma Reporters
      'jasmine-order'
    ]
  });
};

License

MIT Licensed

karma-jasmine-order-reporter's Issues

Duplicate logging emitted on start/end

Hi,

Thanks for a nice Karma plugin. When enabling this, I get duplicate entries logged on start and end of the test run though:

Chrome Headless 89.0.4389.114 (Linux x86_64) JASMINE ORDER REPORTER LOG: Started with seed 77398
Chrome Headless 89.0.4389.114 (Linux x86_64) JASMINE ORDER REPORTER: Started with seed 77398

[...]

JASMINE ORDER REPORTER LOG: Done with seed 77398
JASMINE ORDER REPORTER: Done with seed 77398

The first and third entries are coloured and the others are not. Is there any way to get rid of that extra logging? We run these tests with logLevel: config.LOG_INFO and with HeadlessChrome as the browser. Can provide more details about our config if needed.

Duplicate logging when used with "dots" reporter

We're seeing the same as #3 but for every log line when using the dots reporter, I wonder if blanking out the logging function like:

https://github.com/angular/angular-cli/pull/9529/files

would fix it?