Goals

• Developers can run the entire CI test suite (unit, functional and e2e tests) on a CRC cluster
• It is reasonable to expect that a full pass on CRC will lead to a full pass in CI.

Non-Goals

CRC needs close to 16G of memory to run our tests, so the target here is a 32G laptop.

It is not a requirement for this Epic to get this all running on a 16G laptop, although if that is possible it is a major bonus.

Motivation

• Developers can test their work on the compete set of tests used by CI before pushing
• Speed up development by removing the long wait-for-CI step in the cycle.
• Speed up CI by reducing the CI failures due to mistakes that could have been detected locally.

Alternatives

Continue to tie all development to costly and scarce cluster resources.

Clearly we do need to continue testing on "real" clusters, but making it possible to use CRC for dev-private tests would reduce the cost and load on cluster resources.

Acceptance Criteria

1. Create a CRC cluster with 16G mem on a 32G laptop
2. Check out latest master
3. Run all tests on CRC
4. They pass.

Risk and Assumptions

None special.

Documentation Considerations

Internal dev doc only.

Open Questions

Additional Notes

We can already run most of the test suite on CRC, so this epic is just removing the few final snags to being able to do a complete CI-equivalent test run on CRC.

Once this is done, it will be possible to work on optimizing the tests to run on a smaller laptop; which will also reduce the demand on cluster resource when run on "real" clusters.