not able to run the coverage for one file #7427

nasreddineskandrani · 2018-11-29T03:44:29Z

🚀 Feature Proposal

coverage shows for full run but for specific files nothing or mixed

I want to be able to run with:

o option from jest menu
jest --watch --coverage STRING_FOR_REGEX_TESTS_SELECTION
jest --watch --coverage --runTestsByPath SPECIFIC_FILE_PATH

And have the coverage for the files impacted only.

Motivation

it's all about productivity.

1. Tech Debt of tests

When we work on tech debt of tests => it's generally one by one (file by file).
So I mostly run targeting the file i am working on. The run in watch mode is faster this way. I would like to see the coverage related to the current file i am targeting (should be faster to generate?)

2. Same thing apply for development of new features

Devs don't do TDD most of the time and do the test after. Testing files one by one is faster especially if you split between multiple developers the work.

this is a reality happening in a lot of companies.

Example

Jest version: "23.6.0"
jest config:

module.exports = {
  preset: 'jest-preset-angular',
  setupTestFrameworkScriptFile: '<rootDir>/src/setupJest.ts',
  roots: ['src/app'],
  moduleFileExtensions: ['ts', 'js']
};

in this repo branch:
(sorry i didn't clean i just commited the state since i am playing with jest to help in vscode-jest repo)
https://github.com/nasreddineskandrani/full-example-angular/tree/jest-playaround

clone the repo
yarn install

-- Example 1 Steps

yarn run testjest:watch -- --coverage
run all tests (the coverage is fine) and the coverage result is:
now use w then o (Press o to only run tests related to changed files.)
then you change the file src\app\game\game-a.service.spec.ts the condition true to false and vise versa
Resulting coverage (PROBLEM):

-- Example 2 Steps

when i run:
yarn run testjest:watch -- --coverage game-a.service.spec.ts
I get:

WHY HERO.SERVICE impacted here? setupJest.ts ....?

-- Example 3 Steps

when i run:
yarn run testjest:watch --coverage --runTestsByPath src/app/game/game-a.service.spec.ts
I get:

WHY HERO.SERVICE impacted here? setupJest.ts ....?

Result expected:

I want to be able to see only the coverage of the file i changed
I want to be able to see only the coverage of the file(s) i watch (with regex or path)
=> without doing any custom config since the file(s) impacted are known.

The text was updated successfully, but these errors were encountered:

rickhanlonii · 2018-11-29T10:02:49Z

hey @nasreddineskandrani, thanks for using Jest - this is not a bug, but it is a pretty good feature request

Can you update the description to use the feature request template?

nasreddineskandrani · 2018-11-29T14:07:12Z

done. waiting for feedback :)

rickhanlonii · 2018-11-29T14:16:57Z

Wow, awesome change thanks 👍

sslgeorge · 2019-03-11T13:02:18Z

Is anybody working on this right now?

SimenB · 2019-03-18T08:35:45Z

Nope, feel free to tackle it if you've got some time!

mwalkerpear · 2019-06-10T23:17:19Z

Doesn't this solve the issue?
--collectCoverageOnlyFrom

joelbarbosa · 2019-07-25T09:15:56Z

jest --coverage --collectCoverageFrom=path/to/your/file.js

falnos24865 · 2019-08-20T00:56:19Z

jest --coverage --collectCoverageFrom=path/to/your/file.js

This does not work for me, it runs a full test run regardless of what is specified - i.e. collectCoverageFrom does nothing.

joelbarbosa · 2019-08-20T07:44:59Z

jest --coverage --collectCoverageFrom=path/to/your/file.js

This does not work for me, it runs a full test run regardless of what is specified - i.e. collectCoverageFrom does nothing.

please, try this way.
example:

yarn jest app/components/search/tests/SearchPage.js --coverage --collectCoverageFrom=app/components/search/SearchPage.js

skube · 2019-09-06T17:45:41Z

While the test suite appears to run, I get a Failed to collect coverage from...

ghost · 2019-10-18T14:44:51Z

collectCoverageOnlyFrom works
collectCoverageFrom does not

eg. jest <suite I want to run> --coverage --collectCoverageOnlyFrom path/to/file.jsx

skube · 2019-10-18T19:17:24Z

Should this work with TypeScript too? I'm trying the following but it still craps out

yarn jest MyComponent --coverage --collectCoverageOnlyFrom=src/components/MyComponent/MyComponent.tsx

I get Jest encountered an unexpected token even though running yarn coverage works fine.

joelbarbosa · 2019-10-18T20:29:32Z

try this way.
yarn jest src/components/MyComponent/MyComponent.tsx --coverage --collectCoverageOnlyFrom=src/components/MyComponent/MyComponent.tsx

skube · 2019-10-18T20:45:35Z

Thanks, but same result

joelbarbosa · 2019-10-19T22:10:58Z

sorry what I meant was yarn jest src/components/MyComponent/test/MyComponent.tsx --coverage --collectCoverageOnlyFrom=src/components/MyComponent/MyComponent.tsx
the first path is for test folder

skube · 2019-10-25T21:07:16Z

My setup is a little different so for me, running:

yarn jest src/components/Button/Button.test.tsx --coverage --collectCoverageOnlyFrom=src/components/Button/Button.tsx

Still results in Jest encountered an unexpected token error — even though running yarn coverage works fine.

Example output:

   8 | `;
   9 |
> 10 | function StyledComponents({ children, ...rest }: ButtonProps): ReactElement {
     |                                                ^
  11 |   return <StyledButton {...rest}>{children}</StyledButton>;
  12 | }
  13 |
STACK: SyntaxError: /Users/skube/Code/my-app/src/components/Button/Button.tsx: Unexpected token, expected "," (10:47)

joelbarbosa · 2019-10-29T13:34:24Z

Maybe you need to see some jest config with typescript:
https://basarat.gitbooks.io/typescript/docs/testing/jest.html

lriostavira · 2020-05-30T00:02:21Z

any update on this? is there an option to collect coverage from tested files only?

ameliexu · 2020-07-21T12:18:54Z

try this way.
yarn jest src/components/MyComponent/MyComponent.tsx --coverage --collectCoverageOnlyFrom=src/components/MyComponent/MyComponent.tsx

is there any way to get coverage correctly with --coverage --changedSince=master?

ElVisPL · 2020-10-20T08:44:58Z

try this way.
yarn jest src/components/MyComponent/MyComponent.tsx --coverage --collectCoverageOnlyFrom=src/components/MyComponent/MyComponent.tsx

It works
In most use cases both paths are the same (tested files and files that we want coverage from).
It would be nice if for collectCoverageOnlyFrom without value it would take path of files that are actually tested

nasreddineskandrani · 2020-10-20T11:18:05Z

I close it since it's solved. Thanks

acostaf · 2020-11-13T11:18:04Z

Can you please open this again ? It is broken on jest 26.6.3
running this display the whole set of test files on the report including the untested files

yarn jest src/components/MyComponent/MyComponent.test.tsx --coverage --collectCoverageOnlyFrom=src/components/MyComponent/MyComponent.tsx

davidomarf · 2020-12-18T18:01:57Z

Hi!

I wanted to do this directly from the Jest CLI options, but since none worked, I did a workaround that may fit your use case.

I only wanted to know what was the coverage of the files I was writing tests for, and piping the output with grep was enough:

yarn jest myPattern | grep myPattern

This will log something like this:

PASS {path of a file that matched your pattern}
PASS {path of a file that matched your pattern}
 {path of one parent directory}                           |      100 |    83.33 |      100 |      100 |                   |
   {path of one of your files}                            |      100 |    83.33 |      100 |      100 |                24 |
   {path of one of your files}                            |      100 |    83.33 |      100 |      100 |               103 |
Jest: "global" coverage threshold for statements (x%) not met: y%
Jest: "global" coverage threshold for lines (x%) not met: y%
Jest: "global" coverage threshold for functions (x%) not met: y%

Test Suites: x passed, x total
Tests:       y passed, y total
Snapshots:   0 total
Time:        Xs
Ran all test suites matching /myPattern/i.

If a test fails it'll still display the expectation errors, only without colors.

github-actions · 2021-05-11T01:28:54Z

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

7rulnik mentioned this issue May 30, 2020

findRelatedTests + coverage doesn't match findRelatedTests + collectCoverageFrom #10083

Closed

nasreddineskandrani closed this as completed Oct 20, 2020

acostaf mentioned this issue Nov 13, 2020

not able to run the coverage for one file on jest 26.6.3 #10815

Closed

github-actions bot locked as resolved and limited conversation to collaborators May 11, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

not able to run the coverage for one file #7427

not able to run the coverage for one file #7427

nasreddineskandrani commented Nov 29, 2018 •

edited

Loading

rickhanlonii commented Nov 29, 2018

nasreddineskandrani commented Nov 29, 2018 •

edited

Loading

rickhanlonii commented Nov 29, 2018

sslgeorge commented Mar 11, 2019 •

edited

Loading

SimenB commented Mar 18, 2019

mwalkerpear commented Jun 10, 2019

joelbarbosa commented Jul 25, 2019

falnos24865 commented Aug 20, 2019

joelbarbosa commented Aug 20, 2019

skube commented Sep 6, 2019

ghost commented Oct 18, 2019

skube commented Oct 18, 2019

joelbarbosa commented Oct 18, 2019

skube commented Oct 18, 2019

joelbarbosa commented Oct 19, 2019 •

edited

Loading

skube commented Oct 25, 2019 •

edited

Loading

joelbarbosa commented Oct 29, 2019

lriostavira commented May 30, 2020

ameliexu commented Jul 21, 2020

ElVisPL commented Oct 20, 2020

nasreddineskandrani commented Oct 20, 2020 •

edited

Loading

acostaf commented Nov 13, 2020 •

edited

Loading

davidomarf commented Dec 18, 2020

github-actions bot commented May 11, 2021

not able to run the coverage for one file #7427

not able to run the coverage for one file #7427

Comments

nasreddineskandrani commented Nov 29, 2018 • edited Loading

🚀 Feature Proposal

Motivation

1. Tech Debt of tests

2. Same thing apply for development of new features

Example

-- Example 1 Steps

-- Example 2 Steps

-- Example 3 Steps

rickhanlonii commented Nov 29, 2018

nasreddineskandrani commented Nov 29, 2018 • edited Loading

rickhanlonii commented Nov 29, 2018

sslgeorge commented Mar 11, 2019 • edited Loading

SimenB commented Mar 18, 2019

mwalkerpear commented Jun 10, 2019

joelbarbosa commented Jul 25, 2019

falnos24865 commented Aug 20, 2019

joelbarbosa commented Aug 20, 2019

skube commented Sep 6, 2019

ghost commented Oct 18, 2019

skube commented Oct 18, 2019

joelbarbosa commented Oct 18, 2019

skube commented Oct 18, 2019

joelbarbosa commented Oct 19, 2019 • edited Loading

skube commented Oct 25, 2019 • edited Loading

joelbarbosa commented Oct 29, 2019

lriostavira commented May 30, 2020

ameliexu commented Jul 21, 2020

ElVisPL commented Oct 20, 2020

nasreddineskandrani commented Oct 20, 2020 • edited Loading

acostaf commented Nov 13, 2020 • edited Loading

davidomarf commented Dec 18, 2020

github-actions bot commented May 11, 2021

nasreddineskandrani commented Nov 29, 2018 •

edited

Loading

nasreddineskandrani commented Nov 29, 2018 •

edited

Loading

sslgeorge commented Mar 11, 2019 •

edited

Loading

joelbarbosa commented Oct 19, 2019 •

edited

Loading

skube commented Oct 25, 2019 •

edited

Loading

nasreddineskandrani commented Oct 20, 2020 •

edited

Loading

acostaf commented Nov 13, 2020 •

edited

Loading