Skip to content

Ministack on

c3c2e86f19ff as measured in this run

Grade C
high divergence
answers 18.0% of the suite differently from real DynamoDB
100.0% covered
Tier 1 · Core 10.9% diverges
100.0% covered
52 of 475 attempted
Tier 2 · Complete 29.6% diverges
100.0% covered
59 of 199 attempted
Tier 3 · Strict 21.3% diverges
100.0% covered
69 of 324 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

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

Ministack divergence up to 2026-07-24 0% 20% 40% divergence - lower is better 24 May 29 May 18 Jun 22 Jun 27 Jun 1 Jul 13 Jul 16 Jul 20 Jul 24 Jul 18.0%
Diverging on 18.0% of the suite as of 24 Jul, at worst 36.4% on 27 Apr. Lower is better, so a falling line is a target getting closer to real DynamoDB.

Coverage

Ministack coverage up to 2026-07-24 96% 98% 100% coverage - higher is better 24 May 29 May 18 Jun 22 Jun 27 Jun 1 Jul 13 Jul 16 Jul 20 Jul 24 Jul 100.0%
Implementing 100.0% of the suite as of 24 Jul, as little as 97.0% on 27 Apr. 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.