Run
7 emulators 762 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 a downward arrow can be the new tests biting rather than a target regressing.
Suite grew from 744 to 762 tests this run.
That's 18 new tests measured against every target. Movement below compares to the previous run, so a fall here is as likely to be the stricter suite as a real regression.
What changed in the suite this run
Suite on
Grew to 762 tests, up 18, covering a malformed value in the lookup Key of a TransactWriteItems Update, Delete, or ConditionCheck - the path a Put item key does not take. Captured across four regions (eu-west-2, us-east-1, ap-southeast-2, eu-central-1), where every string was identical, so they pin exactly. An empty-string Key surfaces as a top-level ValidationException with the same message a Put item key gives; a wrong-typed or non-scalar Key cancels with a ValidationError reason carrying "The provided key element does not match the schema" - the key-only form, not the "Type mismatch for key" message the item-key path returns. The same run confirmed the BatchWriteItem table-key schema-mismatch message is region-invariant.
-
live (AWS) full coverage100% ground truthTier 1 100%Tier 2 100%Tier 3 100%
-
99.7% +5.5pp rose 5.5 percentage pointsTier 1 100.0%Tier 2 100.0%Tier 3 99.2%
-
92.1% -1.5pp fell 1.5 percentage pointsTier 1 93.6%Tier 2 89.8%Tier 3 90.8%
-
45cc7b1398e0 full coverage90.0% 0.0pp unchangedTier 1 93.3%Tier 2 82.7%Tier 3 89.5%
-
78ee619e895a 9 unsupported ; covers 98.8% of the suite89.1% -1.8pp fell 1.8 percentage pointsTier 1 94.4%Tier 2 79.4%Tier 3 86.6%
-
85.8% -0.7pp fell 0.7 percentage pointsTier 1 97.9%Tier 2 89.4%Tier 3 64.7%
-
d89f8fcc6b1a 13 unsupported ; covers 98.3% of the suite84.5% -0.8pp fell 0.8 percentage pointsTier 1 96.5%Tier 2 86.1%Tier 3 64.7%
-
77.0% -2.0pp fell 2.0 percentage pointsTier 1 93.0%Tier 2 13.3%Tier 3 73.9%