Skip to content

ExtendDB on

extenddb.org github.com/ExtendDB/extenddb

v0.1.10 as measured in this run

Grade B
low divergence · coverage lowers this row to B
answers 1.8% of the suite differently from real DynamoDB
78.7% covered · 267 unsupported
Tier 1 · Core 0.0% diverges
100.0% covered
Tier 2 · Complete 0.0% diverges
33.6% covered 229 unsupported
Tier 3 · Strict 5.6% diverges
90.7% covered 38 unsupported
23 of 372 attempted

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-09-03 0% 10% 20% divergence - lower is better 26 May 18 Jun 23 Jun 30 Jun 13 Jul 17 Jul 22 Jul 29 Jul 13 Aug 21 Aug 3 Sep 1.8%
Diverging on 1.8% of the suite as of 3 Sep, at worst 16.2% on 16 Jul. Lower is better, so a falling line is a target getting closer to real DynamoDB.

Coverage

ExtendDB coverage up to 2026-09-03 75% 88% 100% coverage - higher is better 26 May 18 Jun 23 Jun 30 Jun 13 Jul 17 Jul 22 Jul 29 Jul 13 Aug 21 Aug 3 Sep 78.7%
Implementing 78.7% of the suite as of 3 Sep. 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.