Skip to content

Explain output of compliance test. #1076

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mbuechse merged 1 commit into from
Jan 30, 2026
Merged

Explain output of compliance test. #1076

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions Tests/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,12 +48,17 @@ pip install -r kaas/requirements.txt
Given a kubeconfig file `path/to/kubeconfig.yaml`, run

```shell
./scs-compliance-check.py -v -a kubeconfig=path/to/kubeconfig.yaml -a subject_root=. -s SUBJECT scs-compatible-kaas.yaml
./scs-compliance-check.py -v -a kubeconfig=path/to/kubeconfig.yaml -a subject_root=. -s SUBJECT -o report.yaml scs-compatible-kaas.yaml
```

Replace `SUBJECT` with an arbitrary, but meaningful subject name.
Also, please note that the check will always use the `current-context` of the kubeconfig and will
fail if it isn't set.
Replace `SUBJECT` with an arbitrary, but meaningful subject name. Also, please note that the check
will always use the `current-context` of the kubeconfig and will fail if it isn't set.

A report in YAML format will be created.

Additionally, the directory `sono-results` will be generated. It contains a JUnit XML file:
`plugins/e2e/results/global/junit_01.xml`. You can render it to HTML with a tool like junit2html.
This might give you hints as to why a test failed.

## Usage information (help output)

Expand Down