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.