Feature Overview

Testing is one of the main pillars of production-grade software. It helps validate and flag issues early on before the code is shipped into productive landscapes. Code changes no matter how small they are might lead to bugs and outages, the best way to validate bugs is to write proper tests, and to run those tests we need to have a foundation for a test infrastructure, finally, to close the circle, automation of these tests and their corresponding builds help reduce errors and save a lot of time.

As a first step, its is important to understand the different pieces and layers required to run tests. To do so, a little background on the kata container architecture might help. Below is a 1000 feet overview of the main building blocks of the katacontainers project E2E.

Any changes in any of these components have the potential to affect (i.e., break) any of the other components, therefore, it is important to gate changes that have cross-components effects with proper testing.

This feature serves to act as the main body of work for enabling testing and CI in the context of Openshift Sandboxed Containers.

Background, and strategic fit

Testing and CI are the first layers of defense against customer complaints when running in production, the stronger this defense system is, the lower the number of issues are, the happier our customers will be.

Goals

• Build the necessary knowledge around CI systems tools for the different projects that kata interacts with.
• Build and Implement tests required to gate changes in Openshift from Kata (Openshift CI)
• Build and Implement tests required to gate changes in CRI-O from Kata (CRI-O CI)
• Build and Implement tests required to gate changes in Kata from CRI-O and Openshift (Kata CI)

Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?
• Does this feature have doc impact?
• New Content, Updates to existing content, Release Note, or No Doc Impact
• If unsure and no Technical Writer is available, please contact Content Strategy.
• What concepts do customers need to understand to be successful in [action]?
• How do we expect customers will use the feature? For what purpose(s)?
• What reference material might a customer want/need to complete [action]?
• Is there source material that can be used as a reference for the Technical Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or Release Note)?