Skip to content

ExtendDB on

extenddb.org github.com/ExtendDB/extenddb

v0.1.1 as measured in this run

Grade A
low divergence
answers 2.0% of the suite differently from real DynamoDB
94.0% covered · 42 unsupported
Tier 1 · Core 2.8% diverges
100.0% covered
10 of 353 attempted
Tier 2 · Complete 1.5% diverges
68.2% covered 42 unsupported
2 of 90 attempted
Tier 3 · Strict 0.9% diverges
100.0% covered
2 of 214 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-06-09 0% 4% 8% divergence - lower is better 23 May 24 May 25 May 26 May 29 May 9 Jun 2.0%
Diverging on 2.0% of the suite as of 9 Jun, at worst 6.0% on 26 May. Lower is better, so a falling line is a target getting closer to real DynamoDB.

Coverage

ExtendDB coverage up to 2026-06-09 92% 96% 100% coverage - higher is better 23 May 24 May 25 May 26 May 29 May 9 Jun 94.0%
Implementing 94.0% of the suite as of 9 Jun. 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.