Run
7 emulators 736 tests
Results as of this run. The arrow shows each target's movement since the previous run it was tested in. The suite grew this run, so an upward arrow can be the new tests biting rather than a target getting worse.
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.
Suite grew from 706 to 736 tests this run.
That's 30 new tests measured against every target. Movement below compares to the previous run, so a rise here is as likely to be the stricter suite as a real regression.
What changed in the suite this run
Suite on
Grew to 736 tests, up 30, covering what TransactWriteItems and BatchWriteItem do with an item whose key value is malformed - the wrong type, non-scalar, or an empty string - across both table and index keys. PutItem already covered this; the transactional and batch paths covered none of it.
Characterising it against real AWS turned up a split worth pinning. An empty-string key value is rejected by up-front input validation, so even inside a transaction it surfaces as a top-level ValidationException. A wrong-typed or non-scalar key value is caught while the transaction runs, so it comes back as a TransactionCanceledException carrying a ValidationError reason rather than a top-level error. BatchWriteItem has no cancellation path, so every variant there is a plain ValidationException. The tests pin both halves, which catches two opposite mistakes: an engine that wraps the empty-string case as a cancellation, and one that surfaces the type-mismatch case as a top-level error.
-
Grade baselineground truth
no divergence in all 33 regions · covers 100.0% of the suite
Tier breakdown
Tier 1 · Core 0.0% diverges100.0% coveredTier 2 · Complete 0.0% diverges100.0% coveredTier 3 · Strict 0.0% diverges100.0% covered -
Runs via: npx, Docker, Homebrew, binary, npm, cargo, embedded, GitHub Action, source
Disclosure: maintained by this board's author
Grade Bdiverged 3.5 percentage points morelow divergence (4.6%) · covers 98.1% of the suite · coverage lowers this row to B
Tier breakdown
Tier 1 · Core 2.7% diverges100.0% coveredTier 2 · Complete 5.7% diverges90.1% covered 14 unsupportedTier 3 · Strict 7.0% diverges100.0% covered -
Grade Bdiverged 2.9 percentage points more
moderate divergence (5.3%) · covers 94.3% of the suite
Tier breakdown
Tier 1 · Core 4.9% diverges100.0% coveredTier 2 · Complete 5.7% diverges70.2% covered 42 unsupportedTier 3 · Strict 5.7% diverges100.0% covered -
Grade Bdiverged 5.6 percentage points more
moderate divergence (9.0%) · covers 100.0% of the suite
Tier breakdown
Tier 1 · Core 9.0% diverges100.0% coveredTier 2 · Complete 12.1% diverges100.0% coveredTier 3 · Strict 7.0% diverges100.0% covered -
18c54f4a774a 9 unsupported ; covers 98.8% of the suite
Runs via: Docker, Homebrew, install script, Scoop, binary, JAR
Grade Bdiverged 3.5 percentage points moremoderate divergence (11.4%) · covers 98.8% of the suite
Tier breakdown
Tier 1 · Core 8.5% diverges100.0% coveredTier 2 · Complete 16.3% diverges93.6% covered 9 unsupportedTier 3 · Strict 13.1% diverges100.0% covered -
Grade Bdiverged 2.0 percentage points more
moderate divergence (13.5%) · covers 98.9% of the suite
Tier breakdown
Tier 1 · Core 2.2% diverges100.0% coveredTier 2 · Complete 8.5% diverges94.3% covered 8 unsupportedTier 3 · Strict 34.5% diverges100.0% covered -
Grade Cdiverged 1.9 percentage points more
moderate divergence (14.5%) · covers 98.2% of the suite · coverage lowers this row to C
Tier breakdown
Tier 1 · Core 3.6% diverges100.0% coveredTier 2 · Complete 11.3% diverges90.8% covered 13 unsupportedTier 3 · Strict 34.1% diverges100.0% covered -
Grade Cdiverged 2.1 percentage points more
high divergence (18.2%) · covers 90.9% of the suite
Tier breakdown
Tier 1 · Core 4.9% diverges100.0% coveredTier 2 · Complete 44.7% diverges52.5% covered 67 unsupportedTier 3 · Strict 23.1% diverges100.0% covered