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.
How it got here
Dynoxide'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
Coverage
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.
-
PutItem - validation rejects a wrong-typed index key attribute
Tier 1 putItem tests/tier1/putItem/validation.test.ts:146
-
PutItem - validation rejects a non-scalar index key attribute
Tier 1 putItem tests/tier1/putItem/validation.test.ts:159
-
PutItem - validation rejects an empty-string index key attribute
Tier 1 putItem tests/tier1/putItem/validation.test.ts:175
-
Query - GSI sparse composite GSI: an item with the GSI hash key but no range key is excluded
Tier 1 query tests/tier1/query/gsi.test.ts:168
-
Scan - GSI sparse composite GSI: an item missing the GSI range key is not scanned
Tier 1 scan tests/tier1/scan/gsi.test.ts:166
-
PutItem - exact error messages NULL attr with false is accepted and normalises to NULL true
Tier 3 error-messages tests/tier3/error-messages/putItem.test.ts:161
-
PutItem - validation ordering empty TableName with invalid ReturnValues reports only tableName
Tier 3 validation-ordering tests/tier3/validation-ordering/putItem.test.ts:48
-
UpdateItem - validation ordering rejects invalid ReturnValues (UpdateItem reports the first enum error)
Tier 3 validation-ordering tests/tier3/validation-ordering/updateItem.test.ts:47