Skip to content

Ministack on

ministack.org github.com/ministackorg/ministack

63621de32116 as measured in this run

Grade B
moderate divergence
answers 11.2% of the suite differently from real DynamoDB
100.0% covered
Tier 1 · Core 3.2% diverges
100.0% covered
15 of 475 attempted
Tier 2 · Complete 17.1% diverges
100.0% covered
34 of 199 attempted
Tier 3 · Strict 19.4% diverges
100.0% covered
63 of 324 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-08-12 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 29 Jul 12 Aug 11.2%
Diverging on 11.2% of the suite as of 12 Aug, 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-08-12 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 29 Jul 12 Aug 100.0%
Implementing 100.0% of the suite as of 12 Aug, 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.