Skip to content

Dynalite on

4.0.0 as measured in this run

Grade C
high divergence
answers 21.7% of the suite differently from real DynamoDB
91.8% covered · 67 unsupported
Tier 1 · Core 8.9% diverges
100.0% covered
37 of 417 attempted
Tier 2 · Complete 48.0% diverges
55.3% covered 67 unsupported
72 of 83 attempted
Tier 3 · Strict 27.2% diverges
100.0% covered
68 of 250 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

Dynalite'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

Dynalite divergence up to 2026-06-27 0% 13% 25% divergence - lower is better 24 Apr 27 Apr 24 May 26 May 9 Jun 18 Jun 21 Jun 23 Jun 27 Jun 21.7%
Diverging on 21.7% of the suite as of 27 Jun. Lower is better, so a falling line is a target getting closer to real DynamoDB.

Coverage

Dynalite coverage up to 2026-06-27 88% 94% 100% coverage - higher is better 24 Apr 27 Apr 24 May 26 May 9 Jun 18 Jun 21 Jun 23 Jun 27 Jun 91.8%
Implementing 91.8% of the suite as of 27 Jun, as little as 90.4% on 29 May. 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.