Unable to run a specific integration test about community HOT 4 CLOSED

Looks like kubernetes/kubernetes#33952 provides a way to specify a test case:

make test-integration WHAT="auth -test.run=TestKindAuthorization"

This seems hacky (due to the dependency on the positional argument - auth in this case), but it does work. Should the documentation be updated to match the script, or the other way around?

cc: @thockin @eparis @deads2k @ncdc

from community.

Why doesn't the documented way work? It seems straight-forward, but I didn't dig in. This hack is a hack.

from community.

I was misinterpreting go test output. I assumed that output like the following indicated that tests were running but that's not the case (it will appear even for packages for which no tests are run):

PASS
ok      k8s.io/kubernetes/test/integration/serviceaccount       0.101s

So the documented way does work, my bad.

I'm assuming that #31533 was aiming to bypass this behavior by scoping to a single integration test package. I think it would be preferable for make test-integration to follow the convention of make test in passing WHAT through to the test runner, and I plan on fixing that.

from community.

Fix for make test-integration posted to kubernetes/kubernetes#41581

from community.