Certificate Management (CX-0135)
TestLab ships a Certificate Management TCK, certificate-management-tck-v0.0.1. It checks a provider's Company Certificate Management API (CCMAPI) against CX-0135 v3.1.0. Every call goes through the provider's Eclipse Dataspace Connector. The suite lives at docs/examples/certificate-management-v2/raw/ and holds four tests:
| Order | Test | Proves |
|---|---|---|
| 1 | Catalog Policy Validation | The CCMAPI offer can be found and is made under the CX-0135 usage policy |
| 2 | Request Certificate | A certificate request through the data plane is answered |
| 3 | Send Feedback Notification | A status notification is accepted and acknowledged back to TestLab |
| 4 | Error Handling | A request for an unknown certificate type is rejected |
Which page to read
| Page | Read it for |
|---|---|
| Business Guide | What a passing run certifies, what it does not, and what the provider must have in place |
| Developer Guide | Configuring a run, running it, reading the results, and fixing failures |
| Architecture Guide | How the suite is built: manifest, test phases, the connector flow, mocks and callbacks |
| CCM Conformity Testing | Test-by-test reference: every step, every check, every value it reads |
At a glance
Bash
# Check the manifest and its tests against the syntax and the step registry
testlab validate docs/examples/certificate-management-v2/raw/index.yaml
# Build a package and list what a run of it will ask for
testlab compile docs/examples/certificate-management-v2/raw/index.yaml --output ccm.tck
testlab inspect ccm.tck --variables --infrastructure
# Run it (see the Developer Guide for run-config.yaml)
testlab run docs/examples/certificate-management-v2/raw/index.yaml --config run-config.yaml