357ad91d78
This test has been part of the Conformance suite since at least Kubernetes 1.2 (2015-10-xx). Some years later, around 2018-10-xx, we drafted a rigorous set of rules for tests to follow in order to be eligible for promotion to Conformance. We explicitly disallowed any tests that check for specific Events, since they are not an API, and we make no guarantees about their contents nor their delivery. Unfortunately, we neglected to go through the existing corpus of Conformance tests with a fine-toothed comb after drafting these rules. The very nature of what this test is attempting to exercise and verify is specific Events, and their delivery, thus making it ineligible for Conformance. We should have caught and demoted this test back then. Better late than never? |
||
|---|---|---|
| .. | ||
| image | ||
| testdata | ||
| cf_header.md | ||
| conformance_test.sh | ||
| doc.go | ||
| gen-conformance-docs.sh | ||
| gen-conformance-yaml.sh | ||
| gen-specsummaries.sh | ||
| OWNERS | ||
| README.md | ||
| spec-to-docs.sh | ||
| spec-to-yaml.sh | ||
| walk_test.go | ||
| walk.go | ||
This directory contains the regression test for controlling the list of all conformance tests.
If you add or remove a conformance test, this test will fail and you will need
to update the golden list of tests stored in testdata/. Changes to that file
require review by sig-architecture.
To update the list, run hack/update-conformance-yaml.sh
Add the changed file to your PR, then send for review.