generated from coulomb/repo-seed
41 lines
1.2 KiB
Markdown
41 lines
1.2 KiB
Markdown
# Optional OpenCMIS TCK Harness
|
|
|
|
This directory reserves the integration-test boundary for Apache Chemistry
|
|
OpenCMIS TCK 1.1.0. The harness is intentionally optional because Java/Maven
|
|
tooling is not part of the default Python test suite.
|
|
|
|
Planned invocation shape:
|
|
|
|
```sh
|
|
mvn -Dcmis.browser.url=http://127.0.0.1:8000/cmis/compat-tck/browser \
|
|
-Dcmis.repository.id=kontextual-compat-tck \
|
|
test
|
|
```
|
|
|
|
The first target is a selected Browser Binding subset:
|
|
|
|
- repository information,
|
|
- type definitions,
|
|
- navigation,
|
|
- object reads,
|
|
- content stream reads,
|
|
- query subset,
|
|
- relationships,
|
|
- change log where supported.
|
|
|
|
Mutation groups should only be enabled for `governed-authoring` or
|
|
`compat-tck` profiles after the policy and audit gates are implemented.
|
|
|
|
Harness files:
|
|
|
|
- `tck-subset-map.json` maps engine capability groups to selected OpenCMIS TCK
|
|
groups and known gaps.
|
|
- `tck-result-template.json` is the compact result capture format for optional
|
|
TCK runs. Results should be stored outside the default repo history unless
|
|
they document an intentional compatibility baseline.
|
|
|
|
Default `pytest` does not execute Java/Maven. It validates the map and result
|
|
template so the optional harness does not drift away from the implemented
|
|
profiles and fixtures.
|
|
|