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.2% of the suite differently from real DynamoDB
94.0% covered · 63 unsupported
Tier 1 · Core 7.6% diverges
100.0% covered
37 of 489 attempted
Tier 2 · Complete 14.2% diverges
79.1% covered 47 unsupported
32 of 178 attempted
Tier 3 · Strict 26.8% diverges
95.3% covered 16 unsupported
91 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-13 0% 13% 25% divergence - lower is better 23 Mar 27 Apr 25 May 9 Jun 19 Jun 23 Jun 29 Jun 2 Jul 14 Jul 17 Jul 21 Jul 26 Jul 2 Aug 13 Aug 15.2%
Diverging on 15.2% of the suite as of 13 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-13 92% 96% 100% coverage - higher is better 23 Mar 27 Apr 25 May 9 Jun 19 Jun 23 Jun 29 Jun 2 Jul 14 Jul 17 Jul 21 Jul 26 Jul 2 Aug 13 Aug 94.0%
Implementing 94.0% of the suite as of 13 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.