Skip to content

Dynalite on

4.0.0 as measured in this run

Grade D
high divergence · coverage lowers this row to D
answers 15.9% of the suite differently from real DynamoDB
57.2% covered · 822 unsupported
Tier 1 · Core 11.2% diverges
100.0% covered
57 of 507 attempted
Tier 2 · Complete 5.3% diverges
7.5% covered 493 unsupported
28 of 40 attempted
Tier 3 · Strict 25.0% diverges
62.6% covered 329 unsupported
220 of 551 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-11-15 0% 15% 30% divergence - lower is better 23 May 9 Jun 22 Jun 30 Jun 14 Jul 20 Jul 28 Jul 13 Aug 23 Aug 20 Sep 22 Oct 15 Nov 15.9%
Diverging on 15.9% of the suite as of 15 Nov, 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-11-15 50% 75% 100% coverage - higher is better 23 May 9 Jun 22 Jun 30 Jun 14 Jul 20 Jul 28 Jul 13 Aug 23 Aug 20 Sep 22 Oct 15 Nov 57.2%
Implementing 57.2% of the suite as of 15 Nov. 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.