Skip to content

Ministack on

ministack.org github.com/ministackorg/ministack

latest (89d602080662) as measured in this run

Grade D
very high divergence
answers 31.6% of the suite differently from real DynamoDB
100.0% covered
Tier 1 · Core 14.2% diverges
100.0% covered
43 of 303 attempted
Tier 2 · Complete 23.3% diverges
100.0% covered
24 of 103 attempted
Tier 3 · Strict 63.1% diverges
100.0% covered
123 of 195 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-05-23 0% 20% 40% divergence - lower is better 27 Apr 23 May 31.6%
Diverging on 31.6% of the suite as of 23 May, 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-05-23 96% 98% 100% coverage - higher is better 27 Apr 23 May 100.0%
Implementing 100.0% of the suite as of 23 May, 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.