[ljharb]

Entries in a module's scripts array may now be an object of the form { "script": "name", "skip": <condition> },
where skip accepts the same conditions as the top-level skip. Use this to skip posttest for resolve on win32.

ref #1182 (comment)

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.15%. Comparing base (147e8d8) to head (9fd5704).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1191      +/-   ##
==========================================
+ Coverage   96.11%   96.15%   +0.03%     
==========================================
  Files          29       29              
  Lines        2213     2235      +22     
==========================================
+ Hits         2127     2149      +22     
  Misses         86       86              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[BethGriggs]

I’m somewhat neutral on this as I am thinking about how often it would be used. Adding more mechanisms to skip tests adds complexity to understanding what’s being run and where. Do we think it’s worthwhile, even if it was just used for resolve? Just thinking it through.

[ljharb]

The way I think about it is, this maximizes test coverage while still allowing skips - otherwise, the script is skipped needlessly on N platforms when it only needs to be skipped on 1.