Merge conformance tests into crossplane/crossplane?

[negz]

What problem are you facing?

These conformance tests are effectively integration tests. We intend to version them alongside Crossplane releases, i.e. there will be a 1.2 branch of this repository to correspond to the release-1.2 branch of the crossplane/crossplane repository.

Merging these tests into crossplane/crossplane (e.g. under a conformance/ directory) would enable Crossplane contributors to update the conformance tests in the same pull request they open to add a new feature. It would also potentially allow us to use the conformance test suite as a general integration test suite.

How could conformance help solve your problem?

We could deprecate this repository and move the conformance tests into crossplane/crossplane. We should also assess this repository as it relates to crossplane/test, which could potentially replace this repository in future.

[negz]

CC @rahulgrover99 and @hasheddan. I don't think I'll tackle this in the near future, but I bet you two have thoughts. :)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jbw976]

This idea came up again in #31 (review):

I think we should consider deduping these conformance tests with the E2E tests. I could imagine keeping both under c/c test/e2e directory. I suspect we could use labels such that conformance tests only ran a subset of the E2E tests (plus some conformance specific tests)?

The conformance test for distros of Crossplane would then become "must pass the c/c E2E suite with --label type=conformance. I suspect this'd reduce duplication and ongoing maintenance burden.