Commit Graph

5 Commits

Author SHA1 Message Date
Steve Kuznetsov
305652a432 conformance: do not parse resourceVersion
This test wishes to observe a watch event. In order to do this in the
past, the test chose a well-known `Service` object, fetched it, and did
arithmetic on the returned `resourceVersion` in order to start a watch
that was guaranteed to see an event. It is not valid to parse the
`resourceVersion` as an integer or to do arithmetic on it, so in order
to make the test conformant to an appropriate use of the API it now:

 - creates a namespace
 - fetches the current `resourceVersion`
 - creates an object
 - watches from the previous `resourceVersion` that was read

This ensures that an event is seen by the watch, but uses the publically
supported API.

`ConfigMap`s are used instead of `Service`s as they do not require a
valid `spec` for creation and make the test terser.

Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
2022-03-10 09:46:04 -08:00
Mike Danese
3aa59f7f30 generated: run refactor 2020-02-07 18:16:47 -08:00
danielqsj
6596a14d39 add missing alias of api errors under test 2019-12-26 17:29:38 +08:00
Lukasz Szaszkiewicz
869aef61af improves watch and report e2e test to also check IsResourceExpired since the API can return both errors (Gone, Expired) 2019-12-17 14:29:25 +01:00
Clayton Coleman
15f5e64404 Detect watch protocol errors via an e2e test for apimachinery
This e2e test reproduces #62175 and will be expanded to check for other
negotiation related errors against real servers.
2019-11-10 21:30:34 -05:00