Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Karma outputs unspecified verbose info

See original GitHub issue

Since Node.js 12 with Firefox. This info is also outputted with test errors and it is very annoying.

Expected behaviour

Output only the specified data.

Actual behaviour

Browser {
  id: '96848431',
  fullName: 'Mozilla/5.0 (X11; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0',
  name: 'Firefox 66.0.0 (Linux 0.0.0)',
  lastResult: [BrowserResult],
  disconnectsCount: 0,
  activeSockets: [Array],
  noActivityTimeout: 100000,
  collection: [BrowserCollection],
  emitter: [Server],
  socket: [Socket],
  timer: [Object],
  disconnectDelay: 2000,
  log: [Logger],
  noActivityTimeoutId: Timeout {
    _idleTimeout: 100000,
    _idlePrev: [TimersList],
    _idleNext: [TimersList],
    _idleStart: 34033,
    _onTimeout: [Function],
    _timerArgs: undefined,
    _repeat: null,
    _destroyed: false,
    [Symbol(refed)]: true,
    [Symbol(asyncId)]: 28047,
    [Symbol(triggerId)]: 28045
  },
  pendingDisconnect: null,
  state: 'EXECUTING'
}

Environment Details

Karma version (output of karma --version): 4.1.0
Relevant part of your karma.config.js file: https://github.com/falsandtru/spica/blob/master/karma.conf.js

Steps to reproduce the behaviour

https://travis-ci.org/falsandtru/spica/jobs/524330826#L508-L537

Issue Analytics

State:
Created 4 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

kurklecommented, Jun 3, 2019

Its not actually dependent on plugin, last one of multiple plugins is output. Probably same issue as #3305 though (util.format dumping the object in node 12).

1reaction

johnjbartoncommented, Apr 25, 2019

That looks like the result of console.log(browser) though of course the variable name could differ. This is not part of karma-runner AFAICT. (Also your config is for chrome, not firefox). Consider installing locally and grep all files for “console.log(”

Top Results From Across the Web

Configuration File - Karma

Description: When Karma is watching the files for changes, it tries to batch multiple changes into a single run so that the test...

Karma's Progress Reporter Makes Failing Tests Unclear - GitLab

Karma's Progress Reporter Makes Failing Tests Unclear. The default reporter for karma, progress , shows one line of output for each test.

Karma runner console - output only failed tests - Stack Overflow

Karma v0.10 defaults to a reporters config of ['progress'] , which is likely causing your verbose output. You might like the 'dots' reporter ......

Angular-Karma-Test-Explorer/Bugs - Gitter

Karma configuration file, see link for more information ... client: { clearContext: false // leave Jasmine Spec Runner output visible in browser } ......

Problem with karma-coverage - Google Groups

Can you debug your jenkins test run - check if the source files are ... I get the xml report for tests output,...