Run
7 emulators 744 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 736 to 744 tests this run.
That's 8 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 744 tests, up 8, pinning the Select / ProjectionExpression rules on Query and Scan. A ProjectionExpression is only valid with Select SPECIFIC_ATTRIBUTES, and ALL_PROJECTED_ATTRIBUTES is only valid with an IndexName; real DynamoDB rejects both with a ValidationException before reading anything. The cases span ALL_ATTRIBUTES, COUNT, and ALL_PROJECTED_ATTRIBUTES, including the request that breaks both rules at once, where AWS reports the ProjectionExpression one. They assert the contractual phrase, so they hold whether or not the engine carries the wrapper AWS adds on Query but not Scan.
-
live (AWS) full coverage100% ground truthTier 1 100%Tier 2 100%Tier 3 100%
-
94.2% -1.0pp fell 1.0 percentage pointsTier 1 95.2%Tier 2 93.7%Tier 3 93.0%
-
93.6% -0.8pp fell 0.8 percentage pointsTier 1 93.6%Tier 2 91.9%Tier 3 94.3%
-
78ee619e895a 9 unsupported ; covers 98.8% of the suite90.9% +2.4pp rose 2.4 percentage pointsTier 1 94.4%Tier 2 82.6%Tier 3 90.0%
-
a64f3c3bebff full coverage90.1% -1.0pp fell 1.0 percentage pointsTier 1 89.0%Tier 2 87.9%Tier 3 93.0%
-
86.5% +0.1pp rose 0.1 percentage pointsTier 1 97.9%Tier 2 91.0%Tier 3 65.5%
-
d89f8fcc6b1a 13 unsupported ; covers 98.3% of the suite85.4% +0.2pp rose 0.2 percentage pointsTier 1 96.5%Tier 2 87.5%Tier 3 65.9%
-
79.0% -0.9pp fell 0.9 percentage pointsTier 1 93.0%Tier 2 14.9%Tier 3 76.9%