sth / karma-summary-reporter Goto Github PK

When running this reporter the result shows 'undefined' instead of the green checkmark or red x

describe('truthy-tests', () => {
  it('should be truthy', () => { expect(true).toBeTruthy(); });
  it('should be truthy', () => { expect(1).toBeTruthy(); });
});

Will output that 1 test cases successful in all browsers, despite it being two successful tests. It seems like only the first test is being reported, and if you have more they are disregarded.

The problem can be found here: https://github.com/sth/karma-summary-reporter/blob/master/index.js#L45

I use karma-summary-reporter together with karma-spec-reporter as you suggest. Unfortunately both the reporters print messages produced by console.log() calls in tests, therefore the console messages are duplicated.

Since your reporter is designed for summary, I request an option to mute the live process logs to solve the duplications.

I've left a pull request with a fix: #5

If something goes wrong you can only see the x that indicates a failed test. However, in other reporters a useful detail is printed, e.g. Expected false to be true if you have the following code (Jasmine):

it("should xxxxx", function () {
    expect(false).toBe(true);
});

If you have multiple expect statements e.g. inside a it(...) block then this gives the necessary information which of them failed.

I would like to see this in this reporter too.

When I upgraded my project's karma from 1.7.1 to 2.0.0, yarn reported the below warning. Any plans to upgrade this project's karma?

[email protected]" has incorrect peer dependency "karma@^1.2.0"

When I upgraded my project's karma from 2.x, yarn reported the below warning. The reporter seems to run fine with Karma 3 but there is a deprecated method warning.

[email protected]" has incorrect peer dependency "karma@^1.2.0 || 2.x"

Hey, I'm not sure if this is effectively a duplicate of the previous discussions about printing errors, but wanted to raise it because I had a tough time tracking down the cause.

I was using this on an angular project and if there's a typescript compilation error, the output from Karma is that it can't connect to Chrome. This makes sense in hindsight because the bundle wasn't able to be built but wasn't obvious since usually the TS errors are visible.

e.g. this is the output from a basic angular project (generated with ng new) with a small typescript error added. The second is with the summary reporter added.

Add an option to hide successful tests. Currently all test results are displayed always. In real test suits this isn't too useful.

Also add an additional option to ignore skipped tests.

Currently it just prints nothing, which doesn't make it very clear what's going on.