Skip to content

Floci on

floci.io/floci github.com/floci-io/floci

eab36252ea43 as measured in this run

Grade C
high divergence
answers 20.9% of the suite differently from real DynamoDB
99.1% covered · 9 unsupported
Tier 1 · Core 8.6% diverges
100.0% covered
41 of 475 attempted
Tier 2 · Complete 36.7% diverges
95.5% covered 9 unsupported
73 of 190 attempted
Tier 3 · Strict 29.3% diverges
100.0% covered
95 of 324 attempted

How it got here

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

Floci 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 20.9%
Diverging on 20.9% of the suite as of 12 Aug, at worst 37.1% on 27 Apr. Lower is better, so a falling line is a target getting closer to real DynamoDB.

Coverage

Floci coverage up to 2026-08-12 94% 97% 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 99.1%
Implementing 99.1% of the suite as of 12 Aug, as little as 95.8% 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.