A OpenCMIS TCK harness to assess CMIS Standard conformity.
Find a file
2026-05-07 23:07:14 +02:00
docs chore(consistency): sync task status from DB [auto] 2026-05-07 22:58:28 +02:00
mappings chore(consistency): sync task status from DB [auto] 2026-05-07 22:58:28 +02:00
profiles chore(consistency): sync task status from DB [auto] 2026-05-07 22:58:28 +02:00
runners chore(consistency): sync task status from DB [auto] 2026-05-07 22:58:28 +02:00
src/open_cmis_tck chore(consistency): sync task status from DB [auto] 2026-05-07 22:58:28 +02:00
tests chore(consistency): sync task status from DB [auto] 2026-05-07 22:58:28 +02:00
workplans Workplan to actually control the testrun 2026-05-07 23:07:14 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-05-07 22:58:28 +02:00
.gitignore core architecture blueprint 2026-05-07 10:53:53 +02:00
extension.json chore(consistency): sync task status from DB [auto] 2026-05-07 22:58:28 +02:00
INTENT.md Separated open-cmis-tck and guide-board repositories 2026-05-07 21:52:08 +02:00
LICENSE Initial commit 2026-05-07 06:02:53 +00:00
pyproject.toml Separated open-cmis-tck and guide-board repositories 2026-05-07 21:52:08 +02:00
README.md chore(consistency): sync task status from DB [auto] 2026-05-07 22:58:28 +02:00

open-cmis-tck

open-cmis-tck is the CMIS conformance-preparation extension for guide-board. It keeps CMIS-specific runner code, profiles, capability mappings, and workplans outside the generic framework repo.

This extension does not issue certifications. It produces preparation evidence that can support compatibility reviews and future certification work.

Relationship To Guide Board

Use this repo as an external extension root:

cd ../guide-board
PYTHONPATH=src python3 -m guide_board \
  --extension-dir ../open-cmis-tck \
  extensions list

The extension root is this repository directory. It exposes:

  • extension.json
  • src/open_cmis_tck/preflight.py
  • runners/opencmis_tck.py
  • mappings/cmis-capability-map.json
  • CMIS sample profiles under profiles/

Local Baseline

From the guide-board repo:

PYTHONPATH=src python3 -m guide_board \
  --extension-dir ../open-cmis-tck \
  plan \
  --target ../open-cmis-tck/profiles/targets/kontextual-cmis-compat.json \
  --assessment ../open-cmis-tck/profiles/assessments/cmis-browser-baseline.json

To run the current baseline:

PYTHONPATH=src python3 -m guide_board \
  --extension-dir ../open-cmis-tck \
  run \
  --target ../open-cmis-tck/profiles/targets/kontextual-cmis-compat.json \
  --assessment ../open-cmis-tck/profiles/assessments/cmis-browser-baseline.json \
  --output-dir /tmp/open-cmis-tck-baseline

Expected current behavior:

  • CMIS Browser Binding preflight runs first.
  • Failed preflight blocks downstream TCK groups.
  • The Java/Maven OpenCMIS wrapper reports structured blockers until a local Apache Chemistry TCK command is configured.
  • If a command is configured, raw stdout/stderr and normalized runner output are captured under the guide-board run directory.

Runner command configuration lives in runtime_policy.opencmis_tck.command. See docs/OPENCMIS-TCK-RUNNER.md.

Tests

Run extension tests with the guide-board core on PYTHONPATH:

PYTHONPATH=../guide-board/src python3 -m unittest discover -s tests

Docs

Boundary

Apache Chemistry/OpenCMIS TCK dependencies may be restricted by upstream licensing or distribution constraints. This repo records the extension boundary and wrapper interface, but restricted harness assets should be resolved or mounted explicitly by the user or by a future extension-specific image.