Skip to content

LocalStack on

2026.10.7 as measured in this run

Grade D
very high divergence
answers 26.8% of the suite differently from real DynamoDB
96.2% covered · 73 unsupported
Tier 1 · Core 1.0% diverges
100.0% covered
5 of 507 attempted
Tier 2 · Complete 23.5% diverges
91.2% covered 47 unsupported
125 of 486 attempted
Tier 3 · Strict 43.8% diverges
97.0% covered 26 unsupported
385 of 854 attempted

How it got here

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

LocalStack divergence up to 2026-11-15 0% 15% 30% divergence - lower is better 23 Mar 23 May 9 Jun 22 Jun 30 Jun 14 Jul 20 Jul 28 Jul 13 Aug 23 Aug 20 Sep 22 Oct 15 Nov 26.8%
Diverging on 26.8% of the suite as of 15 Nov. Lower is better, so a falling line is a target getting closer to real DynamoDB.

Coverage

LocalStack coverage up to 2026-11-15 94% 97% 100% coverage - higher is better 23 Mar 23 May 9 Jun 22 Jun 30 Jun 14 Jul 20 Jul 28 Jul 13 Aug 23 Aug 20 Sep 22 Oct 15 Nov 96.2%
Implementing 96.2% of the suite as of 15 Nov, as little as 95.1% 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.