Skip to content

Dynalite on

github.com/architect/dynalite

4.0.0 as measured in this run

Grade C
high divergence
answers 16.2% of the suite differently from real DynamoDB
90.4% covered · 67 unsupported
Tier 1 · Core 4.5% diverges
100.0% covered
16 of 353 attempted
Tier 2 · Complete 40.9% diverges
49.2% covered 67 unsupported
54 of 65 attempted
Tier 3 · Strict 20.1% diverges
100.0% covered
43 of 214 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-09 0% 10% 20% divergence - lower is better 23 Mar 24 Apr 25 Apr 27 Apr 23 May 24 May 25 May 26 May 29 May 9 Jun 16.2%
Diverging on 16.2% of the suite as of 9 Jun. Lower is better, so a falling line is a target getting closer to real DynamoDB.

Coverage

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