Skip to content
Grade D
very high divergence
answers 26.0% of the suite differently from real DynamoDB
up to 26.1% in the others
100.0% of the suite implemented
Tier 1 · Core 3.9% diverges
100.0% covered
20 of 507 attempted
Tier 2 · Complete 24.8% diverges
100.0% covered
132 of 533 attempted
Tier 3 · Strict 39.4% diverges
100.0% covered
347 of 880 attempted

How to run it

Every way AWS Emulator is distributed, each linking to the project's own documentation for it. These are the project's claims, not the suite's measurements.

Needs: Linux for the native package; elsewhere Docker, with an image you build

Licence: CC0-1.0 AND Apache-2.0, licence of AWS Emulator (opens in a new tab)

DynamoDB is one of the many AWS services it serves. No image is published; the Docker route builds one from a Dockerfile in its user guide. HTTPS and SigV4 are on by default, and it listens on 9297.

Per-region divergence

The headline is eu-west-2 + 30 regions, measured against 31 of 32 observed regions, and scored in ap-east-1. Real DynamoDB doesn't behave identically in every region, so a target can match some regions more closely than others. Each figure below is divergence in those regions, best first. eu-west-2 is marked as the historical baseline, and a region that couldn't be resolved this sweep is flagged rather than counted as a disagreement.

26.0% 9 regions
ap-east-1ap-southeast-2ca-west-1eu-south-2eu-west-3mx-central-1us-east-1us-west-1us-west-2
26.0% 22 regions
af-south-1ap-east-2ap-northeast-1ap-northeast-2ap-northeast-3ap-south-1ap-south-2ap-southeast-1ap-southeast-3ap-southeast-4ap-southeast-5ap-southeast-6ap-southeast-7ca-central-1eu-central-1eu-central-2eu-south-1eu-west-1eu-west-2 · baselineil-central-1sa-east-1us-east-2
26.1% 1 region
eu-north-1

Feature support

Measured across the suite's tests for each feature. Compare with other emulators.

AWS Emulator 1.0.385

Core DynamoDB

Vector search
AWS Emulator Vector search: partially supported (33 pass, 25 fail)
GSI
AWS Emulator GSI: partially supported (187 pass, 47 fail)
LSI
AWS Emulator LSI: partially supported (150 pass, 39 fail)
PartiQL
AWS Emulator PartiQL: partially supported (326 pass, 230 fail)
Transactions
AWS Emulator Transactions: partially supported (144 pass, 40 fail)
Streams
AWS Emulator Streams: supported (18 pass)
TTL
AWS Emulator TTL: supported (7 pass)
Legacy params
AWS Emulator Legacy params: partially supported (54 pass, 80 fail)

Other AWS services

Backups / PITR
AWS Emulator Backups / PITR: supported (5 pass)
Export / import
AWS Emulator Export / import: supported (2 pass)
Kinesis
AWS Emulator Kinesis: failing (1 fail)
Resource policies
AWS Emulator Resource policies: supported (2 pass)
Contributor Insights
AWS Emulator Contributor Insights: supported (2 pass)
Account API
AWS Emulator Account API: supported (2 pass)

Fully supports

Operation areas this target implements completely - every test passes, nothing skipped. Areas it only partly gets wrong are in “Where it falls short” below; the ones it only partly attempts are in “What it doesn’t attempt”.

  • batchGetItem tier 1
  • batchWriteItem tier 1
  • deleteItem tier 1
  • deleteTable tier 1
  • describeTable tier 1
  • listTables tier 1
  • scan tier 1
  • updateTable tier 1
  • account tier 2
  • backups tier 2
  • contributorInsights tier 2
  • export tier 2
  • multiAttributeKeys tier 2
  • resourcePolicy tier 2
  • streams tier 2
  • ttl tier 2
  • legacy-api tier 3
Only one run recorded so far. The history charts appear once a second run lands.

By operation

Every operation this target implements, with how much of it diverges and how much of it it covers, on the same two axes as the figures above. The counts are fails over the operation's whole size. full, partial, failing, unsupported, not scored. The emulator directory lists support across targets.

Tier 1 - Core

  • batchGetItem 0/15 0.0% 100.0% batchGetItem: supported, diverges on 0.0% of it, covers 100.0% (15 pass)
  • batchWriteItem 0/18 0.0% 100.0% batchWriteItem: supported, diverges on 0.0% of it, covers 100.0% (18 pass)
  • createTable 1/30 3.3% 100.0% createTable: partially supported, diverges on 3.3% of it, covers 100.0% (29 pass, 1 fail)
  • deleteItem 0/13 0.0% 100.0% deleteItem: supported, diverges on 0.0% of it, covers 100.0% (13 pass)
  • deleteTable 0/3 0.0% 100.0% deleteTable: supported, diverges on 0.0% of it, covers 100.0% (3 pass)
  • describeTable 0/4 0.0% 100.0% describeTable: supported, diverges on 0.0% of it, covers 100.0% (4 pass)
  • getItem 5/39 12.8% 100.0% getItem: partially supported, diverges on 12.8% of it, covers 100.0% (34 pass, 5 fail)
  • listTables 0/5 0.0% 100.0% listTables: supported, diverges on 0.0% of it, covers 100.0% (5 pass)
  • putItem 5/130 3.8% 100.0% putItem: partially supported, diverges on 3.8% of it, covers 100.0% (125 pass, 5 fail)
  • query 7/99 7.1% 100.0% query: partially supported, diverges on 7.1% of it, covers 100.0% (92 pass, 7 fail)
  • scan 0/60 0.0% 100.0% scan: supported, diverges on 0.0% of it, covers 100.0% (60 pass)
  • updateItem 2/76 2.6% 100.0% updateItem: partially supported, diverges on 2.6% of it, covers 100.0% (74 pass, 2 fail)
  • updateTable 0/15 0.0% 100.0% updateTable: supported, diverges on 0.0% of it, covers 100.0% (15 pass)

Tier 2 - Complete

  • account 0/2 0.0% 100.0% account: supported, diverges on 0.0% of it, covers 100.0% (2 pass)
  • backups 0/5 0.0% 100.0% backups: supported, diverges on 0.0% of it, covers 100.0% (5 pass)
  • contributorInsights 0/2 0.0% 100.0% contributorInsights: supported, diverges on 0.0% of it, covers 100.0% (2 pass)
  • export 0/2 0.0% 100.0% export: supported, diverges on 0.0% of it, covers 100.0% (2 pass)
  • kinesis 1/1 100.0% 100.0% kinesis: failing, diverges on 100.0% of it, covers 100.0% (1 fail)
  • multiAttributeKeys 0/14 0.0% 100.0% multiAttributeKeys: supported, diverges on 0.0% of it, covers 100.0% (14 pass)
  • partiql 112/356 31.5% 100.0% partiql: partially supported, diverges on 31.5% of it, covers 100.0% (244 pass, 112 fail)
  • resourcePolicy 0/2 0.0% 100.0% resourcePolicy: supported, diverges on 0.0% of it, covers 100.0% (2 pass)
  • streams 0/18 0.0% 100.0% streams: supported, diverges on 0.0% of it, covers 100.0% (18 pass)
  • tags 1/8 12.5% 100.0% tags: partially supported, diverges on 12.5% of it, covers 100.0% (7 pass, 1 fail)
  • transactions 2/62 3.2% 100.0% transactions: partially supported, diverges on 3.2% of it, covers 100.0% (60 pass, 2 fail)
  • ttl 0/7 0.0% 100.0% ttl: supported, diverges on 0.0% of it, covers 100.0% (7 pass)
  • updateTable 1/14 7.1% 100.0% updateTable: partially supported, diverges on 7.1% of it, covers 100.0% (13 pass, 1 fail)
  • vectorSearch 15/40 37.5% 100.0% vectorSearch: partially supported, diverges on 37.5% of it, covers 100.0% (25 pass, 15 fail)

Tier 3 - Strict

  • error-messages 180/451 39.9% 100.0% error-messages: partially supported, diverges on 39.9% of it, covers 100.0% (271 pass, 180 fail)
  • legacy-api 0/42 0.0% 100.0% legacy-api: supported, diverges on 0.0% of it, covers 100.0% (42 pass)
  • limits 67/214 31.3% 100.0% limits: partially supported, diverges on 31.3% of it, covers 100.0% (147 pass, 67 fail)
  • validation-ordering 101/173 58.4% 100.0% validation-ordering: partially supported, diverges on 58.4% of it, covers 100.0% (72 pass, 101 fail)

Where it falls short

Operations AWS Emulator implements and answers differently from real DynamoDB, biggest gap first. This is what its divergence figure counts. Open one for the exact tests, or see the conformance suite.

  • error-messages Tier 3 180 diverging
    View these tests in the suite →
    • BatchWriteItem - exact error messages empty RequestItems: full required-parameter error source:44
    • BatchWriteItem - exact error messages > 25 requests: anchored regex on the constraint phrase source:91
    • BatchWriteItem - exact error messages empty request list for a table: exact constraint message source:239
    • Table and index operations measure a name table names, in UTF-16 units CreateTable does not find two emoji too short source:76
    • Table and index operations measure a name table names, in UTF-16 units CreateTable finds 128 emoji too long source:80
    • Table and index operations measure a name table names, in UTF-16 units DescribeTable does not find two emoji too short source:86
    • Table and index operations measure a name table names, in UTF-16 units DescribeTable finds 128 emoji too long source:90
    • Table and index operations measure a name table names, in UTF-16 units DeleteTable does not find two emoji too short source:96
    • Table and index operations measure a name table names, in UTF-16 units DeleteTable finds 128 emoji too long source:100
    • Table and index operations measure a name table names, in UTF-16 units UpdateTable does not find two emoji too short source:106
    • Table and index operations measure a name table names, in UTF-16 units UpdateTable finds 128 emoji too long source:110
    • Table and index operations measure a name ListTables and index names, in characters ListTables does not find 128 emoji too long source:161
    • Table and index operations measure a name ListTables and index names, in characters CreateTable does not find a GSI name of 128 emoji too long source:176
    • Table and index operations measure a name ListTables and index names, in characters CreateTable does not find an LSI name of 128 emoji too long source:191
    • Table and index operations measure a name ListTables and index names, in characters UpdateTable does not find a new GSI name of 128 emoji too long source:202
    • CreateTable - exact error messages more than 2 KeySchema elements source:112
    • CreateTable - exact error messages invalid AttributeType source:158
    • CreateTable - exact error messages LSI without range key on base table source:189
    • CreateTable - exact error messages duplicate index names source:233
    • DeleteItem - request validation envelope every malformed Expected condition source:154
    • GetItem - exact error messages invalid ProjectionExpression syntax: full parser error source:69
    • Leading underscore - exact error messages in a Query FilterExpression source:28
    • Leading underscore - exact error messages in a Scan FilterExpression source:28
    • Leading underscore - exact error messages in a ProjectionExpression source:28
    • Leading underscore - exact error messages as the partition key in a KeyConditionExpression source:69
    • Leading underscore - exact error messages inside begins_with in a KeyConditionExpression source:83
    • Leading underscore - exact error messages in a KeyConditionExpression on an index source:99
    • Leading underscore - exact error messages in a ConditionExpression source:28
    • Leading underscore - exact error messages in an UpdateExpression source:28
    • PartiQL - exact error messages DELETE RETURNING MODIFIED OLD * - exact message source:47
    • PartiQL - exact error messages ExecuteTransaction with a RETURNING member - exact message source:94
    • PartiQL functions - exact error messages EXISTS(path) in a WHERE is not a function - exact message source:76
    • PartiQL functions - exact error messages a path through an attribute named inner - exact message source:76
    • PartiQL functions - exact error messages a SELECT in ExecuteTransaction whose WHERE uses attribute_exists - exact message source:131
    • PartiQL functions - exact error messages a SELECT in BatchExecuteStatement whose WHERE uses attribute_exists - exact message source:144
    • PartiQL functions - exact error messages EXISTS(SELECT ...) with no further condition in ExecuteTransaction - exact message source:160
    • PartiQL functions - exact error messages set_add assigned to another attribute - exact message source:76
    • PartiQL functions - exact error messages set_add whose first argument is not a path - exact message source:76
    • PartiQL functions - exact error messages set_add with a string to add - exact message source:76
    • PartiQL functions - exact error messages set_add with a list to add - exact message source:76
    • PartiQL functions - exact error messages set_add with one argument - exact message source:76
    • PartiQL functions - exact error messages set_add with three arguments - exact message source:76
    • PartiQL functions - exact error messages set_add of a set literal with a repeated member - exact message source:76
    • PartiQL functions - exact error messages set_add of an empty set literal - exact message source:76
    • PartiQL functions - exact error messages set_add on a path through an attribute named inner - exact message source:76
    • PartiQL functions - exact error messages set_add in a SELECT WHERE - exact message source:76
    • PartiQL functions - exact error messages set_add in an INSERT value - exact message source:76
    • PartiQL functions - exact error messages set_delete assigned to another attribute - exact message source:76
    • PartiQL functions - exact error messages set_delete with a string to remove - exact message source:76
    • PartiQL grammar - exact error messages an exponent that does not fit a 32-bit integer - nothing after the colon source:69
    • PartiQL grammar - exact error messages a far larger exponent - nothing after the colon source:69
    • PartiQL grammar - exact error messages an exponent that fits but leaves a scale that does not - nothing after the colon source:69
    • PartiQL grammar - exact error messages a hash comment - nothing after the colon source:69
    • PartiQL grammar - exact error messages an unterminated block comment - nothing after the colon source:69
    • PartiQL grammar - exact error messages an alias on an INSERT is a leftover token - exact message source:69
    • PartiQL grammar - exact error messages a WHERE literal above the largest number - exact message source:69
    • PartiQL grammar - exact error messages a WHERE literal below the smallest number - exact message source:69
    • PartiQL grammar - exact error messages a WHERE literal with 39 significant digits - exact message source:69
    • PartiQL grammar - exact error messages an INSERT literal above the largest number - exact message source:69
    • PartiQL grammar - exact error messages an UPDATE SET literal below the smallest number - exact message source:69
    • PartiQL grammar - exact error messages a literal inside a map names its path - exact message source:69
    • PartiQL grammar - exact error messages a literal inside a list names its index - exact message source:69
    • PartiQL grammar - exact error messages a condition ending in AND - exact message source:69
    • PartiQL grammar - exact error messages a condition ending in OR - exact message source:69
    • PartiQL grammar - exact error messages IS INT4 parses as a type test - exact message source:69
    • PartiQL grammar - exact error messages IS INT8 parses as a type test - exact message source:69
    • PartiQL grammar - exact error messages IS DOUBLE PRECISION parses as a type test - exact message source:69
    • PartiQL grammar - exact error messages IS CHARACTER VARYING parses as a type test - exact message source:69
    • PartiQL grammar - exact error messages IS with a name that is not a type, in a WHERE - exact message source:69
    • PartiQL grammar - exact error messages IS where a WHERE condition should start - exact message source:69
    • PartiQL grammar - exact error messages LIKE where a comparison operand should start - exact message source:69
    • PartiQL grammar - exact error messages DELETE FROM with no table - exact message source:69
    • PartiQL grammar - exact error messages DELETE FROM then spaces with no table - exact message source:69
    • PartiQL grammar - exact error messages DELETE FROM then WHERE with no table - exact message source:69
    • PartiQL grammar - exact error messages FROM ... SET with no WHERE - exact message source:69
    • PartiQL grammar - exact error messages FROM ... REMOVE with no WHERE - exact message source:69
    • PartiQL grammar - exact error messages FROM ... WHERE on a non-key attribute ... SET - exact message source:69
    • PartiQL grammar - exact error messages FROM ... SET with the WHERE after it - exact message source:69
    • PartiQL grammar - exact error messages FROM ... SET ... WHERE ... SET - exact message source:69
    • PartiQL grammar - exact error messages FROM ... WHERE ... SET on a table that does not exist - exact error source:302
    • PartiQL grammar - exact error messages an OR branch with a non-key equality beside a sort-key branch - exact message source:58
    • PartiQL grammar - exact error messages an OR branch with a non-key <> beside a sort-key branch - exact message source:58
    • PartiQL grammar - exact error messages OR branches whose sort-key ranges meet - exact message source:58
    • PartiQL grammar - exact error messages an OR beside a sort-key equality with a non-key branch - exact message source:58
    • PartiQL grammar - exact error messages 1 (NOT sk = ... OR x = ...) pairs - exact message source:58
    • PartiQL grammar - exact error messages 2 (NOT sk = ... OR x = ...) pairs - exact message source:58
    • PartiQL grammar - exact error messages 9 (NOT sk = ... OR x = ...) pairs - exact message source:58
    • PartiQL grammar - exact error messages a partition key given a boolean - exact message source:69
    • PartiQL grammar - exact error messages a partition key given a boolean beside two sort-key equalities - exact message source:69
    • PartiQL grammar - exact error messages ORDER BY over two branches on one partition - exact message source:69
    • PartiQL grammar - exact error messages ORDER BY over a literal branch and a parameter branch on one partition - exact message source:69
    • PartiQL grammar - exact error messages ORDER BY on the sort key over two partitions - exact message source:69
    • PartiQL grammar - exact error messages a Limit sent as a string - exact error source:427
    • PartiQL index qualifier - exact error messages unprojected projection attribute on a GSI - exact message source:24
    • PartiQL index qualifier - exact error messages unprojected projection attribute on an unkeyed GSI scan - exact message source:24
    • PartiQL index qualifier - exact error messages two unprojected projection attributes on a GSI, named as listed - the same list source:24
    • PartiQL index qualifier - exact error messages two unprojected projection attributes on a GSI, named reversed - the same list source:24
    • PartiQL - multi-attribute index exact error messages a SELECT on a GSI with two HASH and two RANGE attributes - exact message source:96
    • PartiQL - multi-attribute index exact error messages a SELECT on a GSI with two HASH attributes and one RANGE - exact message source:96
    • PartiQL - multi-attribute index exact error messages a SELECT with ORDER BY on a multi-attribute GSI - exact message source:107
    • PartiQL - multi-attribute index exact error messages a number literal that cannot be converted is reported ahead of the refusal source:107
    • PartiQL - multi-attribute index exact error messages a parameter that cannot be converted to a number is reported ahead of the refusal source:107
    • PartiQL - multi-attribute index exact error messages the refusal is reported ahead of a key type mismatch, a non-key WHERE, a missing WHERE and COUNT(*) source:107
    • PartiQL - multi-attribute index exact error messages in a BatchExecuteStatement only the statement reading the index fails, ahead of the key-only rule source:169
    • PartiQL parameters - numbers - exact error messages the parameter 1e99999999999 in a WHERE comparison cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e99999999999 in an INSERT value cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e99999999999 in an UPDATE SET cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e99999999999 in a key cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter -1e99999999999 in a WHERE comparison cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter -1e99999999999 in an INSERT value cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter -1e99999999999 in an UPDATE SET cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter -1e99999999999 in a key cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e-99999999999 in a WHERE comparison cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e-99999999999 in an INSERT value cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e-99999999999 in an UPDATE SET cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e-99999999999 in a key cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e2147483648 in a WHERE comparison cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e2147483648 in an INSERT value cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e2147483648 in an UPDATE SET cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e2147483648 in a key cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e-2147483648 in a WHERE comparison cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e-2147483648 in an INSERT value cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e-2147483648 in an UPDATE SET cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e-2147483648 in a key cannot be converted - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e2147483647 in a WHERE comparison underflows - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e2147483647 in an INSERT value underflows - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e2147483647 in an UPDATE SET underflows - exact message source:66
    • PartiQL parameters - numbers - exact error messages the parameter 1e2147483647 in a key underflows - exact message source:66
    • PartiQL parameters - numbers - exact error messages an unconvertible number inside a list parameter - exact message source:66
    • PartiQL parameters - numbers - exact error messages an unconvertible number inside a map parameter - exact message source:66
    • PartiQL parameters - numbers - exact error messages an unconvertible member of a number set parameter - exact message source:66
    • PartiQL parameters - numbers - exact error messages an unconvertible number in ExecuteTransaction - exact message source:123
    • PartiQL parameters - numbers - exact error messages an unconvertible number in BatchExecuteStatement - exact message source:133
    • PartiQL parameters - numbers - exact error messages nested 40 levels an unconvertible member of a map before a deep one - exact message source:66
    • PartiQL parameters - numbers - exact error messages nested 100 levels a deep parameter before an unconvertible one - exact message source:66
    • PartiQL parameters - numbers - exact error messages nested 100 levels an unconvertible parameter before a deep one - exact message source:66
    • PartiQL parameters - numbers - exact error messages nested 100 levels a deep member of a map before an unconvertible one - exact message source:66
    • PartiQL parameters - numbers - exact error messages nested 100 levels an unconvertible member of a map before a deep one - exact message source:66
    • PartiQL parameters - numbers - exact error messages nested 100 levels an unconvertible number at the bottom of a deep value - exact message source:66
    • PartiQL parameters - numbers - exact error messages nested 100 levels a deep parameter before one past the largest number - exact message source:66
    • PartiQL parameters - numbers - exact error messages nested 100 levels a deep parameter before an unconvertible one, in ExecuteTransaction - exact message source:178
    • PartiQL parameters - numbers - exact error messages nested 100 levels a deep parameter before an unconvertible one, in BatchExecuteStatement - exact message source:183
    • PutItem - exact error messages missing table name: full validation error string source:37
    • PutItem - exact error messages contains() with duplicate path and operand: full distinct-operand error source:350
    • Query - exact error messages invalid Select value source:90
    • Query - exact error messages empty KeyConditionExpression source:129
    • Query - exact error messages redundant parentheses in KeyConditionExpression: full error string source:166
    • Query - KeyConditionExpression operand types equality with a boolean fails the schema check - exact message source:46
    • Query - KeyConditionExpression operand types two conditions on the sort key - exact message source:46
    • SearchVectors - exact error messages TopK above the maximum source:38
    • SearchVectors - exact error messages non-equality comparator on the HASH element source:40
    • SearchVectors - exact error messages condition attribute outside the SearchSchema source:40
    • SearchVectors - exact error messages L-wrapped search vector source:40
    • SearchVectors - request shape errors refuses an explicit null member as a SerializationException source:222
    • SearchVectors - request shape errors names a missing TableName as a missing field, before a too-short IndexName source:235
    • Item operations count a table name in characters, split by region UpdateItem finds two emoji too short, after the pattern source:82
    • TransactGetItems - exact error messages invalid ProjectionExpression syntax: full parser error source:115
    • TransactGetItems - exact error messages missing key attribute: action-level ValidationError surfaces as TransactionCanceledException source:140
    • TransactGetItems - exact error messages malformed table name: top-level ValidationException naming the member source:166
    • TransactGetItems - exact error messages malformed table name on the second Get: the message names its position source:186
    • TransactWriteItems - exact error messages action with no operation: top-level message source:491
    • UpdateItem - exact error messages invalid UpdateExpression syntax source:68
    • Number values - messages by operation DeleteItem refuses a malformed number in a condition value and in the key inside the envelope, with no wrapper source:169
    • Number values - messages by operation GetItem, BatchGetItem and Query refuse a malformed number bare, in the current wording source:185
    • Number values - messages by operation BatchWriteItem refuses a malformed number bare, in one layer for every shape source:191
    • Number values - transactions by region TransactWriteItems refuses a malformed number in a Put item up front source:220
    • Number values - transactions by region TransactWriteItems refuses a malformed number in an Update value up front source:233
    • Duplicate set members - messages by operation PutItem refuses a duplicate in an item, a condition value and an Expected value inside the envelope source:290
    • Duplicate set members - messages by operation UpdateItem refuses a duplicate in a condition value, AttributeUpdates and the key inside the envelope source:312
    • Duplicate set members - messages by operation DeleteItem refuses a duplicate in the key inside the envelope source:317
    • Duplicate set members - messages by operation GetItem and BatchGetItem refuse a duplicate in the key bare, in the current wording source:323
    • Duplicate set members - messages by operation Query refuses a duplicate in a key value, a filter value, ExclusiveStartKey and QueryFilter bare, with no wrapper source:354
    • Duplicate set members - messages by operation BatchWriteItem refuses a duplicate in an item and a delete key bare, in one layer for both source:370
    • Duplicate set members - transactions by region TransactWriteItems refuses a duplicate in a Put item and a Delete key up front source:388
    • Duplicate set members - transactions by region TransactWriteItems refuses a duplicate in a condition or update value of every action type up front source:406
    • Duplicate set members - transactions by region TransactGetItems refuses a duplicate in a key up front source:413
    • CreateTable vector indexes - exact error messages SearchSchema attribute missing from AttributeDefinitions source:48
    • CreateTable vector indexes - exact error messages more vector indexes than the per-table limit source:46
    • CreateTable vector indexes - exact error messages two indexes on one attribute with different Dimensions source:46
    • PutItem vector writes - exact error messages empty string in the SearchSchema HASH attribute source:29
  • partiql Tier 2 112 diverging
    View these tests in the suite →
    • BatchExecuteStatement - PartiQL surfaces an invalid RETURNING variant on a member DELETE as a per-statement error source:267
    • BatchExecuteStatement - PartiQL surfaces a malformed member statement as a per-statement ValidationError without failing the batch source:299
    • BatchExecuteStatement - PartiQL a failed member echoes its table only if it ran omits TableName on a member rejected before it ran source:485
    • ExecuteStatement - PartiQL DELETE on a missing key with a non-key predicate is a silent no-op source:572
    • ExecuteStatement - PartiQL DELETE RETURNING ALL OLD * on a missing item returns an empty Items list source:620
    • ExecuteStatement - PartiQL DELETE rejects RETURNING MODIFIED OLD * (only ALL OLD * is valid on DELETE) source:637
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * over multiple list indices returns a dense pack of the changed elements source:1034
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED OLD * over multiple list indices returns the prior elements densely source:1061
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * packs changed indices in ascending index order, not statement order source:1083
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED OLD * packs changed indices in ascending index order, not statement order source:1109
    • ExecuteStatement - PartiQL Limit a Limit at or past the 32-bit range returns the whole partition on one page source:1386
    • ExecuteStatement - PartiQL Limit a Limit near the 64-bit range returns a whole set of keys on one page source:1394
    • ExecuteStatement - PartiQL Limit a Limit written with an exponent or past 64 bits returns the whole partition on one page source:1402
    • ExecuteStatement - PartiQL Limit a Limit of 1.5 reads as 1, one row a page source:1415
    • ExecuteTransaction - PartiQL rejects a RETURNING clause inside a transaction statement source:207
    • PartiQL - FROM-first UPDATE FROM ... WHERE ... SET updates the item source:77
    • PartiQL - FROM-first UPDATE FROM ... WHERE ... REMOVE removes the attribute source:83
    • PartiQL - FROM-first UPDATE SET and REMOVE can follow each other source:89
    • PartiQL - FROM-first UPDATE RETURNING ALL NEW * returns the updated item source:95
    • PartiQL - FROM-first UPDATE the keywords are case-insensitive source:101
    • PartiQL - FROM-first UPDATE takes parameters source:107
    • PartiQL - FROM-first UPDATE a further condition in the WHERE that holds lets the update through source:113
    • PartiQL - FROM-first UPDATE a further condition in the WHERE that fails stops the update source:119
    • PartiQL - FROM-first UPDATE a key that matches no item fails its condition and creates nothing source:128
    • PartiQL - FROM-first UPDATE ExecuteTransaction runs it source:137
    • PartiQL - FROM-first UPDATE BatchExecuteStatement runs it source:149
    • PartiQL - grammar a number with no leading digit matches in WHERE source:84
    • PartiQL - grammar a negative number with no leading digit matches in WHERE source:84
    • PartiQL - grammar a number with no leading digit in an INSERT stores the number it denotes source:129
    • PartiQL - grammar a line comment after the statement is ignored source:84
    • PartiQL - grammar a line comment between FROM and WHERE leaves the WHERE clause in force source:84
    • PartiQL - grammar a line comment before the statement is ignored source:84
    • PartiQL - grammar a block comment between clauses is ignored source:84
    • PartiQL - grammar a block comment after the statement is ignored source:84
    • ExecuteStatement - index qualifier projection follows the index, not the item SELECT * against a non-ALL index does not reach back source:236
    • ExecuteStatement - index qualifier the reach-back splits by index kind an LSI serves an unprojected attribute from the base table source:251
    • ExecuteStatement - index qualifier the reach-back splits by index kind a GSI rejects an unprojected attribute rather than reaching back source:261
    • ExecuteStatement - index qualifier the reach-back splits by index kind naming only projected attributes on an LSI charges no table arm source:270
    • ExecuteStatement - index qualifier the reach-back splits by index kind a bounded reach-back walks fewer rows and is charged less source:299
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition accepts the same GSI filter unkeyed, matching nothing source:72
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition accepts the same LSI filter unkeyed, matching nothing source:72
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition accepts two unprojected filters with no index key source:72
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition matches every index row when the negated filter names an absent attribute source:72
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition accepts an unprojected filter inside an OR branch source:72
    • ExecuteStatement - index qualifier a set of LSI keys holds the token past a missing key written after the found key source:496
    • ExecuteStatement - index qualifier a set of LSI keys holds the token past a missing key written before the found key source:496
    • ExecuteStatement - index qualifier a set of LSI keys charges a missing key beside a found one under ConsistentRead source:506
    • ExecuteStatement - index qualifier a set of LSI keys charges per key, not per row, for two found keys over three rows source:514
    • ExecuteStatement - index qualifier capacity lands on the index arm a keyed GSI read charges the index and a zero table arm source:603
    • ExecuteStatement - index qualifier capacity lands on the index arm a keyed LSI read charges the index and a zero table arm source:610
    • ExecuteStatement - order of rows tied on an index key returns LSI ties in the order a Query of the index does source:72
    • ExecuteStatement - order of rows tied on an index key returns two rows sharing an LSI key in a fixed order, not sort-key order source:78
    • ExecuteStatement - order of rows tied on an index key reverses that order under ORDER BY on the tied key descending source:24
    • PartiQL - GSI with a multi-attribute key a SELECT on a GSI with two HASH and two RANGE attributes is refused source:130
    • PartiQL - GSI with a multi-attribute key a SELECT on a GSI with two HASH attributes and one RANGE is refused source:144
    • PartiQL - GSI with a multi-attribute key base table SELECT, INSERT, UPDATE and DELETE run on a table whose GSI is multi-attribute source:170
    • PartiQL - OR reads in one partition: paging a set of sort keys ends on its last key two keys under Limit 1 take two pages, the second with no token, written as one OR of sort-key equalities source:140
    • PartiQL - OR reads in one partition: paging a set of sort keys ends on its last key two keys under Limit 1 take two pages, the second with no token, written as two branches that each name the partition key source:140
    • PartiQL - OR reads in one partition: paging a set of sort keys ends on its last key two keys under Limit 1 take two pages, the second with no token, written as parameters source:140
    • PartiQL - OR reads in one partition: paging a set of sort keys ends on its last key two keys under Limit 2 come back on one page with no token source:148
    • PartiQL - OR reads in one partition: paging a set of sort keys ends on its last key two keys under Limit 3 come back on one page with no token source:148
    • PartiQL - OR reads in one partition: paging a set of sort keys ends on its last key three keys under Limit 2 take two pages, the second with no token source:157
    • PartiQL - OR reads in one partition: paging a set of sort keys ends on its last key two keys read descending return the higher key first and end on the lower source:167
    • PartiQL - OR reads in one partition: paging a set of sort keys ends on its last key two keys with a row between them read descending skip that row source:177
    • PartiQL - OR reads in one partition: paging number sort keys keys 1.5 and 10 under Limit 1 take two pages, the second with no token source:189
    • PartiQL - OR reads in one partition: paging number sort keys keys -1 and 1.5 under Limit 1 take two pages, the second with no token source:189
    • PartiQL - OR reads in one partition: paging a missing key a missing last key keeps the token for an empty half-unit page, ascending source:205
    • PartiQL - OR reads in one partition: paging a missing key a missing last key keeps the token for an empty half-unit page, descending source:205
    • PartiQL - OR reads in one partition: paging a missing key a missing first key gives one page with no token, charged for both keys, ascending source:215
    • PartiQL - OR reads in one partition: paging a missing key a missing first key gives one page with no token, charged for both keys, descending source:215
    • PartiQL - OR reads in one partition: paging a missing key a missing key between two found ones is charged on the second page, ascending source:227
    • PartiQL - OR reads in one partition: paging a missing key a missing key between two found ones is charged on the second page, descending source:227
    • PartiQL - OR reads in one partition: paging a single key a full key under Limit 1 gives one page with no token source:243
    • PartiQL - OR reads in one partition: paging a single key a full key with a filter under Limit 1 gives one page with no token source:243
    • PartiQL - OR reads in one partition: paging a single key a single key read descending under Limit 1 gives one page with no token source:243
    • PartiQL - OR reads in one partition: paging a sort-key IN two found keys under Limit 1 take two pages, the second with no token source:254
    • PartiQL - OR reads in one partition: paging a sort-key IN a missing last key keeps the token for an empty half-unit page source:261
    • PartiQL - OR reads in one partition: paging a sort-key IN read descending returns the higher key first source:271
    • PartiQL - OR reads in one partition: paging ranges with closed bounds BETWEEN under Limit 1 ends on the bound with no trailing empty page source:295
    • PartiQL - OR reads in one partition: paging ranges with closed bounds <= under Limit 2 ends on the bound with no trailing empty page source:295
    • PartiQL - OR reads in one partition: paging ranges with closed bounds BETWEEN over three rows under Limit 3 ends on the bound with no trailing empty page source:295
    • PartiQL - OR reads in one partition: paging ranges with closed bounds >= read descending under Limit 1 ends on the bound with no trailing empty page source:295
    • PartiQL - OR reads in one partition: paging ranges with closed bounds a union of two closed ranges under Limit 1 ends on the bound with no trailing empty page source:295
    • PartiQL - OR reads in one partition: paging ranges with closed bounds an empty branch the read has not reached keeps the token for an empty page source:302
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead two found keys cost 2 source:87
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead three found keys cost 3 source:96
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead a missing key beside a found one costs 2 source:108
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead a missing key repeated within one branch beside a found one costs 2 source:117
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead a union of two ranges, one of them empty, costs 2 source:124
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead a union of two ranges that each find a row costs 2 source:130
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead a key beside a range costs 2 source:136
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead an empty begins_with branch beside a found one costs 2 source:145
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead an empty BETWEEN branch beside a found one costs 2 source:154
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead an empty range branch read descending costs 2 source:163
    • PartiQL - read capacity of OR and IN on the sort key eventually consistent two found keys cost 1 source:173
    • PartiQL - read capacity of OR and IN on the sort key eventually consistent two missing keys cost 1 source:179
    • PartiQL - read capacity of OR and IN on the sort key eventually consistent three missing keys and one found cost 2 source:186
    • PartiQL - read capacity of OR and IN on the sort key IN costs what its OR costs two keys cost 2 under ConsistentRead source:196
    • PartiQL - read capacity of OR and IN on the sort key IN costs what its OR costs two keys cost 1 eventually consistent source:204
    • PartiQL - read capacity of OR and IN on the sort key IN costs what its OR costs three keys cost 3 under ConsistentRead source:213
    • PartiQL - read capacity of OR and IN on the sort key IN costs what its OR costs a missing key and a found one cost 2 under ConsistentRead source:222
    • PartiQL - read capacity of OR and IN on the sort key two sort keys beside a wide filter nine non-key OR pairs that no row passes cost 1 eventually consistent source:235
    • PartiQL - read capacity of OR and IN on the sort key two sort keys beside a wide filter eight IS MISSING OR pairs that every row passes cost 2 under ConsistentRead source:242
    • PartiQL - read capacity of a partition key that cannot be a key pk = true beside one closed range finds nothing for 2, or 4 consistently source:30
    • PartiQL - read capacity of a partition key that cannot be a key pk = true beside two closed ranges finds nothing for 2, or 4 consistently source:30
    • PartiQL - read capacity of a partition key that cannot be a key pk = true beside three closed ranges finds nothing for 2, or 4 consistently source:30
    • PartiQL - read capacity of a partition key that cannot be a key pk = 1 on a string key beside one closed range finds nothing for 2, or 4 consistently source:30
    • PartiQL - read capacity of a partition key that cannot be a key pk = 1 on a string key beside two closed ranges finds nothing for 2, or 4 consistently source:30
    • PartiQL - read capacity of a partition key that cannot be a key pk = 1 on a string key beside three closed ranges finds nothing for 2, or 4 consistently source:30
    • PartiQL - functions and IS in a WHERE clause can be compared with true source:83
    • PartiQL - functions and IS in a WHERE clause IS with a type name runs as a filter source:83
    • PartiQL - responses to writes a DELETE that finds no item returns an empty Items list source:70
  • validation-ordering Tier 3 101 diverging
    View these tests in the suite →
    • Batch operations - enum and ordering checks BatchGetItem reports a malformed table name and an unknown ReturnConsumedCapacity together source:256
    • CreateTable - validation ordering invalid table name pattern reports only tableName source:41
    • CreateTable - validation ordering rejects more than two KeySchema elements source:134
    • CreateTable - index name errors across index kinds lists the GSI error before the LSI error when the request lists the LSI first source:207
    • CreateTable - index name errors across index kinds lists the GSI error first even when the LSI name sorts first source:214
    • Deep requests - legacy conditions PutItem reports XOR in the older enum wording ahead of an Expected value nested 100 levels source:98
    • Deep requests - legacy conditions UpdateItem reports XOR in the older enum wording ahead of an Expected value nested 100 levels source:113
    • Deep requests - TransactWriteItems action order reports a Put item nested 40 levels before an empty attribute name in a later Put source:153
    • Deep requests - TransactWriteItems action order reports an empty attribute name before a Put item nested 100 levels in a later Put source:163
    • Deep requests - TransactWriteItems action order reports a top-level empty attribute name before a value nested 100 levels in the same item, in either order source:169
    • Deep requests - TransactWriteItems action order refuses a value nested 40 levels beside an empty map key inside the same item source:179
    • Deep requests - TransactWriteItems action order reports an empty attribute name before a later ConditionCheck value nested 100 levels source:196
    • Deep requests - TransactWriteItems action order reports an earlier ConditionCheck value nested 40 levels before a later empty attribute name source:215
    • Deep requests - TransactWriteItems action order reports an earlier Update value nested 40 levels before a later empty attribute name source:233
    • Deep requests - TransactWriteItems action order reports a Put condition syntax error before a later Delete key nested 100 levels source:270
    • Deep requests - TransactWriteItems action order reports a condition syntax error before the same Delete key nested 100 levels source:277
    • Deep requests - TransactWriteItems action order reports an oversized condition before the same Delete key nested 100 levels source:295
    • Deep requests - TransactWriteItems action order reports an oversized UpdateExpression before a later ConditionCheck key nested 100 levels source:312
    • Deep requests - TransactWriteItems action order reports an unused value before a later ConditionCheck key nested 100 levels source:329
    • Deep requests - DeleteItem ReturnValues refuses an unknown ReturnValues in the older wording when the condition value is nested 63 levels source:348
    • Deep requests - DeleteItem ReturnValues refuses an unknown ReturnValues in the older wording when an Expected value is nested 63 levels source:357
    • Deep requests - DeleteItem ReturnValues refuses an unknown ReturnValues in the older wording when the key is nested 100 levels source:364
    • Deep requests - DeleteItem ReturnValues refuses UPDATED_NEW with the bare ReturnValues message ahead of a condition value nested 100 levels source:371
    • Deep writes list every bad member in order PutItem joins a bad ReturnValues and XOR source:404
    • Deep writes list every bad member in order PutItem lists ReturnValues, XOR, then a bad ReturnConsumedCapacity source:409
    • Deep writes list every bad member in order PutItem lists ReturnValues, XOR, then a bad ReturnItemCollectionMetrics source:414
    • Deep writes list every bad member in order PutItem lists ReturnValues then ReturnConsumedCapacity without XOR source:419
    • Deep writes list every bad member in order PutItem leaves a valid ReturnValues out of the list source:424
    • Deep writes list every bad member in order PutItem lists all five bad members in order source:428
    • Deep writes list every bad member in order PutItem lists a missing Item third among all five bad members source:435
    • Deep writes list every bad member in order PutItem reads a null Item as missing source:441
    • Deep writes list every bad member in order UpdateItem joins a bad ReturnValues and XOR source:447
    • Deep writes list every bad member in order UpdateItem lists a bad ReturnConsumedCapacity ahead of ReturnValues and XOR source:452
    • Deep writes list every bad member in order UpdateItem lists ReturnValues, XOR, then a bad ReturnItemCollectionMetrics source:457
    • Deep writes list every bad member in order UpdateItem lists ReturnConsumedCapacity, ReturnValues, XOR, then ReturnItemCollectionMetrics source:464
    • Deep writes list every bad member in order UpdateItem lists all five bad members in order source:468
    • Deep writes list every bad member in order UpdateItem lists a missing Key last among all five bad members source:475
    • Deep writes list every bad member in order UpdateItem lists a missing Key after ReturnValues and XOR source:482
    • Deep writes list every bad member in order UpdateItem reads a null Key as missing source:488
    • Deep writes list every bad member in order UpdateItem keeps the envelope for a bad ReturnConsumedCapacity alone source:492
    • Deep writes list every bad member in order UpdateItem keeps the envelope for a bad ReturnValuesOnConditionCheckFailure alone source:496
    • Deep writes list every bad member in order UpdateItem treats a value that reads like an error header as a plain value source:501
    • Deep writes list every bad member in order DeleteItem joins a bad ReturnValues and XOR source:507
    • Deep writes list every bad member in order DeleteItem lists ReturnValues, XOR, then a bad ReturnConsumedCapacity source:512
    • Deep writes list every bad member in order DeleteItem lists ReturnValues, XOR, then a bad ReturnItemCollectionMetrics source:517
    • Deep writes list every bad member in order DeleteItem lists ReturnValues, XOR, ReturnConsumedCapacity, then ReturnItemCollectionMetrics source:524
    • Deep writes list every bad member in order DeleteItem lists ReturnValues, XOR, then a bad ReturnValuesOnConditionCheckFailure source:531
    • Deep writes list every bad member in order DeleteItem lists all five bad members in order source:535
    • Deep writes list every bad member in order DeleteItem lists a missing Key last among all five bad members source:542
    • Deep writes list every bad member in order DeleteItem reads a null Key as missing source:548
    • Deep writes list every bad member in order DeleteItem reports XOR alone ahead of the nesting error source:552
    • Deep writes list every bad member in order DeleteItem reports only XOR beside a ReturnValues of ALL_NEW source:556
    • Deep writes list every bad member in order DeleteItem drops a ReturnValues of ALL_NEW beside a bad ReturnConsumedCapacity source:560
    • Deep writes list every bad member in order DeleteItem keeps a value holding "; " as one error source:565
    • Deep writes check the table name in two stages PutItem lists a missing name after a bad ReturnValues source:594
    • Deep writes check the table name in two stages PutItem reports a missing name alone in the envelope source:598
    • Deep writes check the table name in two stages PutItem lists a missing name last, after every bad member and the missing Item source:602
    • Deep writes check the table name in two stages PutItem lists an empty name as a member error after a bad ReturnValues source:608
    • Deep writes check the table name in two stages PutItem lists an empty name after a missing Item source:612
    • Deep writes check the table name in two stages PutItem drops a short name beside a bad ReturnValues source:616
    • Deep writes check the table name in two stages PutItem drops a name with bad characters beside a bad ReturnValues source:620
    • Deep writes check the table name in two stages PutItem drops a short name beside a missing Item source:624
    • Deep writes check the table name in two stages PutItem drops a 300-character name beside XOR and a bad ReturnValues source:629
    • Deep writes check the table name in two stages PutItem reports a short name once every member passes source:633
    • Deep writes check the table name in two stages PutItem lists the length then the pattern for a short name with bad characters source:637
    • Deep writes check the table name in two stages PutItem lists the length then the pattern for a long name with bad characters source:644
    • Deep writes check the table name in two stages PutItem reports only the length for a long name with a valid pattern source:649
    • Deep writes check the table name in two stages UpdateItem lists a missing name second, after a bad ReturnConsumedCapacity source:655
    • Deep writes check the table name in two stages UpdateItem lists an empty name as a member error after a bad ReturnConsumedCapacity source:662
    • Deep writes check the table name in two stages UpdateItem drops a short name beside a bad ReturnConsumedCapacity source:666
    • Deep writes check the table name in two stages UpdateItem drops a short name with bad characters beside a bad ReturnConsumedCapacity source:670
    • Deep writes check the table name in two stages UpdateItem drops a 300-character name beside a missing Key source:674
    • Deep writes check the table name in two stages UpdateItem lists the length then the pattern for a short name with bad characters source:678
    • Deep writes check the table name in two stages UpdateItem lists the length then the pattern for a long name with bad characters source:685
    • Deep writes check the table name in two stages DeleteItem lists a missing name after XOR source:691
    • Deep writes check the table name in two stages DeleteItem lists a missing name last, after every bad member and the missing Key source:695
    • Deep writes check the table name in two stages DeleteItem reads a null name as missing and drops a ReturnValues of ALL_NEW beside XOR source:703
    • Deep writes check the table name in two stages DeleteItem reports an empty name alone in the envelope source:707
    • Deep writes check the table name in two stages DeleteItem drops a name with bad characters beside XOR source:711
    • Deep writes check the table name in two stages DeleteItem lists the length then the pattern for a short name with bad characters source:715
    • Deep writes check the table name in two stages DeleteItem reports only the pattern for a long enough name with bad characters source:721
    • Deep writes check the table name in two stages DeleteItem reports the name errors ahead of a ReturnValues of ALL_NEW source:726
    • Deep writes check the table name in two stages DeleteItem keeps the bare ReturnValues sentence for ALL_NEW alone source:730
    • Deep writes count a table name in UTF-16 units PutItem finds two accented letters too short source:748
    • Deep writes count a table name in UTF-16 units PutItem does not find 200 accented letters too long source:753
    • Deep writes count a table name in UTF-16 units PutItem does not find two emoji too short source:757
    • Deep writes count a table name in UTF-16 units UpdateItem finds two accented letters too short source:761
    • Deep writes count a table name in UTF-16 units UpdateItem does not find two emoji too short source:765
    • Deep writes count a table name in UTF-16 units UpdateItem finds 128 emoji too long source:769
    • Deep writes count a table name in UTF-16 units DeleteItem finds two accented letters too short source:773
    • Deep writes count a table name in UTF-16 units DeleteItem does not find two emoji too short source:777
    • Deep writes count a table name in UTF-16 units DeleteItem finds 128 emoji too long source:781
    • PartiQL - validation ordering a Limit sent as a string fails deserialisation ahead of table resolution source:143
    • Query - ConditionalOperator beside Select reports XOR with two QueryFilter conditions before an unknown Select source:96
    • TransactWriteItems - validation ordering reports a malformed condition on a later action ahead of a missing table on an earlier one source:51
    • TransactWriteItems - validation ordering reports a malformed condition on the first action ahead of a too deep item on the second source:215
    • TransactWriteItems - validation ordering reports a too deep item on the first action ahead of a malformed condition on the second source:235
    • UpdateItem - validation ordering rejects invalid ReturnValues (UpdateItem reports the first enum error) source:54
    • UpdateItem - member errors beside a missing Key joins an empty table name with the missing key source:101
    • UpdateItem - member errors beside a missing Key joins the enums, an empty table name and the missing key in member order source:105
    • UpdateItem - member errors beside a missing Key joins XOR with two Expected conditions to the missing key source:121
  • limits Tier 3 67 diverging
    View these tests in the suite →
    • Item size limit by surface - PartiQL INSERT accepts an item of exactly 409,600 bytes source:143
    • Item size limit by surface - PartiQL UPDATE refuses it one byte over, with the update wording source:183
    • Item size limit by surface - TransactWriteItems an Update one byte over surfaces as a cancellation, with the update wording source:221
    • Item size limit by surface - TransactWriteItems answers the same way for a fresh key and for an existing row source:221
    • Item size limit by surface - UpdateItem does not charge for the key sits below 409,600 at a one-byte key, so the exclusion binds source:453
    • Item size limit by surface - UpdateItem does not charge for the key caps at exactly 409,600 with a 100-byte key value source:453
    • Item size limit by surface - UpdateItem does not charge for the key caps at exactly 409,600 with a 1024-byte key value source:453
    • Item size limit by surface - UpdateItem does not charge for the key buys back the same headroom from the key name as from the key value source:453
    • Item size limit by surface - UpdateItem does not charge for the key buys back a sort key’s own bytes as well source:453
    • Item size limit by surface - UpdateItem charges per action charges a second SET clause exactly 19 bytes source:453
    • Item size limit by surface - UpdateItem charges per action charges a REMOVE alongside a SET exactly 2 bytes source:453
    • Item size limit by surface - UpdateItem charges per action charges the clause, not the value it writes source:453
    • Item size limit by surface - UpdateItem charges per action does not charge for an attribute the statement leaves alone source:453
    • Item size limit by surface - UpdateItem charges per action charges the clause, not the attribute name or its alias source:453
    • Item size limit by surface - UpdateItem through a document path charges a SET through a list index exactly one byte more source:727
    • Item size limit by surface - a PartiQL UPDATE does not inherit the exclusion writes what UpdateItem refuses at the same key source:746
    • Item size limit by surface - a transacted Update does not inherit the exclusion writes what UpdateItem refuses at the same key source:746
    • Item size limit by surface - UpdateItem charges each kind of clause charges a path operand 15 bytes plus its name, not the value it copies source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges a nested path operand 14 bytes plus the element for each element source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges list_append 37 bytes plus its operands source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges a document value operand at its size, at every use source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges an addition 34 bytes plus its operands, whatever the result source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges a subtraction 37 bytes plus its operands source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges if_not_exists 39 bytes plus its operands, whether or not the path exists source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges an ADD 19 bytes plus its path and the value added source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges an ADD to a set only for the members it adds source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges a REMOVE one byte plus its path source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges a REMOVE through a list index 4 bytes plus its digits source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges a DELETE one byte plus its path, not the members it removes source:872
    • Item size limit by surface - AttributeUpdates sizes the finished item caps the finished item at exactly 409,600 alone source:1093
    • Item size limit by surface - AttributeUpdates sizes the finished item caps the finished item at exactly 409,600 beside an untouched attribute source:1093
    • Item size limit by surface - UpdateItem checks the charge before the condition refuses an over-limit charge even when the condition would fail source:1124
    • Item size limit by surface - UpdateItem checks the charge before the condition refuses an over-limit charge when the condition passes, and with no condition source:1129
    • Leading underscore in expressions rejects one in a FilterExpression on Query and Scan source:51
    • Leading underscore in expressions rejects one in a ProjectionExpression source:62
    • Leading underscore in expressions rejects one in a KeyConditionExpression, on a table and on an index source:88
    • Leading underscore in expressions rejects one in a ConditionExpression source:103
    • Leading underscore in expressions rejects one in an UpdateExpression source:117
    • Nesting depth - 32-level document limit accepts a 32-level ExpressionAttributeValue (condition is evaluated) source:158
    • Nesting depth - 32-level document limit rejects a stored attribute nested 63 levels without the envelope source:193
    • Nesting depth - 32-level document limit rejects a 63-level ExpressionAttributeValue naming its key source:204
    • Nesting depth - BatchWriteItem rejects a Put item nested 32 levels (leaf at level 33) source:258
    • Nesting depth - TransactWriteItems rejects a Put item nested 32 levels with a top-level ValidationException source:309
    • Nesting depth - TransactWriteItems cancels an Update that writes a 32-level value into the item with a ValidationError reason source:361
    • Nesting depth - TransactWriteItems does not check the depth of an Update ExpressionAttributeValue (the condition is evaluated) source:400
    • Nesting depth - TransactWriteItems does not check the depth of a ConditionCheck ExpressionAttributeValue (the condition is evaluated) source:436
    • Nesting depth - TransactWriteItems refuses a ConditionCheck value nested 33 levels before the transaction runs source:470
    • Nesting depth - TransactWriteItems refuses a Put whose condition compares a value nested 33 levels, and writes nothing source:494
    • Nesting depth - TransactWriteItems refuses an Update writing a value nested 33 levels before the transaction runs source:521
    • Nesting depth - TransactWriteItems refuses a ConditionCheck map value nested 61 levels, naming the key source:549
    • Nesting depth - TransactWriteItems refuses a ConditionCheck list value nested 61 levels, naming the key source:549
    • A number's byte cost sizes '1' at '2 bytes' source:104
    • A number's byte cost sizes '123' at '3 bytes' source:104
    • A number's byte cost sizes '100' at '2 bytes' source:104
    • A number's byte cost sizes '1010' at '3 bytes' source:104
    • A number's byte cost sizes '0.0000001' at '2 bytes' source:104
    • A number's byte cost sizes '1E125' at '2 bytes' source:104
    • A number's byte cost sizes '1E-100' at '2 bytes' source:104
    • A number's byte cost sizes '1.5' at '3 bytes' source:104
    • A number's byte cost sizes '1.2' at '3 bytes' source:104
    • A number's byte cost sizes '1.200' at '3 bytes' source:104
    • A number's byte cost sizes '1.234' at '4 bytes' source:104
    • A number's byte cost sizes '3.14159' at '5 bytes' source:104
    • A number's byte cost sizes '100.5' at '4 bytes' source:104
    • A number's byte cost sizes '-42' at '3 bytes' source:104
    • A number is stored expanded and sized by its significant digits costs the same either way: the expanded form is not what is measured source:145
    • TransactWriteItems limits TransactWriteItems total item size over 4MB fails with ValidationException source:98
  • vectorSearch Tier 2 15 diverging
    View these tests in the suite →
    • PutItem - vector write capacity shape TOTAL folds nothing in: no vector fields at all source:204
    • PutItem - vector write capacity shape an identical overwrite reports no vector write: replication is delta-based source:243
    • PutItem - a vector index is charged on the change to its stored view charges the index that projects the changed attribute, and not the one that does not source:280
    • PutItem - a vector index is charged on the change to its stored view charges neither when the write changes nothing either index holds source:288
    • PutItem - VectorWriteRequestBytes applies the floor per index, not per write source:329
    • PutItem - VectorWriteRequestBytes charges four bytes per dimension source:339
    • PutItem - VectorWriteRequestBytes charges the vector attribute’s name by its own length source:345
    • PutItem - VectorWriteRequestBytes charges a projected non-vector attribute its own item size source:352
    • GetItem and the 400KB gate - how a vector is sized charges a read for the vector’s billed size, not the numbers it holds source:445
    • PartiQL - vector indexes are out of reach rejects a PartiQL read of a vector index source:56
    • SearchVectors - deterministic search behaviour omits the vector attribute by default and returns it when projected source:163
    • SearchVectors - deterministic search behaviour stores full precision on the base table and f32 in the index source:215
    • UpdateTable - vector index lifecycle adds an index that backfills like a GSI, enforces one online action, then deletes it source:158
    • UpdateTable - vector index lifecycle refuses to delete the table while a vector index is still being created source:318
    • UpdateTable - vector index lifecycle reports UPDATING with Backfilling false while allocating, and takes a cancel only once backfilling starts source:460
  • query Tier 1 7 diverging
    View these tests in the suite →
    • Query - size() string encoding counts UTF-16 code units (3), not UTF-8 bytes (6) source:486
    • Query - order of rows tied on an index key returns LSI ties in a fixed order ascending source:80
    • Query - order of rows tied on an index key returns LSI ties in the exact reverse descending source:84
    • Query - order of rows tied on an index key returns GSI ties in a fixed order ascending, different from the LSI source:88
    • Query - order of rows tied on an index key returns GSI ties in the exact reverse descending source:92
    • Query - KeyConditionExpression with parentheses rejects redundant parentheses in KeyConditionExpression source:98
    • Query - KeyConditionExpression semantics rejects a nested path on a key attribute source:54
  • getItem Tier 1 5 diverging
    View these tests in the suite →
    • ConsumedCapacity - single-item ops report only the aggregate, no read/write split a strongly-consistent GetItem reports 1 CapacityUnit and no read/write split source:188
    • ConsumedCapacity - single-item ops report only the aggregate, no read/write split an eventually-consistent GetItem reports 0.5 CapacityUnits and no read/write split source:200
    • ConsumedCapacity - single-item ops report only the aggregate, no read/write split a Query under INDEXES omits the split at the top level and on Table source:217
    • ConsumedCapacity - single-item ops report only the aggregate, no read/write split an UpdateItem reports 1 CapacityUnit and no read/write split source:232
    • ConsumedCapacity - single-item ops report only the aggregate, no read/write split a DeleteItem reports 1 CapacityUnit and no read/write split source:243
  • putItem Tier 1 5 diverging
    View these tests in the suite →
    • PutItem - ConditionExpression parens rejects contains() with a duplicate path and operand source:139
    • PutItem - ConditionExpression rejects a BETWEEN with reversed bounds at parse time source:251
    • ReturnConsumedCapacity - PutItem reports only the aggregate, no write-capacity split PutItem with TOTAL reports 1 CapacityUnit and no read/write split source:142
    • ReturnConsumedCapacity - PutItem reports only the aggregate, no write-capacity split PutItem with INDEXES omits the split at the top level and on Table source:153
    • PutItem - index write capacity reports the GSI write beside the table write and sums them source:110
  • updateItem Tier 1 2 diverging
    View these tests in the suite →
    • UpdateItem - ADD ADD of an empty string member onto an existing set adds it source:480
    • UpdateItem - SET evaluation semantics applies parenthesised arithmetic (SET c = (c - :v)) source:830
  • transactions Tier 2 2 diverging
    View these tests in the suite →
    • TransactGetItems - projection matching nothing omits Item when the projection matches no attribute on a present item source:342
    • TransactWriteItems - ConsumedCapacity: conditional, check, replay, cancel reports write capacity on the first call and read capacity on a same-token replay source:1421
  • createTable Tier 1 1 diverging
    View these tests in the suite →
    • CreateTable - LSI rejects LSI on a hash-only table source:58
  • kinesis Tier 2 1 diverging
    View these tests in the suite →
    • Kinesis streaming destination enables a streaming destination and reports it via Describe source
  • tags Tier 2 1 diverging
    View these tests in the suite →
    • Tags - validation rejects ListTagsOfResource with a non-existent ARN source:211
  • updateTable Tier 2 1 diverging
    View these tests in the suite →
    • UpdateTable - add GSI accepts a conflicting redeclaration of an existing key attribute and keeps the stored type source:487

Run history

Every percentage here is divergence, per tier and over the whole suite, so lower is better in each column. Coverage is the exception it is named as.

Run Gradecurrent criteria Divergence Movement

Suite on

ca-central-1 joins eu-west-2 on the five Scan rows. It gave the new wording on the 2026-11-07 and 2026-11-14 sweeps and on the three runs on 2026-11-13, which leaves me-central-1 the only region recorded on the old wording. On the 2026-11-14 sweep eu-north-1 stored UpdateItem writes that the statement-sized rule refuses, which it had not done before. Three runs later that day had it answering both ways, so the item-size rows stay as they are.

Ten regions join eu-west-2 on the five Scan rows: ap-northeast-1, ap-south-2, ap-southeast-6, ap-southeast-7, eu-central-2, eu-south-1, eu-south-2, eu-west-1, us-east-2 and us-west-2. Each gave the new wording on the 2026-11-07 sweep and at least one sweep before it, and on three runs against every region on 2026-11-13, which leaves ca-central-1 and me-central-1 on the old wording. ca-central-1 gave the new wording on the 2026-11-07 sweep and on all three runs, but the old wording on the two sweeps before, so it keeps its recorded answer until a second sweep agrees. eu-north-1 gave the old wording on one of the three runs, so it answers Scan both ways for now and keeps its recorded answer, the new wording. The BatchGetItem row doesn't change: me-central-1 gave both answers to an empty RequestItems across the same runs.

eu-west-2 now accepts a 32-level ExpressionAttributeValue in an UpdateItem condition, so the test that pinned its refusal now pins acceptance, and is renamed to say so. It asserts the ConditionalCheckFailedException a false condition gives, the same proof the 31-level test uses. The 2026-11-14 sweep found 19 regions accepting a value they had refused the week before, and by the last of three runs that day 23 did. ap-east-1, ap-southeast-2, ca-west-1, eu-south-2, eu-west-3, mx-central-1, us-east-1, us-west-1 and us-west-2 still refuse it, and me-central-1, which had accepted it until then, now refuses it too. The registry records those ten on that side. The same regions moved together on UpdateItem's ReturnValues error, which now lists UPDATED_NEW where it listed UPDATE_NEW. That test accepts both, and its row now pins the new wording. A stored item is still capped at 32 levels everywhere, and a 63-level value is still refused.

The wait for an index added by UpdateTable to become ACTIVE is now 2 minutes on any emulator, down from 40. Real DynamoDB keeps 40 minutes. The slowest passing index test on any emulator in the published results takes about 31 seconds, against about 25 minutes on real DynamoDB, so the shorter wait only shortens runs where an index never completes. An expired wait is recorded as no answer either way, never as a failure, so no score can change.

PartiQL reads whose OR branches stay in one partition now have paging and capacity tests. Under Limit, a set of sort keys ends on its last key, a missing last key keeps the token for one empty half-unit page, and a branch the read hasn't reached holds the token. Each shape pinned page by page gave the same pages on every walk in eu-west-2 and us-east-1 between 2026-11-03 and 2026-11-05. Page endings that DynamoDB answers at random, such as a page ending inside an open range, are checked only for the keys they return. Each branch costs a unit under ConsistentRead even when it finds nothing, a sort-key IN costs and pages exactly as the equivalent OR does, and a partition key that can't be a key reads the whole table, so beside sort-key ranges it costs what that read does: 2.0, or 4.0 consistent, on the small on-demand table the test uses.

Items tied on an index key come back in a fixed order that isn't the table's sort-key order, and descending is its exact reverse. The order was the same in nine fresh tables across two regions and two AWS accounts, whatever order the items were written in, so Query on an LSI and a GSI, and PartiQL on an LSI, now pin it.

The PartiQL refusals these reads run into are pinned word for word: a negated sort key inside an OR filter, a partition key given the wrong type or a boolean, ORDER BY over branches that each name the partition key, a KEYS_ONLY index asked to filter on an attribute it doesn't project, and ExecuteStatement Limit values of 0, -1 and a string. What DynamoDB accepts is pinned beside them: ORDER BY on an OR in one partition, the same key written twice, and Limit values past 2^31, past 2^64 and written with an exponent or a fraction.

An attribute name starting with an underscore is a syntax error in every expression type unless it goes through ExpressionAttributeNames, including key conditions. An UpdateItem that creates its item returns no Attributes under ALL_OLD or UPDATED_OLD.

Deep PutItem, UpdateItem and DeleteItem requests, read by the older validation layer, now have their joined errors pinned: every bad member, in each operation's own order, under the N validation errors detected envelope even when only one member is wrong.

A table name's length is counted in UTF-16 units on deep writes and on CreateTable, DescribeTable, DeleteTable and UpdateTable, and in characters on shallow item operations, ListTables' start name and index names. So two emoji are long enough for CreateTable and too short for PutItem. Deep writes also check the name in two stages: a missing or empty name is listed among the member errors, while length and pattern errors only show when nothing else is wrong.

Fourteen new rows in registry/splits.json record where me-central-1, and eu-north-1 on Scan, gave the older validation layer's answer to the shallow table-name and leading-underscore cases on 2026-11-05. The other regions agree with eu-west-2. The answers from all 33 regions on 2026-11-05 are in captures/2026-11-05-shallow-validation-rollout.json. On three later runs on 2026-11-13, me-central-1 gave eu-west-2's answer to the twelve cases that aren't Scan (once cut short, on UpdateItem) and eu-north-1 gave it on Scan, so the rows keep the 2026-11-05 answers until a sweep has run the tests. Those runs are in captures/2026-11-13-shallow-validation-follow-up.json.

Four more PartiQL index-qualifier answers are pinned. An unknown index read with ConsistentRead is reported as an unknown index, not as a consistent read on a GSI. Selecting an attribute a GSI doesn't project is refused on an unkeyed scan as well as on a keyed read. With two such attributes the refusal lists them in the same order whichever way round the statement names them, and that order isn't alphabetical, so the test pins the list for one pair. A BatchExecuteStatement SELECT on a composite table that gives the partition key but not the sort key is refused like any other member without the full primary key. All four gave the same answers on three runs each in eu-west-2 and us-east-1 on 2026-11-14.

Renaming or removing a released test, or changing a region's recorded answer, no longer fails the checks on its own pull request. The committed results are now checked against the suite and registry as they stood at the release they were measured at, as the rest of the published board already was, rather than against main. The change reaches the board at the next release, when every target is re-run. A board is now refused if real DynamoDB's own run, in its own region, fails a test or passes one on a split row with an answer recorded for a different region.

A project's own row on the board now names its configuration beside the project, as the README table already did, so ExtendDB's row reads "ExtendDB · PostgreSQL" before its other builds are opened. The ways to run a target gain one more, OS package, for an operating system package: a .deb or .rpm, or an apt or dnf repository.

AWS Emulator joins the board, suggested by @exoego in #304. It is AWS's own multi-service emulator, written in Rust, with DynamoDB and DynamoDB Streams among the services it serves. It installs from a Linux package, or on other systems runs in Docker from an image built with the Dockerfile in its user guide. It serves HTTPS and checks SigV4 signatures by default, with a certificate and key it generates on each start, and it is measured that way.

Alternator joins the board. It is ScyllaDB's DynamoDB-compatible API, built into the database node itself rather than run as a separate emulator, with global secondary indexes on materialised views and Streams on change data capture. It runs from the official ScyllaDB container image, and its version column shows the ScyllaDB release the node reports.

ExtendDB's MongoDB backend joins the run as a third build of the same release, beside PostgreSQL and SQLite. It runs against a single-node MongoDB 7.0 replica set and is held to the same TLS, SigV4 and IAM posture as the other two, so the storage engine is again the only thing that differs between them. ExtendDB's PostgreSQL row now lists its official Docker image beside the source.

A target whose run is not scored now publishes as one everywhere. Its badge reads not scored in grey rather than going missing, and its row in the results table reads not scored where the letter would be. Neither the table nor the board gives it a region count, because a cohort is only ever read off a scored headline, and its page says no region has a figure rather than naming a headline region. It still sits below every lettered row. The rule itself doesn't change: a run that gets no answer to any one test is not scored.

Phoenix-Adapters joins the board. It is an Apache project serving the DynamoDB API as a REST layer over Apache Phoenix on HBase, so the row measures an adapter over an external store rather than a self-contained emulator. There is no release yet, so it is built from main with the project's own Docker setup and the row records the commit it ran.

npm run suite:manifest no longer writes into results/. It lists the suite by running it against an endpoint nothing answers, and that run wrote its own "provisioning never completed" file beside the results of whichever target the shell named. With CONFORMANCE_TARGET exported, that target then showed as not scored until the file was deleted, and with nothing set it replaced the one a real local run had left. The listing run now keeps everything in a temporary directory and ignores the caller's target, results directory, endpoint and AWS settings (#342).

Five index tests now have a timeout longer than the waits inside them, which corrects an earlier note in this section: in these five an expired wait could still end as a failure. Two vector index tests could wait up to 20 seconds longer than their timeouts allowed, and three GSI validation tests waited up to 2 minutes for a new table inside the 30-second default. The test runner ended them first, so a slow target got a failure where it should have got no answer. No published result came near the old limits, so no verdict changes.

Floci's row no longer lists Scoop. Its link pointed at a repository that doesn't exist, and Floci's own install instructions don't mention Scoop.

Every target now names its licence. Each target's page shows it in How to run it, next to what the target needs, and each project's entry in the emulator directory shows it under What you need. In both places it is the licence's name, linked to its text or to the vendor's terms. Where a licence has an SPDX identifier, that identifier is the name shown. Builds of one project show the project's licence. Where the thing the suite runs is licensed differently from its source repository, the licence shown is the one for what is run. Each target in /data/latest.json carries the same fact as licence, with name, url and, where one exists, spdx. The one licence remark that sat in a target's run note has moved into the field, so no target carries a line about its licence that the others do not.

LocalStack's name in the results table, and the project links on its pages, now point at localstack.cloud rather than its GitHub repository, which is archived.

A test expecting an error now says so plainly when the request was accepted: expected ValidationException, but the request was accepted, where it used to read expected AssertionError: expected "should have thrown" ... to be an instance of DynamoDBServiceException. The verdict is the same, a failure. What does change is a request that got no answer while a test was waiting for an error. A throttle that outlasted the SDK's retries, a transport fault or a 5xx other than 501 (not implemented, which stays a real failure) used to be judged as the wrong error and recorded as a failure. It is now recorded as no answer, the same as anywhere else in the suite, so a run that meets one is not scored rather than carrying a failure for it. A test that expects one of those errors on purpose still passes when it gets it. This covers tests that use expectDynamoError. Tests that catch the error by hand are unchanged for now.

The sweep's confirmation re-runs now run the test they are meant to repeat (#332). On the 2026-10-31, 2026-11-07 and 2026-11-14 sweeps every confirmation re-run selected no test, so all 16 split candidates were discarded as not reproduced. A candidate that cannot be re-run is now reported on a confirmation-error issue rather than discarded.

The six TransactWriteItems and TransactGetItems tests on malformed numbers and duplicate set members now pin eu-west-2's answer, from the current validation layer, where they accepted either layer's. us-east-1, eu-west-1 and us-west-2, which gave the older layer's answer in October, have moved. On 2026-11-13 every region that answered gave the current layer's answer to all of them except ap-south-1 and me-central-1, and a run of the six tests on 2026-11-14 found ap-south-1 on the current layer as well. Six new rows in registry/splits.json record me-central-1 on the older layer, which reads 1e2147483647 as an underflow and prints set members as sent. An engine that answers these six in the older layer now fails them, and is credited only against me-central-1. me-central-1 has missed the sweeps since 2026-10-17 and is not among the regions the board scores against, so for now such an engine fails them everywhere the board shows. The answers are in captures/2026-11-14-transaction-value-layers.json.

A not-scored row now says why it is not scored, where it used to print its sentences with a dash in place of each figure. Its row on the board and its directory entry say how many of its tests got no answer, or that the whole run did. Its page and the text corpus say the same, and add the reason the suite recorded for each kind (a transport failure or 5xx, a table that never became active, and so on) and what the answered tests did. A row that implements none of the suite says that instead. The page lists the tests that got no answer by operation, each with its reason, and no longer lists them among the failures as divergences they never were. The counts above the lists, and the row's counts in the data endpoints, are read from the same results as the lists, so the failed count is the number of failures listed. The methodology gains a section stating the rule.

The rest of the row reads the same way. A run that got no answer at all lists every operation and feature as not scored, with no pass or fail counts beneath them and no findings, where it used to show figures tallied from tests the run never answered. A feature holding some tests that got no answer reads as not scored too, as an operation holding one already did, rather than wearing a support state read from the rest. The data endpoints add indeterminate to each row's counts, tiers, operation areas and features, so the counts add up to the total on a row that is not scored as on any other; give an area or feature where nothing was observed the state unanswered rather than unsupported; and withhold correctness, and each region's pass rate, wherever the other two figures are withheld. Movement says when a target loses its score or gets one, as not scored and scored, instead of reading unchanged on both runs.

Grade D 26.0% first run