Kristian asked the family to check WordPress 7.1.2. Run pinned rather than
against "latest", because latest drifts and then nobody knows which version a
green belonged to:
PHP 7.4 69 assertions, 0 failures "none from this plugin"
PHP 8.3 69 assertions, 0 failures "none from this plugin"
PHP 8.4 69 assertions, 0 failures "none from this plugin"
The container reported WordPress 7.1.2 and WooCommerce 11.1.2 on all three,
read out of the run rather than from the variable it was given. So there is no
problem with 7.1.2 here.
The findings were in the reporting, not the code.
The headers were stale: "Tested up to: 7.1" and "WC tested up to: 11.1.0"
against current 7.1.2 and 11.1.2. The WooCommerce one is the visible half — a
shop on 11.1.2 sees an untested warning on the WooCommerce status page, and on
this plugin that banner sits in front of somebody deciding whether to update a
discount engine.
And the suite said "All assertions passed" without a number, which is the exact
failure every other check here was fixed for. It now prints the count.
🔴 Then the floor for that count found a bigger hole than it was written for.
Putting it at the end of the smoke file does nothing: wp eval-file runs the
file in function scope, so a `return` partway through skips everything after
it, including the floor. Measured — truncating tests/smoke.php before the
shipping section ran two thirds of the assertions and ci/site-test.sh reported
GREEN.
A file cannot assert about its own early exit. ci/site-test.sh now captures the
output and checks the total against MIN_SITE_ASSERTIONS from outside, where an
early return cannot reach, and fails when the summary line is missing
altogether. The in-file floor stays for a short run that does reach the end.
Proven with the same fixture that exposed it: the truncated suite now exits 1
saying it printed no assertion total.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
