Restructure conformance tests

[coryrc]

Moved from knative/serving#6264

Useful conversation and updates are present in the thread.

In what area(s)?
/area test-and-release

Describe the feature
Design doc

Summary:
Our API conformance tests were written before we had a pattern to split out tests and before the API specification identified ‘should’ and ‘must’ fields. This resulted in them covering a large swath of functionality in large tests, making it difficult to isolate conformance gaps. They need some help to become useful to people who wish to prove conformance and useful to people to make their implementation conformant.

[knative-prow-robot]

@coryrc: The label(s) area/test-and-release cannot be applied, because the repository doesn't have them.

In response to this:

Moved from knative/serving#6264

Useful conversation and updates are present in the thread.

In what area(s)?
/area test-and-release

Describe the feature
Design doc

Summary:
Our API conformance tests were written before we had a pattern to split out tests and before the API specification identified ‘should’ and ‘must’ fields. This resulted in them covering a large swath of functionality in large tests, making it difficult to isolate conformance gaps. They need some help to become useful to people who wish to prove conformance and useful to people to make their implementation conformant.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.