CMIS compliance fixture integration and optional OpenCMIS TCK harness boundary
This commit is contained in:
parent
88f9df6288
commit
23c90b33a7
7 changed files with 251 additions and 6 deletions
|
|
@ -26,3 +26,15 @@ The first target is a selected Browser Binding subset:
|
|||
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.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue