Skip to content

Kumo on

github.com/sivchari/kumo

9ae3cf4555ec as measured in this run

Grade F
severe divergence
answers 44.9% of the suite differently from real DynamoDB
78.5% covered · 272 unsupported
Tier 1 · Core 47.2% diverges
100.0% covered
234 of 496 attempted
Tier 2 · Complete 13.9% diverges
32.2% covered 234 unsupported
48 of 111 attempted
Tier 3 · Strict 67.3% diverges
91.1% covered 38 unsupported
286 of 387 attempted

How it got here

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

Kumo divergence up to 2026-09-29 0% 25% 50% divergence - lower is better 20 Sep 29 Sep 44.9%
Diverging on 44.9% of the suite as of 29 Sep, at worst 45.2% on 20 Sep. Lower is better, so a falling line is a target getting closer to real DynamoDB.

Coverage

Kumo coverage up to 2026-09-29 75% 88% 100% coverage - higher is better 20 Sep 29 Sep 78.5%
Implementing 78.5% of the suite as of 29 Sep, as little as 78.3% on 20 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.