The moxml conformance test suite: certify any XML engine against the moxml model.
The moxml processing model (https://github.com/lutaml/moxml — docs/_references/processing-model.adoc) is a set of committed answers: one object model, one document order, one serialization shape, one canonicalization, one validation verdict — for every question an XML program can ask. The moxml conformance dataset (schema 5, 177 cases across seven families) IS those answers as data, and this gem is the runner that drives any engine through them.
| Family | Cases | Facade faces |
|---|---|---|
builtin_lexical |
81 |
|
xsd_regex_translation |
21 |
|
schema_wildcards |
24 |
|
entity_registry |
11 |
|
serialization |
20 |
|
c14n |
14 |
|
xsd_structural |
6 |
|
The quick path is the CLI:
$ moxml-testsuite
moxml-testsuite (facade: Moxml::TestSuite::Reference)
PASS decisions (126 cases)
PASS entity_registry (11 cases)
PASS serialization (20 cases)
PASS c14n (14 cases)
PASS xsd_structural (6 cases)
$ moxml-testsuite --adapter leptris
$ moxml-testsuite --families c14n,serializationThe exit code mirrors the verdict (0 certified, 1 failed, 2 unusable adapter), so it drops straight into CI.
The library path - any object implementing the certification protocol can be certified:
require "moxml/testsuite"
report = Moxml::TestSuite.run(Moxml::TestSuite::Reference.new)
puts report
report.passed? # => trueReference implements the whole protocol on moxml itself — pin the engine when the host carries several:
Moxml::TestSuite::Reference.new(adapter: :leptris)
Moxml::TestSuite::Reference.new(adapter: :nokogiri)A facade that cannot answer a family’s faces sees that family SKIP — loudly, in the report — never a quiet pass. A facade that answers against the dataset FAILs with the offending case named.
The model’s degradation is one-directional: an engine that cannot evaluate a construct stays silent (under-report); it never produces a different answer. The suite pins that too — unevaluatable rows expect under-reporting, and "answered wrong" and "answered differently per engine" are both failures. Equivalence is to the model, not merely engine-to-engine.
The dataset is generated from the moxml suite (rake conformance:export in lutaml/moxml) and consumed by the cross-language runners: moxml-rs (Rust) and moxml-ts (TypeScript). schema 5 is the row-shape version; generator names the producing moxml release.