User Story

Define a core set of features that QE can verify and run automated tests against.

This will be time-boxed for one sprint.

Acceptance Criteria

• Shipwright downstream feature tests should exist in a GitHub repository
• Initial "core"/"basic" set of features to test are written as .feature files
• Features are linked to GitHub/Polarion test cases
• Bootstrap CI in this repository.
• NodeJS, Java, Python, Go image testing for S2I
• Simple Containerfile build for Buildah (Golang)
• Test framework will need to manually deploy the BuildStrategies following instructions given in the README.md to customers.

Docs Impact

None

QE Impact

This is a QE-driven story. Engineering will be consulted.

PX Impact

None

Notes

QE feature tests should use the shp CLI as much as possible.
If the CLI does easily support a particular feature or use case, we can fall back to using oc apply -f <YAML>

End goal is that we are able to run smoke tests against downstream Shipwright using OpenShift CI.