Skip to content

Floci on

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

bec9b9f74932 as measured in this run

Grade C
high divergence
answers 21.0% of the suite differently from real DynamoDB
95.2% covered · 51 unsupported
Tier 1 · Core 10.8% diverges
100.0% covered
53 of 489 attempted
Tier 2 · Complete 32.4% diverges
84.4% covered 35 unsupported
73 of 190 attempted
Tier 3 · Strict 27.9% diverges
95.3% covered 16 unsupported
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-18 0% 20% 40% divergence - lower is better 27 Apr 25 May 9 Jun 19 Jun 23 Jun 29 Jun 2 Jul 14 Jul 17 Jul 21 Jul 26 Jul 2 Aug 13 Aug 18 Aug 21.0%
Diverging on 21.0% of the suite as of 18 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-18 94% 97% 100% coverage - higher is better 27 Apr 25 May 9 Jun 19 Jun 23 Jun 29 Jun 2 Jul 14 Jul 17 Jul 21 Jul 26 Jul 2 Aug 13 Aug 18 Aug 95.2%
Implementing 95.2% of the suite as of 18 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.