Skip to content

DynamoDB Local on

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

- as measured in this run

Grade B
moderate divergence
answers 11.8% of the suite differently from real DynamoDB
100.0% covered
Tier 1 · Core 1.0% diverges
100.0% covered
3 of 303 attempted
Tier 2 · Complete 8.7% diverges
100.0% covered
9 of 103 attempted
Tier 3 · Strict 30.3% diverges
100.0% covered
59 of 195 attempted

When this run was published the board led with a single correctness percentage. The figures here are that run's own results restated as divergence and coverage, so they read differently from what this page showed at the time. The changelog has the change.

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-04-27 0% 8% 15% divergence - lower is better 23 Mar 24 Apr 25 Apr 27 Apr 11.8%
Diverging on 11.8% of the suite as of 27 Apr. Lower is better, so a falling line is a target getting closer to real DynamoDB.

Coverage

DynamoDB Local coverage up to 2026-04-27 98% 99% 100% coverage - higher is better 23 Mar 24 Apr 25 Apr 27 Apr 100.0%
Implementing 100.0% of the suite as of 27 Apr. 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.