Skip to content

ExtendDB on

v0.1.1 as measured in this run

Grade B
moderate divergence
answers 13.3% of the suite differently from real DynamoDB
95.1% covered · 43 unsupported
Tier 1 · Core 15.0% diverges
100.0% covered
67 of 446 attempted
Tier 2 · Complete 7.7% diverges
72.3% covered 43 unsupported
12 of 112 attempted
Tier 3 · Strict 13.6% diverges
100.0% covered
37 of 272 attempted

When this run was published the board led with a single correctness percentage. The figures here are that run's own results restated as divergence and coverage, so they read differently from what this page showed at the time. The changelog has the change.

How it got here

ExtendDB'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

ExtendDB divergence up to 2026-07-13 0% 10% 20% divergence - lower is better 24 May 26 May 9 Jun 18 Jun 21 Jun 23 Jun 27 Jun 30 Jun 2 Jul 13 Jul 13.3%
Diverging on 13.3% of the suite as of 13 Jul. Lower is better, so a falling line is a target getting closer to real DynamoDB.

Coverage

ExtendDB coverage up to 2026-07-13 92% 96% 100% coverage - higher is better 24 May 26 May 9 Jun 18 Jun 21 Jun 23 Jun 27 Jun 30 Jun 2 Jul 13 Jul 95.1%
Implementing 95.1% of the suite as of 13 Jul, as little as 94.0% on 29 May. 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.