kubernetes/test/e2e/common/storage
Patrick Ohly 6af5bf0585 e2e: enhance tests that check for pod staying pending
Using WaitTimeoutForPodRunningInNamespace followed by ExpectError was not very
precise (any error passed the check, not just the expected timeout) and
hard to read. Now the test's expectation is spelled out explicitly: the pod
must stay in pending.
2023-01-16 09:12:30 +01:00
..
configmap_volume.go e2e: enhance tests that check for pod staying pending 2023-01-16 09:12:30 +01:00
downwardapi_volume.go e2e: use Ginkgo context 2022-12-16 20:14:04 +01:00
downwardapi.go e2e: use Ginkgo context 2022-12-16 20:14:04 +01:00
empty_dir.go e2e: use Ginkgo context 2022-12-16 20:14:04 +01:00
framework.go update ginkgo from v1 to v2 and gomega to 1.19.0 2022-07-08 10:44:46 +08:00
host_path.go e2e: use Ginkgo context 2022-12-16 20:14:04 +01:00
OWNERS
projected_combined.go e2e: use Ginkgo context 2022-12-16 20:14:04 +01:00
projected_configmap.go e2e: enhance tests that check for pod staying pending 2023-01-16 09:12:30 +01:00
projected_downwardapi.go e2e: use Ginkgo context 2022-12-16 20:14:04 +01:00
projected_secret.go e2e: enhance tests that check for pod staying pending 2023-01-16 09:12:30 +01:00
secrets_volume.go e2e: enhance tests that check for pod staying pending 2023-01-16 09:12:30 +01:00
util.go
volumes.go e2e: use Ginkgo context 2022-12-16 20:14:04 +01:00