Skip to content

ExtendDB on

extenddb.org github.com/ExtendDB/extenddb

v0.1.13 as measured in this run

Grade C
moderate divergence · coverage lowers this row to C
answers 10.3% of the suite differently from real DynamoDB
70.0% covered · 504 unsupported
Tier 1 · Core 0.0% diverges
100.0% covered
Tier 2 · Complete 2.7% diverges
28.8% covered 322 unsupported
12 of 130 attempted
Tier 3 · Strict 21.9% diverges
75.0% covered 182 unsupported
160 of 547 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-10-22 0% 10% 20% divergence - lower is better 25 May 16 Jun 22 Jun 29 Jun 6 Jul 16 Jul 21 Jul 28 Jul 12 Aug 18 Aug 30 Aug 29 Sep 22 Oct 10.3%
Diverging on 10.3% of the suite as of 22 Oct, 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-10-22 65% 83% 100% coverage - higher is better 25 May 16 Jun 22 Jun 29 Jun 6 Jul 16 Jul 21 Jul 28 Jul 12 Aug 18 Aug 30 Aug 29 Sep 22 Oct 70.0%
Implementing 70.0% of the suite as of 22 Oct. 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.