Dynoxide on 9 Aug 2026

dynoxide.dev github.com/nubo-db/dynoxide

0.13.0 as measured in this run

no divergence · coverage lowers this row to A

answers 0.0% of the suite differently from real DynamoDB

98.6% covered · 14 unsupported

Tier 1 · Core 0.0% diverges

100.0% covered

Tier 2 · Complete 0.0% diverges

93.0% covered 14 unsupported

Tier 3 · Strict 0.0% diverges

100.0% covered

When this run was published the board led with a single correctness percentage. The figures here are that run's own results restated as divergence and coverage, so they read differently from what this page showed at the time. The changelog has the change.

How it got here

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

Diverging on 0.0% of the suite as of 9 Aug, at worst 5.6% on 23 Jun. Lower is better, so a falling line is a target getting closer to real DynamoDB.

Coverage

Implementing 98.6% of the suite as of 9 Aug, as little as 98.0% on 26 May. 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.

Nothing failed in this run.