Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

coverageTheshold no work inside projects node of jest configre #6809

Closed
scott1028 opened this issue Aug 7, 2018 · 4 comments
Closed

coverageTheshold no work inside projects node of jest configre #6809

scott1028 opened this issue Aug 7, 2018 · 4 comments
Labels

Comments

@scott1028
Copy link

🐛 Bug Report

My jest version is v22.4.3, I found a issue possibly that if I put coverageThreshold inside projects node, it seem to no work correctly, but if I put it outside projects node, it will work correctly.

  • below is work for me when it acheive the threshold.
{
   ...
  "jest": {
     "coverageThreshold": {
        "global": {
          line: 50
        }
     }
  }
}
  • below is no work for me when it acheive the threshold. namely, It will not throw a error of threshold.
  "jest": {
    "projects": [
      {
        "displayName": "test",
        "coverageThreshold": {
          "global": {
            line: 50
          }
        }
      }
    ]
  }

To Reproduce

try to put your coverageThreshold inside the glob of projects.

  "jest": {
    "projects": [
      {
        "displayName": "test",
        "coverageThreshold": {
          "global": {
            line: 50
          }
        }
      }
    ]
  }

Expected behavior

It should throw a error of threshold too, even if I put it inside the projects of jest configure.

Link to repl or repo (highly encouraged)

Repl Project

  • You can run yarn test

Issues without a reproduction link are likely to stall.

Run npx envinfo --preset jest

Paste the results here:

npx: installed 1 in 2.818s

  System:
    OS: Linux 4.10 Linux Mint 18.3 (Sylvia)
    CPU: x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
  Binaries:
    Node: 8.11.3 - ~/.nvm/versions/node/v8.11.3/bin/node
    Yarn: 1.7.0 - ~/.nvm/versions/node/v8.11.3/bin/yarn
    npm: 5.6.0 - ~/.nvm/versions/node/v8.11.3/bin/npm
  npmPackages:
    jest: ^22.4.3 => 22.4.3 
@thymikee
Copy link
Collaborator

thymikee commented Jan 8, 2019

Might be connected to #5457

@github-actions
Copy link

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the Stale label Feb 25, 2022
@github-actions
Copy link

This issue was closed because it has been stalled for 7 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants