https://github.com/complianceascode/ocp4e2e
E2E tests for verifying the Compliance Operator against ComplianceAsCode/content
https://github.com/complianceascode/ocp4e2e
Last synced: 19 days ago
JSON representation
E2E tests for verifying the Compliance Operator against ComplianceAsCode/content
- Host: GitHub
- URL: https://github.com/complianceascode/ocp4e2e
- Owner: ComplianceAsCode
- License: apache-2.0
- Created: 2021-05-04T13:24:51.000Z (almost 4 years ago)
- Default Branch: main
- Last Pushed: 2024-11-01T14:05:19.000Z (6 months ago)
- Last Synced: 2025-03-28T18:50:39.200Z (about 1 month ago)
- Language: Go
- Size: 5.57 MB
- Stars: 2
- Watchers: 4
- Forks: 5
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Compliance Operator Functional Tests
This repository contains end-to-end tests that exercise the
compliance-operator in Kubernetes deployments.
These tests require that you have a cluster deploy and available. These tests
will change the configuration of your deployment since they scan and remediate
issues in the cluster. Please be aware of the cluster you're running these
tests against as the tests do not restore the cluster or undo remediations
executed as part of the test.
## Parameters
- `PROFILE`: The profile to test. This value must match an existing profile in
[ComplianceAsCode/content](https://github.com/ComplianceAsCode/content/),
typically ending in a `.profile` file extension (required).
- `PRODUCT`: The product to test (default: `rhcos4`).
- `CONTENT_IMAGE`: An image registry and image where the content is located
(default: `quay.io/complianceascode/ocp4:latest`)
- `ROOT_DIR`: File path of the
[ComplianceAsCode/content](https://github.com/ComplianceAsCode/content/). By
default, the tests will clone the repository into a `/tmp` directory.
Providing the file path to the content will reduce the time it takes by not
cloning the repository.
- `TEST_FLAGS`: Optional `go test` flags (default: `-v -timeout 120m`)
- `INSTALL_OPERATOR`: If true, the tests will attempt to install the
compliance-operator in the provided cluster (default: `true`).
## Usage
You can use a dedicate Makefile target for running the tests
```console
$ PROFILE=high make e2e
```