-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
False
-
None
-
False
-
-
origin should support calling an external test binary implemented using openshift-tests-extension. There's an external test binary already in the hyperkube repo: https://github.com/openshift/kubernetes/tree/master/openshift-hack/cmd/k8s-tests-ext
Here's the existing external binary using the legacy interface:
https://github.com/openshift/origin/blob/master/pkg/test/ginkgo/cmd_runsuite.go#L174-L179
That can just be removed and replaced with k8s-test-ext.
MVP requires for k8s-tests:
- Support for list and run-tests:
- openshift-tests runs list, to support the ExtensionTestSpec JSON format instead of the legacy one
-
- Run the tests with the main loop alongside origin's existing tests
- Process the ExtensionTestResult format, and convert it to JUnit and origin's internal representations (origin's testCase structure)
Additional things for later:
- Support suites by getting them from the "info" command and CEL expressions to filter tests
- Handle the informing/blocking lifecycle for tests(informing shouldn't make openshift-tests exit 1)
The design should be flexible enough to allow a scheduling algorithm that takes into account available resources/isolation, but the first pass doesn't need to implement it yet.
- is related to
-
TRT-1903 Port annotation framework to Origin
- Closed
- links to