Skip to content

Ministack on

ministack.org github.com/ministackorg/ministack

f90981c85c9b as measured in this run

Grade A
low divergence
answers 0.1% of the suite differently from real DynamoDB
100.0% covered
Tier 1 · Core 0.0% diverges
100.0% covered
Tier 2 · Complete 0.3% diverges
100.0% covered
1 of 345 attempted
Tier 3 · Strict 0.0% diverges
100.0% covered

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-10-11 0% 20% 40% divergence - lower is better 23 May 29 May 19 Jun 24 Jun 1 Jul 14 Jul 18 Jul 24 Jul 2 Aug 15 Aug 23 Aug 13 Sep 11 Oct 0.1%
Diverging on 0.1% of the suite as of 11 Oct, 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-10-11 94% 97% 100% coverage - higher is better 23 May 29 May 19 Jun 24 Jun 1 Jul 14 Jul 18 Jul 24 Jul 2 Aug 15 Aug 23 Aug 13 Sep 11 Oct 100.0%
Implementing 100.0% of the suite as of 11 Oct, as little as 95.8% on 21 Aug. 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.