You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The strict profile pins line, branch, and method coverage at 100%, but
left eval coverage off. On Ruby 3.2+, code reached through Kernel#eval
(notably ERB templates whose ERB#filename= has been set) gets routed
through the standard line and branch counters, so leaving the toggle
off meant strict was quietly lenient on the exact code paths most
likely to grow untested.
The profile now flips `enable_coverage :eval` on when the runtime
supports it. The guard avoids the "Coverage for eval is not available"
warning that would otherwise fire every time the profile loaded on
Ruby 3.1 (the project's minimum), keeping graceful degradation
consistent with how the existing branch and method clauses no-op on
JRuby. A new spec asserts the toggle matches `coverage_for_eval_supported?`
on whichever runtime the suite is running on, and the README's
"equivalent" example mirrors the new conditional.
0 commit comments