Repository navigation
Description
Summary
89 of the 165 packages carrying a Makefile have no test target at all, so make helm-unit-tests never visits them. A green run therefore means "the opted-in half of the catalog passed", not "the catalog passed". The suite runner is honest about its boundary (skipping targetless packages is deliberate and pinned by its tests), but the boundary itself is wider than most readers of a green check assume.
Eight of the 89 are user-facing apps in packages/apps/: foundationdb, http-cache, mongodb, rabbitmq, redis, tcp-balancer, vpc, vpn. These ship to tenants with zero helm-unittest coverage: no render pin, no values-contract test, nothing that would redden on a template regression.
Counted with the runner's own detection gate over the current tree: 165 Makefiles, 76 with a working test target, 89 without.
Fix shape
Per chart, not per script: add a tests/ suite and a test: target to each chart, starting with the eight user-facing apps. Each one is a self-contained first contribution: render the chart with default values, pin the objects a tenant relies on, and wire the standard test: target the sibling charts already use. The detection work that makes missing suites loud (a chart with a test target must actually report suites) already guards the opted-in half, so every chart added here stays protected once it opts in.
Activity
lexfrei commentedon Sep 10, 2026
Three of the 89 carry an extra hazard worth using to order the work. Their
updaterecipe clears their owntemplates/before refetching, so a first-party file added there is deleted by the nextmake update, which exits 0. With no suite in the package, nothing downstream reddens and the loss reaches a cluster.Measured at
origin/main,f7cb9e785:Nine packages clear their own
templates/at that ref. Three of them have notesttarget:kubevirt-cdi-operator,kubevirt-instancetypes,objectstorage-controller.The ref is in the command because the count moves with the branch you run it on.
kubevirt-cdiis the ninth wiper atorigin/mainand stops being one when #4097 lands, so a run inside a checkout of that branch gives eight.Not a separate issue, and not the same as #4206 or #4119: those are about a guard that cannot see a loss, this is about a package that has no suite to report one. It just says which three of the 89 to do first.
test(vpn): add default render helm unit tests (#4347)
KrisD08 commentedon Oct 25, 2026
Hi Aleksei Sviridkin (@lexfrei) I'd like to work on this issue. I'm a student contributing for my course and can start right away. Thank you!