Skip to content

DynamoDB Local on

6ada631ec7aa as measured in this run

Grade not scored

3 of 1,920 tests got no answer (3 a transport failure or 5xx), so the suite gives no letter or figures for this run. 1,237 passed, 601 failed, 79 not attempted.

Tier 1 · Core 8.3% diverges
100.0% covered
42 of 507 attempted
Tier 2 · Complete not scored
3 of 533 got no answer 61 unsupported
119 of 469 attempted
Tier 3 · Strict 50.0% diverges
98.0% covered 18 unsupported
440 of 862 attempted

How it got here

DynamoDB Local's history up to this run, ending on the figures above. Both are plotted because neither reads correctly alone: divergence falls when a target stops attempting an operation it used to get wrong, so a fall in the first plot is only an improvement if the second one holds. The target's own page carries the full history.

Divergence

DynamoDB Local divergence up to 2026-11-15 0% 15% 30% divergence - lower is better 23 May 9 Jun 22 Jun 30 Jun 14 Jul 20 Jul 28 Jul 13 Aug 23 Aug 20 Sep 22 Oct 15 Nov 24.8%
Diverging on 24.8% of the suite as of 8 Nov. Lower is better, so a falling line is a target getting closer to real DynamoDB.

Coverage

DynamoDB Local coverage up to 2026-11-15 92% 96% 100% coverage - higher is better 23 May 9 Jun 22 Jun 30 Jun 14 Jul 20 Jul 28 Jul 13 Aug 23 Aug 20 Sep 22 Oct 15 Nov 95.3%
Implementing 95.3% of the suite as of 8 Nov, as little as 93.8% on 21 Aug. Higher is better. This is the share of the suite's tests a target implements at all. A fail becoming a skip leaves both numerators over the same fixed denominator, so a fall here is matched point for point by a fall in divergence: withdrawal costs exactly as much coverage as it gains divergence.

Where it fell short on this date

The tests this run recorded as failing, each linked to its source at the commit that measured it. For the current picture, see this target's latest results, or every target in this run.

Tests that got no answer

The tests this run got no answer to, by operation, each with the reason the suite recorded. None of them is a divergence, and any one of them is enough for a run to be not scored.

  • partiql Tier 2 3 got no answer
    • ExecuteStatement - PartiQL Limit a Limit at or past the 32-bit range returns the whole partition on one page (a transport failure or 5xx) source:1386
    • ExecuteStatement - PartiQL Limit a Limit near the 64-bit range returns a whole set of keys on one page (a transport failure or 5xx) source:1394
    • ExecuteStatement - PartiQL Limit a Limit written with an exponent or past 64 bits returns the whole partition on one page (a transport failure or 5xx) source:1402