coulomb/open-cmis-tck
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

maturity scorecard generation

Browse Source
This commit is contained in:
Bernd Worsch
2026-05-08 01:59:42 +02:00
parent b4f620533c
commit 3a94042ca3
14 changed files with 1385 additions and 95 deletions
Download Patch File Download Diff File Expand all files Collapse all files

55
docs/LOCAL-RUNBOOK.md
View File

@@ -61,9 +61,18 @@ Expected dry-run artifacts:
If preflight fails, fix the target profile or endpoint before continuing.
Generate a maturity scorecard from the dry-run output:
```sh
cd /home/worsch/open-cmis-tck
PYTHONPATH=src python3 scripts/cmis_scorecard.py \
--run-dir /tmp/open-cmis-tck-dry-run
```
## Install Java And Maven
The current WSL environment needs Java and Maven before the real TCK can run:
The current WSL environment does not expose system `java` and `mvn` on `PATH`.
Either install them as system packages:
```sh
sudo apt-get update
@@ -73,10 +82,33 @@ sudo apt-get install -y openjdk-17-jdk maven
Use a managed local Java/Maven installation instead if preferred. The bootstrap
only requires `java` and `mvn` on `PATH`.
Or use the repo-local toolchain under `.local/`:
```sh
cd /home/worsch/open-cmis-tck
python3 scripts/install_local_toolchain.py
source .local/toolchains/env.sh
PYTHONPATH=src python3 scripts/bootstrap_opencmis_tck.py --resolve
```
The local installer downloads a Linux x64 Temurin JDK 17 archive and Apache
Maven 3.9.11, extracts them under `.local/toolchains`, verifies Maven's SHA-512
checksum, writes `.local/toolchains/env.sh`, and leaves the downloaded binaries
outside version control.
This workspace has already been bootstrapped with the repo-local path. In a new
shell, source the environment file before running live TCK commands:
```sh
cd /home/worsch/open-cmis-tck
source .local/toolchains/env.sh
```
## Resolve The TCK Runtime
```sh
cd /home/worsch/open-cmis-tck
source .local/toolchains/env.sh
PYTHONPATH=src python3 scripts/bootstrap_opencmis_tck.py --resolve
```
@@ -100,6 +132,7 @@ After bootstrap reports `ready`, run the baseline assessment:
```sh
cd /home/worsch/guide-board
source /home/worsch/open-cmis-tck/.local/toolchains/env.sh
PYTHONPATH=src python3 -m guide_board \
--extension-dir ../open-cmis-tck \
run \
@@ -116,6 +149,26 @@ The baseline currently selects:
Expand selected check groups only after the repository/type run produces useful
output.
Then generate the maturity scorecard:
```sh
cd /home/worsch/open-cmis-tck
PYTHONPATH=src python3 scripts/cmis_scorecard.py \
--run-dir /tmp/open-cmis-tck-live
```
Review the real TCK evidence before expanding the scope:
```text
/tmp/open-cmis-tck-live/normalized/evidence.json
/tmp/open-cmis-tck-live/artifacts/open-cmis-tck/tck/<check-group>/console-runner-stdout.txt
/tmp/open-cmis-tck-live/artifacts/open-cmis-tck/tck/<check-group>/normalized-runner-result.json
```
The normalizer preserves native OpenCMIS statuses (`OK`, `WARNING`, `FAILURE`,
`SKIPPED`, `UNEXPECTED_EXCEPTION`, and `INFO`) as case-level facts while mapping
the overall check group to guide-board's result vocabulary.
## Authenticated Targets
For environment credentials: