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.

How to debug coverage source remap?

See original GitHub issue

I have my repo which I use ts-jest@0.1.10 with testResultsProcessor . I expected to get a better coverage and better debug-ability but nothing changed.

How do I debug the coverage code?

Issue Analytics

State:
Created 7 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

kwonojcommented, Oct 27, 2016

Also output in console is seems to be wrong - probably we have to investigate and fix it.

: I’ve investigated this and currently it’s not possible.

Jest writes coverage by delivering result to coverage reporter while collecting all test results. Console output for coverage happens at this time, before testresultprocessor being invoked. So its output is before-mapping, then coverage processor takes over try to remap its results.

It is because design of test result processor limitation, details at here : https://github.com/facebook/jest/issues/1907#issuecomment-254032111 unless there’s upstream changes to have specific hooks invoked to return mutated results back to jest or change behavior of current hooks, there isn’t way to achieve this.

0reactions

kulshekharcommented, Mar 18, 2017

Closing in favor of #101

Top Results From Across the Web

Change history for coverage.py - Read the Docs

A new debug option --debug=pathmap shows details of the remapping of paths that happens during combine due to the [paths] setting.

Issues between include and source with coverage.py

Try using: source = ['service', 'handler'].

LCOV - coverage.info - proxy/http/remap/RemapConfig.cc

Current view: top level - proxy/http/remap - RemapConfig.cc (source / functions) ... 0) { 120 0 : Debug("url_rewrite", "[process_filter_opt] Add per remap ......

Standardizing support for path remappings - hermetic builds ...

Introduce a new -file-prefix-map and make the existing -debug-prefix-map and -coverage-prefix-map aliases for -file-prefix-map. Any opinions/ ...

Test coverage visualization - GitLab Docs

The file you are viewing in the diff view is mentioned in the coverage report. · The source and filename nodes in the...