Skip to content

ExtendDB on

extenddb.org github.com/ExtendDB/extenddb

v0.1.3 as measured in this run

Grade A
low divergence
answers 1.9% of the suite differently from real DynamoDB
91.3% covered · 87 unsupported
Tier 1 · Core 0.4% diverges
100.0% covered
2 of 475 attempted
Tier 2 · Complete 3.0% diverges
58.3% covered 83 unsupported
6 of 116 attempted
Tier 3 · Strict 3.4% diverges
98.8% covered 4 unsupported
11 of 320 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-08-12 0% 10% 20% divergence - lower is better 24 May 29 May 18 Jun 22 Jun 27 Jun 1 Jul 13 Jul 16 Jul 20 Jul 24 Jul 29 Jul 12 Aug 1.9%
Diverging on 1.9% of the suite as of 12 Aug, 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-08-12 90% 95% 100% coverage - higher is better 24 May 29 May 18 Jun 22 Jun 27 Jun 1 Jul 13 Jul 16 Jul 20 Jul 24 Jul 29 Jul 12 Aug 91.3%
Implementing 91.3% of the suite as of 12 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.