jestjs/jest

[Bug]: shard option and global coverageThreshold config

Open

#12,751 建立於 2022年4月26日

在 GitHub 查看
 (29 留言) (49 反應) (0 負責人)TypeScript (45,361 star) (6,653 fork)batch import
:bug: BugHelp WantedPinned

描述

Version

28.0.1

Steps to reproduce

Run tests with the shard option and have coverageThreshold defined in the config with some global values.

Expected behavior

The global values should only be tested against tests who ran in the given shard

Actual behavior

the global values are used for all tests, even those who don't run in the same shard

Additional context

I'm actually not 100% sure about the right behavior to have here. But if we set some global coverage threshold, those won't be met because only a subset of tests run on each shard. All others are considered 0

Environment

System:
    OS: macOS 11.6.4
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
  Binaries:
    Node: 16.14.1 - ~/.volta/tools/image/node/16.14.1/bin/node
    npm: 8.5.0 - ~/.volta/tools/image/node/16.14.1/bin/npm
  npmPackages:
    jest: ^28.0.1 => 28.0.1

貢獻者指南

技術棧
typescriptjavascript
領域
testing
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Familiarity with JestKnowledge of code coverageUnderstanding of test sharding
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
The bug pertains to how global coverage thresholds interact with test sharding. The fix likely requires modifying how Jest aggregates coverage across shards. Relevant files include packages/jest core/src/runJest.ts or packages/jest reporters/src/CoverageReporter.ts. Review the issue comments for further clarification on expected behavior, particularly any maintainer input. Also examine how thresholds are currently applied and where shard information is known.