Validation of OpenShift Pipeline releases using Gauge
-
Clone this repository
-
Need OpenShift cluster
-
Download latest OpenShift Client for your operating system
Install Gauge to /usr/local/bin by running
curl -SsL https://downloads.gauge.org/stable | sh
or install Gauge to a <custom path> using
curl -SsL https://downloads.gauge.org/stable | sh -s -- --location-[custom path]
For other installation methods, refer to the Gauge documentation.
GO111MODULE=off gauge install go
GO111MODULE=off gauge install html-report
GO111MODULE=off gauge install screenshot
GO111MODULE=off gauge install xml-report
(optional)
GO111MODULE=off gauge install reportportal
Refer to the Gauge documentation for general information about how to run specifications (aka specs).
Majority of tests assume that they run on an OpenShift cluster with already installed OpenShift Pipelines operator (e.g. latest release of a nightly build).
Operator installation tests have to run as admin user
CATALOG_SOURCE=custom-operators CHANNEL=latest gauge run --log-level=debug --verbose --tags install specs/olm.spec
CATALOG_SOURCE=custom-operators CHANNEL=latest gauge run --log-level=debug --verbose --tags upgrade specs/olm.spec
gauge run --log-level=debug --verbose --tags uninstall specs/olm.spec
Notes:
CATALOG_SOURCE- catalog source name,redhat-operatorsfor released versions,custom-operatorsfor nightly buildsCHANNEL- channel to which the installation test is supposed to subscribe, e.g.latestorpipelines-1.9
The following tests have to run as admin user
gauge run --log-level=debug --verbose --tags e2e specs/metrics
gauge run --log-level=debug --verbose --tags 'e2e & tls' specs/triggers/eventlistener.spec
gauge run --log-level=debug --verbose --tags e2e specs/clustertasks/clustertask.spec
gauge run --log-level=debug --verbose --tags 'e2e & linux/amd64' specs/clustertasks/clustertask-multiarch.spec
gauge run --log-level=debug --verbose --tags e2e specs/operator/rbac.spec
gauge run --log-level=debug --verbose --tags e2e specs/operator/auto-prune.spec
gauge run --log-level=debug --verbose --tags e2e specs/operator/addon.spec
The following tests can run as both admin and regular/non-admin user
gauge run --log-level=debug --verbose --tags e2e specs/pipelines
gauge run --log-level=debug --verbose --tags 'e2e & !tls' specs/triggers
gauge run --log-level=debug --verbose --tags disconnected-e2e specs/clustertasks/clustertask.spec
gauge run --log-level=debug --verbose --tags 'e2e & !skip_linux/amd64' specs/clustertasks/clustertask-s2i.spec
- Create or update a spec file in
specsdirectory usingMarkdownsyntax. - If necessary, create steps in a new or appropriate existing
Gofile instepsdirectory. - If necessary, create test resources in
YAMLintestdatadirectory. - If necessary, implement new steps using
Goin new or appropriate existing file inpkgdirectory.
CI system is running these tests inside a container using image quay.io/openshift-pipeline/ci built using a Dockerfile hosted in a non-public repository.
cd <path_with_content_of_this_repo>
podman run --rm -it -v $KUBECONFIG:/root/.kube/config:z -v .:/root/release-tests:z -w /root/release-tests quay.io/openshift-pipeline/ci /bin/bash
gauge run ...
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent