Skip to content

Dynalite on

github.com/architect/dynalite

4.0.0 as measured in this run

Grade C
moderate divergence · coverage lowers this row to C
answers 11.5% of the suite differently from real DynamoDB
69.1% covered · 386 unsupported
Tier 1 · Core 10.7% diverges
100.0% covered
53 of 496 attempted
Tier 2 · Complete 8.1% diverges
11.6% covered 305 unsupported
28 of 40 attempted
Tier 3 · Strict 15.4% diverges
80.2% covered 81 unsupported
63 of 329 attempted

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-09-03 0% 15% 30% 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 3 Sep 11.5%
Diverging on 11.5% of the suite as of 3 Sep, at worst 22.9% on 1 Jul. Lower is better, so a falling line is a target getting closer to real DynamoDB.

Coverage

Dynalite coverage up to 2026-09-03 65% 83% 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 3 Sep 69.1%
Implementing 69.1% of the suite as of 3 Sep. 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.