README note on Scorecard tests #143
Conversation
Include how to easily use scorecard testing to validate the operator bundle directory
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: razo7 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
|
/override 4.15-openshift-e2e |
|
@razo7: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/override ci/prow/4.15-openshift-e2e |
|
@razo7: Overrode contexts on behalf of razo7: ci/prow/4.15-openshift-e2e In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/override 4.12-openshift-e2e |
|
@razo7: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/override ci/prow/4.12-openshift-e2e |
|
@razo7: Overrode contexts on behalf of razo7: ci/prow/4.12-openshift-e2e, ci/prow/4.13-openshift-e2e, ci/prow/4.14-openshift-e2e, ci/prow/4.16-openshift-e2e In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/override ci/prow/4.12-test Overriding the required tests that are skipped in docs only changes |
|
@razo7: Overrode contexts on behalf of razo7: ci/prow/4.12-test, ci/prow/4.13-test, ci/prow/4.14-test, ci/prow/4.15-test, ci/prow/4.16-test In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
| @@ -235,6 +235,10 @@ Run `make test` | |||
| 3. Export the operator installed namespace (e.g., *openshift-workload-availability*) before running the e2e test: | |||
| `export OPERATOR_NS=openshift-workload-availability && make test-e2e` | |||
|
|
|||
| ### Run Scorecard tests | |||
|
|
|||
| Run `make test-scorecard` on a running Kubernetes cluster to statically validate the operator bundle directory using [Scorecard](https://sdk.operatorframework.io/docs/testing-operators/scorecard/). | |||
There was a problem hiding this comment.
how do you run that command "on a cluster"?
Why we need this PR
Include how to easily use scorecard testing to validate the operator bundle directory. Follow up to #141
Changes made
Which issue(s) this PR fixes
Test plan