Skip to content

Floci on

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

f5aa8c18302c as measured in this run

Grade C
high divergence
answers 15.0% of the suite differently from real DynamoDB
95.3% covered · 59 unsupported
Tier 1 · Core 0.0% diverges
100.0% covered
Tier 2 · Complete 27.5% diverges
87.5% covered 43 unsupported
95 of 302 attempted
Tier 3 · Strict 22.7% diverges
96.1% covered 16 unsupported
93 of 394 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-09-20 0% 20% 40% divergence - lower is better 24 May 9 Jun 21 Jun 27 Jun 2 Jul 15 Jul 20 Jul 26 Jul 9 Aug 17 Aug 25 Aug 20 Sep 15.0%
Diverging on 15.0% of the suite as of 20 Sep, 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-09-20 92% 96% 100% coverage - higher is better 24 May 9 Jun 21 Jun 27 Jun 2 Jul 15 Jul 20 Jul 26 Jul 9 Aug 17 Aug 25 Aug 20 Sep 95.3%
Implementing 95.3% of the suite as of 20 Sep, as little as 95.0% 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.