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 13.0% of the suite differently from real DynamoDB
77.0% covered · 242 unsupported
Tier 1 · Core 10.8% diverges
100.0% covered
53 of 489 attempted
Tier 2 · Complete 12.4% diverges
17.8% covered 185 unsupported
28 of 40 attempted
Tier 3 · Strict 16.5% diverges
83.2% covered 57 unsupported
56 of 283 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-08-13 0% 15% 30% 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 13.0%
Diverging on 13.0% of the suite as of 13 Aug, 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-08-13 70% 85% 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 77.0%
Implementing 77.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.