Skip to content

Ministack on

ministack.org github.com/ministackorg/ministack

9b67e6f8e53d as measured in this run

Grade C
high divergence
answers 17.6% of the suite differently from real DynamoDB
95.8% covered · 52 unsupported
Tier 1 · Core 5.6% diverges
100.0% covered
28 of 496 attempted
Tier 2 · Complete 25.5% diverges
89.6% covered 36 unsupported
88 of 309 attempted
Tier 3 · Strict 25.4% diverges
96.1% covered 16 unsupported
104 of 394 attempted

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-09-03 0% 20% 40% 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 17.6%
Diverging on 17.6% of the suite as of 3 Sep, 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-09-03 94% 97% 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 95.8%
Implementing 95.8% 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.