docs(annex): add informative Conformance Test Corpus (T-16)#590
Open
aorzelskiGH wants to merge 1 commit into
Open
docs(annex): add informative Conformance Test Corpus (T-16)#590aorzelskiGH wants to merge 1 commit into
aorzelskiGH wants to merge 1 commit into
Conversation
Introduce a new annex that defines a structured, informative set of acceptance tests for conforming implementations. The corpus covers: - Query Language parsing and evaluation - HTTP/REST API (auth, PUT CREATE/UPDATE, invoke, files, query) - Error handling and edge cases (parse, schema, cast errors, profile applicability) Each test case has a stable ID, one-line purpose and expected behaviour, so the corpus can be turned directly into an executable conformance test suite. Aligned with the matching corpus in IDTA-01004. Refs: Review Finding T-16 Made-with: Cursor
aorzelskiGH
requested review from
BirgitBoss,
alexgordtop,
danielporta,
g1zzm0,
mjacoby,
sebbader-sap,
waltersve and
zrgt
as code owners
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| | Status `422`, JSON-pointer in body. | ||
|
|
||
| | HTTP.discovery.001 | ||
| | Discovery endpoints MUST honour the operation-to-RIGHT mapping of this spec (xref:annex/operation-to-right-mapping.adoc[]). |
| This work is licensed under a [Creative Commons Attribution 4.0 International License]( | ||
| https://creativecommons.org/licenses/by/4.0/). | ||
|
|
||
| SPDX-License-Identifier: CC-BY-4.0 |
| //// | ||
|
|
||
| [#conformance-test-corpus] | ||
| = Conformance Test Corpus (informative) |
|
|
||
| This annex defines an informative but structured set of *acceptance tests* for conforming implementations of the AAS Query Language and the HTTP/REST API defined in this specification. The corpus is intentionally technology-neutral and worded as a set of test cases; an implementation is said to be conformant to a given area if it passes every required test case in that area. | ||
|
|
||
| The corpus is aligned with the conformance test corpus in IDTA-01004 Part 4: Security xref:bibliography.adoc#bib3[[3\]]. Tests that exercise shared formula grammar productions (logical expressions, comparisons, FieldIdentifiers, value literals, type casts, `$match`/`$and`/`$or`/`$not`) are normative for both specifications. |
| | Status `200 OK` if rule allows, else `403`. | ||
|
|
||
| | HTTP.invoke.001 | ||
| | `POST /.../operations/{idShortPath}/invoke` MUST require the RIGHT `EXECUTE`. |
BirgitBoss
approved these changes
May 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a new informative annex
Conformance Test Corpusto IDTA-01002 with a structured, technology-neutral set of acceptance tests that implementations can run to demonstrate conformance.Problem
The specification currently has no structured catalogue of test / acceptance criteria. Reviewers and implementers rediscover the same edge cases on every review cycle (parse vs. schema errors, cast runtime errors, profile applicability, supplemental semantic IDs, PUT CREATE/UPDATE disambiguation,
$and/$oridentities, ...).Solution
documentation/IDTA-01002-3/modules/ROOT/pages/annex/conformance-test-corpus.adoc.QL.parse.001,HTTP.put.001,ERR.schema.001, ...), a one-line purpose, an expected behaviour and a requirement level.nav.adoc.Affected files
documentation/IDTA-01002-3/modules/ROOT/pages/annex/conformance-test-corpus.adoc(new)documentation/IDTA-01002-3/modules/ROOT/nav.adocReview notes
aas-specs-securityadds a matching corpus for the Access Rule Model.Refs: Review Finding T-16