nlstn/OData Compliance Suite
Run the OData v4 compliance suite against a running OData service and fail the job if it is not conformant. Downloads a prebuilt binary and runs it on the runner host, so a service-under-test on localhost is reachable directly.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| server | URL of the OData service under test (its root). | yes | — |
| version | OData version to test: 4.0 | 4.01 | vocabularies | all. | no | all |
| pattern | Run only suites whose name contains this substring. | no | "" |
| verbose | Show every individual test result. | no | false |
| debug | Show full HTTP request/response details. | no | false |
| timeout | Seconds to wait for the server to become reachable. | no | 30 |
| strict | Treat capability-skipped tests as failures. By default, tests for features the service declares unsupported via Capabilities.V1 annotations are skipped, not failed. Set to 'true' to disable that and require full compliance. | no | false |
| suite-version | Release tag of the suite to run (e.g. v1.2.3), "latest", or "source" to build and run the suite from the checked-out action ref. This pins the compliance implementation independently of the action ref unless "source" is selected. | no | latest |
| format | Output format for the structured report: text (default), junit, json, or sarif. "text" writes human-readable output only. The other formats also write a machine-readable report to report-file (or stdout when report-file is empty). | no | text |
| report-file | Path where the structured report is written (e.g. odata-results.xml). Required when format is junit, json, or sarif and you want to upload the report as an artifact. When omitted the report goes to stdout. | no | "" |
Outputs
| name | description |
|---|---|
| report-file | Path to the generated report file (empty when report-file input was not set). |