Kubernetes Contributor Summit North America 2024

Traditionally, E2E testing has been based on Ginkgo, whereas unit and integration testing are based on `go test`. Because of the different APIs, different helper packages have been developed for both although the often do the same thing (create objects

ktesting is an abstraction of common functionality (reporting failures, logging, cleanup, timeouts). We could use it to unify the test helper code. But should we?

This session provides a comparison of Ginkgo vs. `go test` and how ktesting hides the differences. It explains some API choices made for ktesting.