Skip to content

Dynoxide (wasm) on

github.com/nubo-db/dynoxide

1.3.0 as measured in this run

Grade A
no divergence · coverage lowers this row to A
answers 0.0% of the suite differently from real DynamoDB
88.0% covered · 152 unsupported
Tier 1 · Core 0.0% diverges
100.0% covered
Tier 2 · Complete 0.0% diverges
71.3% covered 99 unsupported
Tier 3 · Strict 0.0% diverges
87.5% covered 53 unsupported

How it got here

Dynoxide (wasm)'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

Dynoxide (wasm) divergence up to 2026-10-11 0% 1% 2% divergence - lower is better 12 Aug 15 Aug 18 Aug 23 Aug 30 Aug 13 Sep 29 Sep 11 Oct 0.0%
Diverging on 0.0% of the suite as of 11 Oct, at worst 0.9% on 12 Aug. Lower is better, so a falling line is a target getting closer to real DynamoDB.

Coverage

Dynoxide (wasm) coverage up to 2026-10-11 75% 88% 100% coverage - higher is better 12 Aug 15 Aug 18 Aug 23 Aug 30 Aug 13 Sep 29 Sep 11 Oct 88.0%
Implementing 88.0% of the suite as of 11 Oct, as little as 78.7% on 24 Jul. 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.