Skip to content

DynamoDB Local on

docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamoDBLocal.html

ff89bd48ff32 as measured in this run

Grade C
high divergence
answers 15.1% of the suite differently from real DynamoDB
93.8% covered · 65 unsupported
Tier 1 · Core 7.6% diverges
100.0% covered
37 of 489 attempted
Tier 2 · Complete 14.1% diverges
78.4% covered 49 unsupported
32 of 178 attempted
Tier 3 · Strict 26.5% diverges
95.3% covered 16 unsupported
90 of 324 attempted

How it got here

DynamoDB Local'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

DynamoDB Local divergence up to 2026-08-21 0% 13% 25% divergence - lower is better 27 Apr 26 May 18 Jun 23 Jun 30 Jun 13 Jul 17 Jul 22 Jul 29 Jul 13 Aug 21 Aug 15.1%
Diverging on 15.1% of the suite as of 21 Aug, at worst 17.8% on 30 Jun. Lower is better, so a falling line is a target getting closer to real DynamoDB.

Coverage

DynamoDB Local coverage up to 2026-08-21 92% 96% 100% coverage - higher is better 27 Apr 26 May 18 Jun 23 Jun 30 Jun 13 Jul 17 Jul 22 Jul 29 Jul 13 Aug 21 Aug 93.8%
Implementing 93.8% of the suite as of 21 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.