Conformance testing¶
Code snapshot: 27 September 2026, 2b80a1ea. fdyno runs three
independent black-box suites against its DynamoDB endpoint and a local
FoundationDB 7.3.51 cluster. They use boto3 or the AWS SDK for JavaScript,
not direct calls to fdyno's Go packages. The selected cases test API
behavior; they do not define the entire DynamoDB specification. The Go
version in go.mod is currently 1.27.1.
Selected-case CI¶
The same-commit CI run 36307867990
completed the build/unit, three selected conformance, and two-instance
fault-smoke jobs. Report each suite's result against its own selected
denominator:
| Suite | Selected result | Client and scope |
|---|---|---|
| ScyllaDB Alternator | 1,452 passed; 34 deselected | boto3/pytest; item, query, index, expression, transaction, stream, TTL, and protocol cases. |
| nubo-db | 693 passed; one skipped | AWS SDK for JavaScript v3/Vitest; selected API and validation cases. The cross-account authorization case is skipped because fdyno has no account model. |
| ExtendDB portable suite | 876 passed; two skipped; 186 deselected; one expected failure | boto3/pytest; selected wire-protocol cases rather than ExtendDB's management-layer features. |
These are three different selected sets. Do not add their counts into a
single compatibility percentage or treat deselected cases as passes.
The test source revisions, exact exclusions, and runnable commands are
tracked in the private test/UPSTREAM_SYNC.md
and test/README.md.
Selected behavior¶
The suites exercise supported item CRUD, key validation, conditions, expressions, Query/Scan pagination, batch and transaction responses, secondary indexes, streams, TTL, return values, and error shapes. Selected ExtendDB cases check raw expression-size boundaries, table-update validation, GSI definition preservation, single-action transaction HASH key size, and consumed-capacity response shape. The latter does not verify numeric metering, billing or index charges. A route or a passing example does not prove all options of an operation.
Not included in the selection¶
- Positive historical PITR behavior is excluded because fdyno reports that workflow unavailable. The negative unsupported behavior remains part of the API contract.
- A small set of region-contested deep condition-only expression-value acceptance cases is excluded; fdyno enforces its documented nesting boundary. Selection uses exact test IDs, not a broad prefix.
- Product-specific management tests, cross-account identity behavior, and unported upstream changes are not certified by this selection.
- A green selected run is not a sustained concurrent hot-key correctness test, a replicated FoundationDB failure test, or a performance result.
For implemented operations and exclusions, see Compatibility. For request sizes and FoundationDB boundaries, see Limits. Run the selected suites against the exact source and topology you intend to evaluate.