MagnetoDB/QA/Test cases
Contents
KVSaaS Test Cases and Ideas
Notes:
- Test Case status:
- R - ready (test scenario exists and works fine - passes)
- P - in progress (test scenario exists but fails due to not-ready functionality)
- N - not implemented (test scenario is incomplete)
- <empty> - TC has not been analysed yet
DDL and DML statements
BatchGetItem
|
|
|
|
|
|
|
General |
|
|
|
|
|
BatchGetItem contains all the correct mandatory parameters |
|
|
|
|
|
BatchGetItem contains all the correct parameters |
|
|
|
|
|
TableName |
|
|
|
|
|
The only table name (existing) specified |
|
|
|
|
|
Several existing table names specified |
|
|
|
|
|
3 symbols long |
|
|
|
|
|
255 symbols long |
|
|
|
|
|
Less than 3 symbols long |
|
|
|
|
|
More than 255 symbols long |
|
|
|
|
|
Non-existent name |
|
|
|
|
|
Empty (like =) |
|
|
|
|
|
= "" |
|
|
|
|
|
Mixed case letters in the name |
|
|
|
|
|
RequestItems |
|
|
|
|
|
(AttributesToGet) |
|
|
|
|
|
Option not specified (by default) |
All attrs are returned |
|
|
|
|
All existing attrs |
|
|
|
|
|
Some existing attrs |
|
|
|
|
|
Only non-existing attributes |
|
|
|
|
|
No attrs specified (whereas the Option exists) |
|
|
|
|
|
Some existing and some non-existent attrs specified |
|
|
|
|
|
Attrs list looks strange like "" or "//', 123, abc##, etc |
|
|
|
|
|
(Keys) |
|
|
|
|
|
Single "B" key specified |
|
|
|
|
|
"B" and "N" keys specified |
|
|
|
|
|
Single "SS" key specified |
|
|
|
|
|
"SS" and "NS" keys specified |
|
|
|
|
|
"B", "S", "SS" and "NS" keys specified |
|
|
|
|
|
Incorrect key name |
|
|
|
|
|
Incorrect key type |
|
|
|
|
|
Key type omitted |
|
|
|
|
|
Key name omitted |
|
|
|
|
|
Empty key name |
|
|
|
|
|
Empty key type |
|
|
|
|
|
(ConsistentRead) |
|
|
|
|
|
By default (if not specified) |
|
|
|
|
|
= TRUE |
|
|
|
|
|
= FALSE |
|
|
|
|
|
= "" |
|
|
|
|
|
Just = symbol |
|
|
|
|
|
= "Another_value" |
|
|
|
|
|
ReturnConsumedCapasity |
|
|
|
|
|
By default (if not specified) |
|
|
|
|
|
= "INDEXES" |
|
|
|
|
|
= "TOTAL" |
|
|
|
|
|
= "NONE" |
|
|
|
|
|
= "" |
|
|
|
|
|
Just "=" |
|
|
|
|
|
= "Another_value" |
|
|
|
|
|
Exceptions |
|
|
|
|
|
InternalServerError |
|
|
|
|
|
ProvisionedThroughputExceededException |
|
|
|
|
|
ResourceNotFoundException |
|
|
|
|
|
Limitations |
|
|
|
|
|
(Data volume) |
|
|
|
|
|
Specify BatchGet to retrieve less than 1MB of data |
"UnprocessedKeys" contains no items |
|
|
|
|
Specify BatchGet to retrieve exactly 1MB of data |
"UnprocessedKeys" contains no items |
|
|
|
|
Specify BatchGet to retrieve more than 1MB (and < 2MB) of data |
"UnprocessedKeys" contains items exceeding 1MB limit |
|
|
|
|
Specify BatchGet to retrieve more than 2MB of data |
"UnprocessedKeys" contains items exceeding first 1MB limit AND (after the next Request, in the next Response) "UnprocessedKeys" contains items exceeding the 2MB limit |
|
|
|
|
(Items number) |
|
|
|
|
|
Specify less than 100 items in the Request |
|
|
|
|
|
Specify exactly 100 items in the Request |
|
|
|
|
|
Specify more than 100 items in the Request |
error? |
|
|
|
|
Response |
|
|
|
|
|
Contains "GlobalSecondaryIndexes" section if there is (are) such for the table |
|
|
|
|
|
Contains "LocalSecondaryIndexes" section if there is (are) such for the table |
|
|
|
|
|
Contains both GSI and LSI sections if there are such for the table |
|
|
|
|
|
Result contains:
|
|
|
|
|
|
|
|
|
|
|
BatchWriteItem
|
|
|
|
|
|
|
General |
|
|
|
|
|
Complete set of correct mandatory options |
|
|
|
|
|
Complete set of correct all options |
|
|
|
|
|
PutRequest |
|
|
|
|
|
Correct Item string AND "N" : "string" value |
|
|
|
|
|
Non-existent Item string AND "N" : "string" value |
Error + UnprocessedItems contains unprocessed PutRequest Items |
|
|
|
|
EMPTY Item string AND "N" : "string" |
Error + UnprocessedItems contains unprocessed PutRequest Items |
|
|
|
|
Correct Item string and "NS" : ["string"] values |
|
|
|
|
|
Correct Item string and "B" : "string" value |
|
|
|
|
|
Correct Item string and "BS" : ["string"] values |
|
|
|
|
|
Correct Item string and "S" : "string" value |
|
|
|
|
|
Correct Item string and "N" : EMPTY value |
ValidationException + UnprocessedItems contains unprocessed PutRequest Items |
|
|
|
|
Correct Item string and "<SOME_STRANGE_OR_EMPTY_VALUE>" : "string" value |
ValidationException + UnprocessedItems contains unprocessed PutRequest Items |
|
|
|
|
Correct Item string and "NS" : "non-existent_string" value |
ValidationException + UnprocessedItems contains unprocessed PutRequest Items |
|
|
|
|
|
|
|
|
|
|
DeleteRequest |
|
|
|
|
|
Correct Key string and "N" : "string" value |
|
|
|
|
|
Non-existent Key string and "N" : "string" value |
Error + UnprocessedItems contains unprocessed DeleteRequest Items |
|
|
|
|
EMPTY Key string and "N" : "string" value |
Error + UnprocessedItems contains unprocessed DeleteRequest Items |
|
|
|
|
correct Key string and "NS" : ["string"] values |
|
|
|
|
|
correct Key string and "B" : "string" value |
|
|
|
|
|
correct Key string and "BS" : ["string"] values |
|
|
|
|
|
correct Key string and "S" : "string" value |
|
|
|
|
|
Correct Key string and "SS" : ["string"] values |
|
|
|
|
|
CombinedRequest |
|
|
|
|
|
Specify in one statement: correct Key string for DeleteRequest "N" : "string" value AND correct Item string for PutRequest "N" : "string" value |
|
|
|
|
|
Specify in one statement: correct Key string for DeleteRequest "B" : "string" value AND correct Key string for DeleteRequest "SS" : "string" values AND correct Item string for PutRequest "NS" : "string" values AND (!!!) INcorrect Item string for PutRequest "S" : "string" value |
|
|
|
|
|
Specify in one statement: correct Item string for PutRequest "N" : "string_A" value correct Key string for DeleteRequest "N" : "string_A" value |
An error: you can't put and delete the same item in the same BatchWriteItem request |
|
|
|
|
RequestItems (TableName) |
|
|
|
|
|
correct table name and correct PutRequest parameters for the Item |
Line(s) added correctly |
|
|
|
|
Specify 25 correct table names and correct PutRequest parameters for the Items |
Line(s) added correctly into all 25 tables |
|
|
|
|
Specify 26 correct table names and correct PutRequest parameters for the Items |
error/exception (?) |
|
|
|
|
correct table name and correct DeleteRequest parameters for the Key |
Line(s) deleted correctly |
|
|
|
|
INcorrect table name correct PutRequest parameters for an Item Check that UnprocessedItems contains unprocessed PutRequest Items:
|
Exception |
|
|
|
|
Correct table name and correct PutRequest parameters for the Item Make total request size more than 1 MB (how to?) |
error |
|
|
|
|
correct table name and correct PutRequest parameters for the Item Any individual item in a batch exceeds 64 KB (how to?) |
error |
|
|
|
|
ReturnItemCollectionMetrics |
|
|
|
|
|
is NONE (by default) |
no statistics returned |
|
|
|
|
is SIZE |
statistics about item collections, if any, that were modified during the operation are returned in the response |
|
|
|
|
is <Something_else> |
error/exception |
|
|
|
|
ReturnConsumedCapacity |
|
|
|
|
|
is NONE (by default)
|
ConsumedCapacity is not included in the response |
|
|
|
|
is TOTAL |
the response includes ConsumedCapacity data for tables and indexes |
|
|
|
|
is INDEXES |
the response includes ConsumedCapacity for indexes only |
|
|
|
|
is <Something_else> (and empty) |
error/exception |
|
|
|
|
Exceptions |
|
|
|
|
|
Simulate InternalServerError |
|
|
|
|
|
Simulate ItemCollectionSizeLimitExceededException |
|
|
|
|
|
Simulate ProvisionedThroughputExceededException |
|
|
|
|
|
Simulate ResourceNotFoundException |
|
|
|
|
|
|
|
|
|
|
CreateTable
|
|
|
|
|
|
|
General |
|
|
|
|
|
Create table without any optional attributes, only all mandatory |
|
|
|
|
|
Create a table specifying ALL (including mandatory) the correct parameters |
|
|
|
|
|
Try to create two tables with the same name in the same region |
ResourceInUseException expected. |
|
|
|
|
Try to create two tables with the same name in two different regions. |
|
|
|
|
|
Verify first status is CREATING, then ACTIVE |
|
|
|
|
|
What happens if read/write to/from table in CREATING state? Possible to reproduce? |
|
|
|
|
|
Create one table with sec. indexes and then try to create one more table while the first one is in CREATING state. - Possible to reproduce? - How much time the table should be in CREATING state? - Can I manage this time anyhow? |
|
|
|
|
|
Try to create table w/o some mandatory attribute: AttributeDefinitions, KeySchema, ProvisionedThroughput, TableName. |
|
|
|
|
|
AttributeDefinitions |
|
|
|
|
|
Number of attributes |
|
|
|
|
|
create table with 1 attr |
|
|
|
|
|
What is upper limit? Try max and max+1 "Individual items in an DynamoDB table can have any number of attributes, although there is a limit of 64 KB on the item size. An item size is the sum of lengths of its attribute names and values (binary and UTF-8 lengths)." So, number of attr is limited only by item size. Can be tested only via PutItem? |
|
|
|
|
|
Create a table with key and non-key (and non-index also) attributes. It should fail. Non-key attrs are unacceptable. Note: Test for PutItem: PutItem not containing values for non-key/non-indexed attributes of the table to ensure these attrs are not required. |
Error/exception ? |
|
|
|
|
AttrName |
|
|
|
|
|
Try length of 1 symbol, 255 (upper limit) - these limits are applicable only for key attrs and index projections. Other attrs can have longer names, without explicit limits (just size of the whole item). |
|
|
|
|
|
Try lengh 255+1 for key and indexes attr. |
|
|
|
|
|
Check size of non-key / non-index-projected attr names |
|
|
|
|
|
Try to send attr names without attr types. |
|
|
|
|
|
Create table with attrs of each type: S, N, B. Ensure the data types are applied on put/get operations (it could be covered in Put/Get tests). |
|
|
|
|
|
AWS says regarding local indexes creation: “You can project attributes of any data type, including scalar data types and multi-valued sets.” But how to define projection of Set types if they cannot be assigned to the attributes on table creation stage? |
|
|
|
|
|
Try to create a table with attribute of some SET type. It should not be allowed. |
|
|
|
|
|
KeySchema |
|
|
|
|
|
Create table with a key of HASH type. |
|
|
|
|
|
Create table with a key of HASH and RANGE type. |
|
|
|
|
|
Try to enumerate key attrs in wrong order: RANGE and then HASH attrs in the KeySchema list |
|
|
|
|
|
Try to create a table only with RANGE key |
|
|
|
|
|
Try to leave the list empty |
|
|
|
|
|
Try to add more than one HASH and/or RANGE attr. In general, add more than 2 attrs to the list. |
|
|
|
|
|
Try keytype different from HASH and RANGE. |
|
|
|
|
|
Try not to mention key attr in Definitions but only in KeySchema. |
|
|
|
|
|
Try to mention attr names not defined in AttrDefinitions. |
|
|
|
|
|
ProvisionedThroughput (for now, MagnetoDB ignores these values.) |
|
|
|
|
|
Set positive values. |
|
|
|
|
|
Try to mention not all mandatory attrs |
|
|
|
|
|
Try to pass non-number, negative number |
|
|
|
|
|
TableName |
|
|
|
|
|
Name length is 3 |
|
|
|
|
|
Name length is 255 |
|
|
|
|
|
Name length < 3 |
|
|
|
|
|
Name length > 255 |
|
|
|
|
|
What are the limitations regarding lower and upper case, hyphen and other symbols? Do they correspond to DynamoDB rules? AWS says: “For table and secondary index names, allowed characters are a-z, A-Z, 0-9, '_' (underscore), '-' (dash), and '.' (dot). Names can be between 3 and 255 characters long.” |
|
|
|
|
|
Provide an empty table name. |
exception ? |
|
|
|
|
LocalSecondaryIndexes |
|
|
|
|
|
Create index without some of mandatory attributes. |
|
|
|
|
|
Number of indexes |
|
|
|
|
|
Create 1 index for a table |
|
|
|
|
|
Create 5 indexes for the table |
|
|
|
|
|
Create 6 indexes for the table |
|
|
|
|
|
Set LSI attribute as an empty list |
|
|
|
|
|
“There is a 10 GB size limit per hash key” - how to evaluate it? Generate so many items that size of all hash key value is about 10 GB? |
|
|
|
|
|
IndexName |
|
|
|
|
|
Create an index having 3 characters long name |
|
|
|
|
|
Create an index having 255 characters long name |
|
|
|
|
|
Create an index having 2 characters long name |
|
|
|
|
|
Create an index having 256 characters long name |
|
|
|
|
|
TO BE CLARIFIED: Is it case-sensitive? non-letters? |
|
|
|
|
|
Create 2 tables with similar index names. |
successful |
|
|
|
|
Try to create 2 indexes with the same name in one table |
error |
|
|
|
|
KeySchema |
|
|
|
|
|
Create LSI with Hash different from table hash key (table should have H+R key). |
|
|
|
|
|
Create LSI for table with HASH w/o RANGE. Should fail. But will work for global indexes. |
|
|
|
|
|
Create similar indexes with different names (the same keys, etc) |
|
|
|
|
|
create an index just with HASH key, w/o RANGE |
|
|
|
|
|
‘Repeat’ key schema of the table. “For a local secondary index, the hash key must be the same as the table's hash key, and the range key must be a non-key table attribute.” |
|
|
|
|
|
Test for PutItem: Ensure range key of LSI is not a mandatory attribute. |
|
|
|
|
|
Projection |
|
|
|
|
|
Check usage of all projection types: KEYS_ONLY, INCLUDE, ALL. Query tests verify that it works as expected. |
|
|
|
|
|
Use NonKeyAttributes but skip ProjectionType |
|
|
|
|
|
Use NonKeyAttributes list with one attribute in it |
|
|
|
|
|
Use key attrs in the NonKeyAttributes list |
|
|
|
|
|
Make NonKeyAttributes list empty
|
|
|
|
|
|
Insert some non-key attrs in NonKeyAttributes list when Pr.Type is KEYS_ONLY. Then - similar but with ALL case. |
|
|
|
|
|
Create a table with 20 non-key attrs in one LSI. |
|
|
|
|
|
Create a table with 21 non-key attrs in one LSI. |
|
|
|
|
|
Create a table with 20 non-key attrs in multiple LSIs. |
|
|
|
|
|
Create a table with 21 non-key attrs in diff. LSIs, without repetitions of attr names. |
|
|
|
|
|
Create a table with 21 non-key attrs in diff. LSIs, with repetitions of attr names between LSI’s. |
|
|
|
|
|
GlobalSecondaryIndexes |
|
|
|
|
|
(out of scope now) |
|
|
|
|
|
Response |
|
|
|
|
|
Most of key-values in TableDescription are equal to data from Request |
Check and verify:
|
|
|
|
|
Attrs not present in Request but should be present in Response |
|
|
|
|
|
If LSI are not created, should this attr be present in response as empty list? |
|
|
|
|
|
Think how to check TableSizeBytes value. |
|
|
|
|
|
CreationDateTime verification: Find a way to get current time from the target system |
|
|
|
|
|
Exceptions |
|
|
|
|
|
LimitExceededException: Is related to in-progress states. Not possible to reproduce for now. |
|
|
|
|
|
ResourceInUseException: Recreate existing table (the case was mentioned above) |
|
|
|
|
|
InternalServerError: When this error [500] is expected and when some other error should appear? |
|
|
|
|
|
Additional |
|
|
|
|
|
Create more than 255 tables |
|
|
|
|
|
|
|
|
|
|
DeleteItem
DeleteTable
|
|
|
|
|
|
|
General |
|
|
|
|
|
Delete an existing table. Check if all the Response’s fields (see Table Description object) are equal to the appropriate table parameters |
|
|
|
|
|
Delete a non-existent table |
ResourceNotFoundException |
|
|
|
|
Delete a table specifying “” as a name |
|
|
|
|
|
Delete a table specifying NULL as a name |
|
|
|
|
|
Delete a table w/o specifying any parameters |
|
|
|
|
|
Delete a table having a name that contains only 2 or 1 symbol |
|
|
|
|
|
Delete a table specifying a name that contains more than 255 symbols |
ResourceNotFoundException ? |
|
|
|
|
Delete an existing table and, while the status is DELETING, run DeleteTable operation for the same table once again |
|
|
|
|
|
Results Verification |
|
|
|
|
|
|
|
|
|
|
|
Exceptions |
|
|
|
|
|
Simulate InternalServerError exception. Ideas? |
|
|
|
|
|
Simulate LimitExceededException exception. Ideas? Delete more than 10 tables in the same time |
|
|
|
|
|
Simulate ResourceInUseException exception. Ideas? Delete a table while it is in use by some other operation |
|
|
|
|
|
Simulate ResourceNotFoundException exception. Other ideas? |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
DescribeTable
|
|
|
|
|
|
|
General |
|
|
|
|
|
Run DescribeTable against the existing table. Check that all the required params are described correctly (see “Response Syntax” for DescribeTable statement) |
|
|
|
|
|
Run DescribeTable against the non-existent table (ResourceNotFoundException exception) |
|
|
|
|
|
Run DescribeTable specifying “” as a table name |
|
|
|
|
|
Run DescribeTable specifying NULL as a name |
|
|
|
|
|
Run DescribeTable w/o specifying any parameters |
|
|
|
|
|
Run DescribeTable specifying a name that contains only 2 or 1 symbol (causes an exception?) |
|
|
|
|
|
Run DescribeTable specifying a name that contains more than 255 symbols |
|
|
|
|
|
Simulate InternalServerError exception |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
GetItem
|
|
|
|
|
|
|
General |
|
|
|
|
|
Get an item specifying correct mandatory attributes |
|
|
|
|
|
Get an item specifying all the correct mandatory and optional ttributes |
|
|
|
|
|
TableName |
|
|
|
|
|
Valid (existing) table name |
|
|
|
|
|
Existing table name of 3 symbols |
|
|
|
|
|
Existing table name of 255 symbols |
|
|
|
|
|
From non-existent table name |
|
|
|
|
|
Empty name (“”) |
|
|
|
|
|
Less than 3 symbols long |
|
|
|
|
|
More than 255 symbols long |
|
|
|
|
|
AttributesToGet: |
|
|
|
|
|
Specified, correct items in the list |
|
|
|
|
|
Section not specified |
|
|
|
|
|
“AttributesToGet” term not specified, but there is a list of items in the section |
Exception/error |
|
|
|
|
Section AttributesToGet is specified, but there is just an empty list (no items) |
Exception/error |
|
|
|
|
Specified more attributes than exist in the table |
Exception/error |
|
|
|
|
Incorrect attributes: Wrong names |
Exception/error |
|
|
|
|
Incorrect attributes: Empty values like "" |
Exception/error |
|
|
|
|
Key |
|
|
|
|
|
One Key specified: “B” |
|
|
|
|
|
One Key specified: “N” |
|
|
|
|
|
One Key specified: “S” |
|
|
|
|
|
One key: “BS” |
|
|
|
|
|
One key: “NS” |
|
|
|
|
|
One key: “SS” |
|
|
|
|
|
Combination of "B", "N", "S" types |
|
|
|
|
|
Combination of "B", "N", "S", "BS", "NS", "SS" types |
|
|
|
|
|
Combination of “B”, “B”, "N", "N", “S”, “S”, “BS”, “BS”, "NS", "NS", “SS”, “SS” types |
|
|
|
|
|
The whole section “Key” not specified |
Exception/error |
|
|
|
|
Section “Key” specified, but the section content is empty |
Exception/error |
|
|
|
|
One incorrect key specified: something that is not in ("B", "N", "S", "BS", "NS", "SS") |
Exception/error |
|
|
|
|
In section “Key” there is a key of type “N” but a non-existent value specified for it |
No items returned in Response |
|
|
|
|
ConsistentRead |
|
|
|
|
|
= True |
|
|
|
|
|
= False |
|
|
|
|
|
Not specified |
|
|
|
|
|
= <Something_else> |
|
|
|
|
|
ReturnConsumedCapacity |
|
|
|
|
|
= INDEXES |
|
|
|
|
|
= TOTAL |
|
|
|
|
|
= NONE |
|
|
|
|
|
= <Something_else> |
|
|
|
|
|
Exceptions |
|
|
|
|
|
Simulate ConditionalCheckFailedException |
|
|
|
|
|
Simulate InternalServerError |
|
|
|
|
|
Simulate ItemCollectionSizeLimitExceededException |
|
|
|
|
|
Simulate ProvisionedThroughputExceededException |
|
|
|
|
|
Simulate ResourceNotFoundException |
|
|
|
|
|
|
|
|
|
|
ListTables
|
|
|
|
|
|
|
General |
|
|
|
|
|
Neither Limit nor ExclusiveStartTableName specified: Empty result (if there are no tables in this Tenant and Datacenter were created) |
|
|
|
|
|
Neither Limit nor ExclusiveStartTableName specified: A list of existing tables in this Tenant and Datacenter (if there are some in this Tenant and Datacenter tables) |
|
|
|
|
|
Neither Limit nor ExclusiveStartTableName specified: The List does not contain the tables having “CREATING” status |
|
|
|
|
|
Incorrect spelling of ListTables specified like: LisTables or Listables or ListTable, etc |
|
|
|
|
|
There is no “{” or “}” in the statement |
|
|
|
|
|
Limit |
|
|
|
|
|
The limit option is not specified and The number of existing tables is 5 |
1 page containing all 5 tables |
|
|
|
|
The limit option is not specified and The number of tables is 100 |
1 page containing all 100 tables |
|
|
|
|
Limit = 3 and number of existing tables is 100 |
The number of tables on the page is 3 and "LastEvaluatedTableName" parameter in Response contains the 3rd (last displayed on the 1st page) table name and There are 34 result pages in total |
|
|
|
|
Limit = 3 and "LastEvaluatedTableName" = <3d_table_name_in_the_table_list_of_the_previous_TC> and number of existing tables is 100 |
The number of tables on the second page is 3 and "LastEvaluatedTableName" parameter in Response contains the 3d (last on the second page) table name and There are 32 yet other pages able to be displayed |
|
|
|
|
Limit = 0 |
Error/exception |
|
|
|
|
Limit = -2 |
Error/exception |
|
|
|
|
Limit = "Some_strange_string" |
Error/exception |
|
|
|
|
Limit = "" |
Error/exception |
|
|
|
|
Limit = <nothing> |
Error/exception |
|
|
|
|
Case sensitivity (?) |
|
|
|
|
|
ExclusiveStartTableName |
|
|
|
|
|
The "ExclusiveStartTableName" option not specified |
|
|
|
|
|
An existing "ExclusiveStartTableName" specified |
|
|
|
|
|
An existing "ExclusiveStartTableName" specified when: There were no previous runs of ListTables statement |
|
|
|
|
|
An existing "ExclusiveStartTableName" specified when: Previous run of ListTables statement returned just one page |
|
|
|
|
|
"ExclusiveStartTableName" is 3 symbols long |
|
|
|
|
|
Table name is 255 symbols long |
|
|
|
|
|
Table name is 1 or 2 symbols long |
|
|
|
|
|
Table name is 256 or more symbols long |
|
|
|
|
|
A non-existent table name specified |
|
|
|
|
|
No table names specified |
|
|
|
|
|
An empty (like "ExclusiveStartTableName" :) table name specified |
|
|
|
|
|
Tenant |
|
|
|
|
|
Switch to another tenant and Perform ListTables operations: The "ExclusiveStartTableName" option not specified |
A unique (pertinent to this specific Tenant) list of tables returned |
|
|
|
|
Switch to another tenant and Perform ListTables operations: An existing table name specified in "ExclusiveStartTableName" |
A unique (pertinent to this specific Tenant) list of tables returned starting from the specified table name |
|
|
|
|
DataCenter (endpoint) Switch to another Datacenter and Perform ListTables operations: |
|
|
|
|
|
The "ExclusiveStartTableName" option not specified |
A unique (pertinent to this specific Datacenter) list of tables returned |
|
|
|
|
An existing table name specified in "ExclusiveStartTableName" |
A unique (pertinent to this specific Datacenter) list of tables returned starting from the specified table name |
|
|
|
|
|
|
|
|
|
PutItem
Note: For each test, check the ResponseValue for required options and values
|
|
|
|
|
|
|
General |
|
|
|
|
|
(Correct names of required fields) |
|
|
|
|
|
put item to INSERT 1 attribute (an existing table, 1 correct attribute “S”) |
|
|
|
|
|
put item to INSERT N attributes (an existing table, 1 correct attribute “S”) |
|
|
|
|
|
put item to UPDATE 1 attribute (an existing table, 1 correct attribute “S”), Exists = true |
|
|
|
|
|
put item to UPDATE N attributes (an existing table, 1 correct attribute “S”), Exists = true |
|
|
|
|
|
put item to UPDATE N attributes (an existing table, N correct attributes “S”), no “Exists” option specified (should be True by default) |
|
|
|
|
|
(Put item to UPDATE N attributes) |
|
|
|
|
|
an existing table, N correct attributes of type “B” |
|
|
|
|
|
an existing table, N correct attributes of type “BS” |
|
|
|
|
|
an existing table, N correct attributes of type “N” |
|
|
|
|
|
an existing table, N correct attributes of type “NS” |
|
|
|
|
|
an existing table, N correct attributes of type “SS” |
|
|
|
|
|
an existing table, N correct attributes of types “B”, “BS”, “N”, “NS”, “S”, “SS” |
|
|
|
|
|
Put item to UPDATE N attributes (an existing table, N correct attributes “SS”) |
|
|
|
|
|
Put the item having the same HASH and RANGE as the already existing one |
ok (Replacement with the new item) |
|
|
|
|
Put the item having the same HASH as the already existing one |
? |
|
|
|
|
Put the item having the same RANGE as the already existing one |
? |
|
|
|
|
(Expected conditions (all combinations)) |
|
|
|
|
|
CORRECT field name and "N" : "string" value |
|
|
|
|
|
NON-EXISTENT field name and "N" : "string" value |
|
|
|
|
|
EMPTY field name and "N" : "string" value |
|
|
|
|
|
CORRECT field name and "NS" : ["string"] values |
|
|
|
|
|
CORRECT field name and "B" : "string" value |
|
|
|
|
|
CORRECT field name and "BS" : ["string"] values |
|
|
|
|
|
CORRECT field name and "S" : "string" value |
|
|
|
|
|
CORRECT field name and "SS" : ["string"] values |
|
|
|
|
|
CORRECT field name and "N" : EMPTY value |
|
|
|
|
|
CORRECT field name and "<SOME_STRANGE_OR_EMPTY_VALUE>" : "string" value |
|
|
|
|
|
CORRECT field name and "NS" : "NON-EXISTENT_string" value |
|
|
|
|
|
(Exists value) |
|
|
|
|
|
Option omitted (by default) |
|
|
|
|
|
= True |
|
|
|
|
|
= False |
|
|
|
|
|
= “” |
|
|
|
|
|
= “something else” |
|
|
|
|
|
= <something_else> |
|
|
|
|
|
ReturnConsumedCapacity: |
|
|
|
|
|
= INDEXES |
|
|
|
|
|
= TOTAL |
|
|
|
|
|
= NONE |
|
|
|
|
|
= “something_else” |
|
|
|
|
|
= “” |
|
|
|
|
|
<no_value> |
|
|
|
|
|
incorrect spelling of RCC |
|
|
|
|
|
ReturnItemCollectionMetrics |
|
|
|
|
|
= SIZE |
|
|
|
|
|
= NONE |
|
|
|
|
|
= “something_else” |
|
|
|
|
|
= “” |
|
|
|
|
|
<no_value> |
|
|
|
|
|
incorrect spelling of RCM |
|
|
|
|
|
ReturnValues |
|
|
|
|
|
= NONE |
|
|
|
|
|
= ALL_OLD |
|
|
|
|
|
= UPDATED_OLD |
|
|
|
|
|
= ALL_NEW |
|
|
|
|
|
=s UPDATED_NEW |
|
|
|
|
|
= “” |
|
|
|
|
|
= “something_else” |
|
|
|
|
|
= empty |
|
|
|
|
|
<empty> |
|
|
|
|
|
incorrect spelling of “ReturnValues” |
|
|
|
|
|
Others |
|
|
|
|
|
Update an existing line while the key-value to be updated is in UPDATING status |
|
|
|
|
|
Update a non-existent table |
|
|
|
|
|
Update a table titled as “” |
|
|
|
|
|
Update a table by specifying only 2 letters of its title |
|
|
|
|
|
Update a table by specifying more than 256 letters of its title |
|
|
|
|
|
Update a table having no name |
|
|
|
|
|
(Insert an item) |
|
|
|
|
|
Specifying PrimaryKey as equal to the already existing line (this scenario update existing line) |
|
|
|
|
|
Specifying strange data type (not in B, BS, S, SS, N, NS) for a Value to be inserted |
|
|
|
|
|
Specifying two equal Key values in one operation (if we specified two attributes with equal names - in table put only value of the last attribute) |
|
|
|
|
|
Specifying no values for a Key |
|
|
|
|
|
Specifying non-existent Keys in “Expected” option |
|
|
|
|
|
Exceptions |
|
|
|
|
|
Simulate: ConditionalCheckFailedException exception |
|
|
|
|
|
Simulate: ItemCollectionSizeLimitExceededException exception |
|
|
|
|
|
Simulate: ProvisionedThroughputExceededException exception |
|
|
|
|
|
Simulate: ResourceNotFoundException exception (implements in "Update a non-existent table") |
|
|
|
|
|
TTL parameter tests |
|
|
|
|
|
|
|
|
|
|
Query
|
|
|
|
|
|
|
General |
|
|
|
|
|
Query statement contains the correct mandatory parameters only |
|
|
|
|
|
Query statement contains ALL the correct parameters |
|
|
|
|
|
TableName |
|
|
|
|
|
Valid name specified |
|
|
|
|
|
Non-existent name |
|
|
|
|
|
Empty name |
|
|
|
|
|
Less than 3 symbols long |
|
|
|
|
|
More than 255 symbols long |
|
|
|
|
|
Exactly 3 and 255 symbols long |
|
|
|
|
|
Upper and lower cases |
|
|
|
|
|
AttributesToGet |
|
|
|
|
|
Specified correct attributes |
|
|
|
|
|
Not specified |
|
|
|
|
|
Specified more attributes than exist in the table |
|
|
|
It’s positive |
|
Specified incorrect attributes: wrong names |
|
|
|
It’s positive |
|
Specified incorrect attributes: empty values like "" |
|
|
|
|
|
Exact correct list: Select = SPECIFIC_ATTRIBUTES |
Correct result |
|
|
|
|
Exact correct list: Select = ALL_ATTRIBUTES |
error |
|
|
|
|
Exact correct list: Select = ALL_PROJECTED_ATTRIBUTES |
error |
|
|
|
|
Exact correct list: Select = COUNT |
error |
|
|
|
|
Exact correct list: Select = “” |
error |
|
|
|
|
Exact correct list: Select = “something_else” |
error |
|
|
|
|
The option is not specified |
|
|
|
|
|
Completely incorrect list |
|
|
|
It’s positive |
|
Some correct and some incorrect names in the list |
|
|
|
It’s positive |
|
Empty list |
|
|
|
|
|
Not specified |
|
|
|
|
|
KeyConditions |
|
|
|
|
|
Key "B" specified |
|
|
|
|
|
Key "N" specified |
|
|
|
|
|
Key "S" specified |
|
|
|
|
|
Key "BS" specified |
|
|
|
|
|
Key "NS" specified |
|
|
|
|
|
Key "SS" specified |
|
|
|
|
|
Combination of "B" + "N" + "S" |
|
|
|
|
|
Combination of all 6 types ("B" + "N" + "S" + "BS" + "NS" + "SS") |
|
|
|
|
|
Not specified |
|
|
|
|
|
One incorrect key specified: something that is not in ("B", "N", "S", "BS", "NS", "SS") |
|
|
|
|
|
ConsistentRead |
|
|
|
|
|
= True |
|
|
|
|
|
Option not specified |
|
|
|
|
|
= “Something else” |
error |
|
|
|
|
ReturnConsumedCapacity |
|
|
|
|
|
= "INDEXES" |
|
|
|
|
|
= "TOTAL" |
|
|
|
|
|
= "NONE" |
|
|
|
|
|
= “Something_else” |
|
|
|
|
|
= “” |
|
|
|
|
|
= <Empty value> |
|
|
|
|
|
ExclusiveStartKey |
|
|
|
|
|
is String |
Records are taken starting by LastKeyValue of the previous operation |
|
|
|
|
is Number |
Records are taken starting by LastKeyValue of the previous operation |
|
|
|
|
is Binary |
Records are taken starting by LastKeyValue of the previous operation |
|
|
|
|
is S or N or B, but there was no previous operations |
What’s the content of ExclusiveStartKey? |
|
|
|
|
is Set of S or N or B |
error |
|
|
|
|
Not specified |
|
|
|
|
|
Incorrect ExclusiveStartKey |
Error |
|
|
|
|
IndexName |
|
|
|
|
|
correct Local SI (Secondary Index) |
|
|
|
|
|
correct Global SI |
|
|
|
|
|
non-existent LSI |
|
|
|
|
|
non-existent GSI |
|
|
|
|
|
Not specified |
|
|
|
|
|
Name length < 3 symbols |
error |
|
|
|
|
Name length > 255 symbols |
error |
|
|
|
|
Empty index name |
error |
|
|
|
|
Upper case index name |
? |
|
|
|
|
Lower case index name |
? |
|
|
|
|
Mix of Upper/lower case letters in index name |
? |
|
|
|
|
Limit |
|
|
|
|
|
Valid statement that returns > 10 lines, Limit = 5 |
5 lines returned and LastEvaluatedKey points to the last returned line |
|
|
|
|
Valid statement that returns N lines Limit = N*2 |
N lines returned and LastEvaluatedKey points to the last returned line |
|
|
|
|
Valid statement that returns N (< 5) lines Limit = 5 |
N lines returned and LastEvaluatedKey points to the last returned line |
|
|
|
|
Valid statement that returns N (< 5) lines Limit = 0 |
? |
|
|
|
|
Valid statement that returns data size > 1 MB Limit = 100 000 (that is more than 1 MB data size) |
Check that obtained data size is not more than 1 MB and LastEvaluatedKey points to the last returned line that does not exceed 1 MB |
|
|
|
|
ScanIndexForward |
|
|
|
|
|
= TRUE (by default) |
data are sorted by ascending of the index key |
|
|
|
|
= FALSE |
data are sorted by descending of the index key |
|
|
|
|
= “Another value” |
error |
|
|
|
|
= <empty value> |
? |
|
|
|
|
Select |
|
|
|
|
|
= ALL_ATTRIBUTES |
Returns all of the item attributes from the specified table or index |
|
|
|
|
= ALL_PROJECTED_ATTRIBUTES |
Retrieves all attributes which have been projected into the index |
|
|
|
|
= COUNT |
Returns the number of matching items, rather than the matching items themselves |
|
|
|
|
= SPECIFIC_ATTRIBUTES |
Returns only the attributes listed in AttributesToGet |
|
|
|
|
= <empty value> |
error |
|
|
|
|
= “” |
error |
|
|
|
|
= “Something else” |
error |
|
|
|
|
KeyConditions |
|
|
|
|
|
One correct field name ComparisonOperator = "EQ" |
Existing record should be returned (STRING, NUMBER, BOOLEAN) |
|
|
|
|
One correct field name ComparisonOperator = "EQ" AttributeValue is SET of Number or String or Boolean |
|
|
|
|
|
One correct field name ComparisonOperator = "EQ" Two AttributeValues specified (NUMBER and STRING) |
|
|
|
|
|
One correct field name (BINARY) ComparisonOperator = "EQ" AttributeValue is of type NUMBER or STRING |
error? |
|
|
|
|
One INcorrect field name ComparisonOperator = "EQ" Valid comparison value |
error ? |
|
|
|
|
One correct field name ComparisonOperator = "EQ" Comparison expression represents a combination that does not exist in the actual table |
No records returned |
|
|
|
|
One correct field name INVALID ComparisonOperator Valid comparison value |
error? |
|
|
|
|
One correct field name (Number or String or Boolean) ComparisonOperator = "LE" Valid comparison value (STRING or NUMBER or BOOLEAN) |
ok |
|
|
|
|
One correct field name ComparisonOperator = "LE" Two AttributeValues specified |
error? |
|
|
|
|
One correct field name ComparisonOperator = "LE" AttributeValue is SET of Number or String or Boolean |
error? |
|
|
|
|
One correct field name (Number or String or Boolean) ComparisonOperator = "LT" Valid comparison value (STRING or NUMBER or BOOLEAN) |
ok |
|
|
|
|
One correct field name ComparisonOperator = "LT" Two AttributeValues specified |
error? |
|
|
|
|
One correct field name (a set) ComparisonOperator = "LT" AttributeValue is SET of the same type |
error? |
|
|
|
|
One correct field name ComparisonOperator = "GE" Valid comparison value (STRING or NUMBER or BOOLEAN) |
ok |
|
|
|
|
One correct field name (N type) ComparisonOperator = "GE" Two (N and S) AttributeValues specified |
error |
|
|
|
|
One correct field name ComparisonOperator = "GE" AttributeValue is SET of Number or String or Boolean |
error |
|
|
|
|
One correct field name (Number or String or Boolean) ComparisonOperator = "GT" Valid comparison value (STRING or NUMBER or BOOLEAN) |
ok |
|
|
|
|
One correct field name ComparisonOperator = "GT" Two AttributeValues specified |
error? |
|
|
|
|
One correct field name (Number or String or Boolean) ComparisonOperator = "GT" AttributeValue is SET of Number or String or Boolean |
ok |
|
|
|
|
One correct field name ComparisonOperator = "BEGINS_WITH" Valid comparison value (STRING, BOOLEAN) |
ok |
|
|
|
|
One non-existent field name ComparisonOperator = "BEGINS_WITH" Valid comparison value (STRING, BOOLEAN) |
|
|
|
|
|
One correct field name ComparisonOperator = "BEGINS_WITH" Two AttributeValues specified |
error |
|
|
|
|
One correct field name ComparisonOperator = "BEGINS_WITH" AttributeValue is SET of Number or String or Boolean |
error |
|
|
|
|
One correct field name ComparisonOperator = "BETWEEN" Two valid comparison values |
ok |
|
|
|
|
One non-existent field name ComparisonOperator = "BETWEEN" Two valid comparison values |
error |
|
|
|
|
One correct field name ComparisonOperator = "BETWEEN" Only one AttributeValue specified |
error |
|
|
|
|
One correct field name ComparisonOperator = "BETWEEN" AttributeValue is SET of Number or String or Boolean |
error |
|
|
|
|
One correct field name ComparisonOperator = "" |
error |
|
|
|
|
One correct field name ComparisonOperator = <empty_value> |
error |
|
|
|
|
One correct field name ComparisonOperator = “something_else” |
error |
|
|
|
|
|
|
|
|
|
Scan
|
|
|
|
|
|
|
General |
|
|
|
|
|
scan stops and returns results if processed data size exceeds 1 MB |
|
|
|
|
|
Reproduce: Scan result is empty |
|
|
|
|
|
Parallel scan topic - out of scope for now |
|
|
|
|
|
TableName |
|
|
|
|
|
scan with only required parameter (table name) |
|
|
|
|
|
scan if name length is 3 |
|
|
|
|
|
scan if name length is 255 |
|
|
|
|
|
scan with name length < 3 |
error? |
|
|
|
|
scan with name length is > 255 |
error? |
|
|
|
|
upper-lower case in t.name |
? |
|
|
|
|
non-existent table name |
|
|
|
|
|
diff. symbols in t. name |
|
|
|
|
|
scan request without required parameter - table name |
|
|
|
|
|
AttributesToGet |
|
|
|
|
|
Skip it: all attrs should be returned |
|
|
|
|
|
include all params |
? |
|
|
|
|
empty list of attrs |
|
|
|
|
|
the only attr in the list is non-key attr |
|
|
|
|
|
the only attr in the list is attr that does not participate in a filter |
|
|
|
|
|
try nonexistent attrs |
should not be displayed in results? |
|
|
|
|
Filter can find items, but selected attrs are not present in those items: selected attrs are present in some other items |
|
|
|
|
|
Filter can find items, but selected attrs are not present in those items: selected attrs are not present in any items |
|
|
|
|
|
Repeat the same attr[s] in this list |
|
|
|
|
|
|
|
|
| |
|
Use LastEvaluatedKey from the previous scan. How to ensure that the scan really starts from this item? |
|
|
|
|
|
What if assign some existing key but scan operation was not executed before? No difference I think. |
|
|
|
|
|
Assign nonexistent value of key attr. |
|
|
|
|
|
Assign non-key attributes and their values. Try attrs of SET type? |
|
|
|
|
|
Limit |
|
|
|
|
|
Verify just the Limit number of items was scanned and LastEvaluatedKey is present in response |
|
|
|
|
|
Set Limit value so that scan processes more than 1 Mb of data before Limit value exceeds. Ensure it stops due to 1 Mb but not continue till Limit items processed |
|
|
|
|
|
Try empty, negative value, zero. |
|
|
|
|
|
ReturnConsumedCapacity |
|
|
|
|
|
Ensure response does not contain ConsumedCapacity (neither for table nor index(es)) if ReturnConsumedCapacity not present or equal to None in request |
|
|
|
|
|
Ensure response contains Capacity for table and indexes if TOTAL in request |
|
|
|
|
|
Ensure response contains Capacity for indexes only (not table) if INDEXES in request |
|
|
|
|
|
Try empty, invalid values. |
|
|
|
|
|
ScanFilter |
|
|
|
|
|
Ensure ScanFilter really filters? |
|
|
|
|
|
Ensure multiple conditions are treated as "AND" operations |
|
|
|
|
|
Try nonexistent attribute name (let’s assume it will be added with some item later) |
|
|
|
|
|
Try empty line instead of attribute name |
|
|
|
|
|
Assign empty line, None to ScanFilter |
|
|
|
|
|
(AttributeValueList) |
|
|
|
|
|
Use single value for appropriate comparison |
|
|
|
|
|
Use 2-element list for BETWEEN and IN |
|
|
|
|
|
Try to use 2+ element for IN |
? |
|
|
|
|
Try to use 2-element-list for operation like EQ |
|
|
|
|
|
Try empty list |
|
|
|
|
|
Try to skip this parameter at all |
|
|
|
|
|
Try data type different from attribute data type. For example, {"S":"6"} vs {"N":"6"}. |
does-not-match expected. |
|
|
|
|
About SETs: most of operators do not support SET types: Try to insert SET value for operator that does not support SET |
|
|
|
|
|
About SETs: most of operators do not support SET types: Ensure appropriate operators really support SETs. |
|
|
|
|
|
(ComparisonOperator) |
|
|
|
|
|
For every comparison operator, verify it correctly compares values of each type it supports (in most cases string, number, binary). Rewrite here tests enumerated above, for AttributeValueList. |
|
|
|
|
|
Verify each comparison operator is supported and compares correctly. |
|
|
|
|
|
Try invalid value for comp. operator (like EQINVALID) |
|
|
|
|
|
Select |
|
|
|
|
|
Ensure ALL_ATTRIBUTES return all attributes, especially if different items have different attributes. |
|
|
|
|
|
Ensure COUNT return just count, not items themselves. |
|
|
|
|
|
Ensure ALL_PROJECTED_ATTRIBUTES returns all attrs projected to the index. Should I request table or index? |
|
|
|
|
|
Set Select=SPECIFIC_ATTRIBUTES and enumerate attributes in AttributesToGet. Ensure it returns only the attributes listed in AttributesToGet (i.e. the same as without Select at all). |
|
|
|
|
|
Try to set Select=SPECIFIC_ATTRIBUTES if AttributesToGet was not set. |
|
|
|
|
|
How ALL_PROJECTED_ATTRIBUTES should work? |
|
|
|
|
|
Set Select to empty line or other invalid value. |
|
|
|
|
|
Use AttributesToGet together with Select equal to ALL_ATTRIBUTES or COUNT. What about ALL_PROJECTED_ATTRIBUTES? |
|
|
|
|
|
Segment |
|
|
|
|
|
parallel scan is out of scope for now. Should be ignored by MagnetoDB? |
|
|
|
|
|
TotalSegments |
|
|
|
|
|
parallel scan is out of scope for now. Should be ignored by MagnetoDB? |
|
|
|
|
|
Response |
|
|
|
|
|
ConsumedCapacity: is returned only if requested and corresponds to requested data
|
|
|
|
|
|
ConsumedCapacity: is empty if provisioned throughput is ignored now? |
|
|
|
|
|
Count: Ensure the value is correct |
|
|
|
|
|
Items: its length correspond to Count |
|
|
|
|
|
Items: should it be present if Select=COUNT? |
|
|
|
|
|
Items: ensure the items are correct |
|
|
|
|
|
LastEvaluatedKey: Ensure it’s present if limit was used and/or reached |
|
|
|
|
|
LastEvaluatedKey: Ensure this item is present in the current results and will not be present in the next results (if it passes filter, of course) |
|
|
|
|
|
ScannedCount: Ensure the value is correct. |
|
|
|
|
|
Exceptions |
|
|
|
|
|
Simulate ProvisionedThroughputExceededException |
|
|
|
|
|
ProvisionedThroughputExceededException: unable to reproduce w/o ProvisionedThroughput |
|
|
|
|
|
ResourceNotFoundException: request nonexistent table |
|
|
|
|
|
ResourceNotFoundException: request nonexistent index |
|
|
|
|
|
ResourceNotFoundException: request table in non Active state |
|
|
|
|
|
|
|
|
|
|
UpdateItem
UpdateTable
==
Indexing
|
|
|
|
|
|
|
CreateTable |
|
|
|
|
|
(LocalSecondaryIndexes) |
|
|
|
|
|
No LSIs specified for a table |
|
|
|
|
|
5 LSI specified for a table |
|
|
|
|
|
6 LSIs specified for a table |
error |
|
|
|
|
(IndexName) |
|
|
|
|
|
Some correct name specified |
|
|
|
|
|
Name is 3 symbols long |
|
|
|
|
|
Name is 255 symbols long |
|
|
|
|
|
Empty name |
error |
|
|
|
|
Option not specified |
error |
|
|
|
|
Name is 2 symbols long |
error |
|
|
|
|
Name is 256 symbols long |
error |
|
|
|
|
(KeySchema) |
|
|
|
|
|
Create 1 LSI for a table: - KeySchema (just 1 HASH key) - No projection |
error (REGION key not specified) |
|
|
|
|
Create 1 LSI for a table: - KeySchema (just 1 REGION key) - No projection |
error (HASH key not specified) |
|
|
|
|
Create 1 LSI for a table: - KeySchema (neither HASH nor REGION keys specified) - No projection |
error |
|
|
|
|
Non-existent (in the table declaration) attribute specified as a HASH key |
error |
|
|
|
|
Non-existant (in the table declaration) attribute specified as REGION key |
error |
|
|
|
|
The same attribute specified as both HASH and REGION keys |
error |
|
|
|
|
Option not specified |
error |
|
|
|
|
Create 1 LSI for a table: - KeySchema (1 HASH key, 1 REGION key) - No projection |
DescribeTable reports the same 1 LSI structure |
|
|
|
|
Create 1 LSI for a table: - KeySchema (1 HASH key, 1 REGION key) - Projection: 1 non-key attribute mentioned |
DescribeTable reports the same 1 LSI structure |
|
|
|
|
Create 1 LSI for a table: - KeySchema (1 HASH key, 1 REGION key) - Projection: several non-key attributes mentioned |
DescribeTable reports the same 1 LSI structure |
|
|
|
|
Create 1 LSI for a table: - KeySchema (1 HASH key, 1 REGION key) - Projection: one KEY (HASH) attribute mentioned |
error |
|
|
|
|
Create 1 LSI for a table: - KeySchema (1 HASH key, 1 REGION key) - Projection: several KEY (HASH, REGION) and non-key attributes mentioned |
DescribeTable reports the same 1 LSI structure |
|
|
|
|
Create 1 LSI for a table: - KeySchema (1 HASH key, 1 REGION key) - Projection: one KEY (REGION) attribute mentioned |
error |
|
|
|
|
Create 1 LSI for a table: - KeySchema (1 HASH key, 1 REGION key) - Projection: several non-key attributes mentioned |
DescribeTable reports the same 1 LSI structure |
|
|
|
|
Create 1 LSI for a table: - KeySchema (1 HASH key, 1 REGION key) - Projection: 20 non-key attributes mentioned |
DescribeTable reports the same 1 LSI structure
|
|
|
|
|
Create 1 LSI for a table: - KeySchema (1 HASH key, 1 REGION key) - Projection: 21 non-key attributes mentioned |
error |
|
|
|
|
Create 1 LSI for a table: - KeySchema (1 HASH key, 1 REGION key) - Projection: 1 NON-EXISTENT non-key attribute mentioned |
error (?) |
|
|
|
|
Create 1 LSI for a table: - KeySchema (1 HASH key, 1 REGION key) - Projection: several NON-EXISTENT non-key attributes mentioned |
error (?) |
|
|
|
|
(ProjectionType) |
|
|
|
|
|
Option not specified (omitted) |
|
|
|
|
|
= KEYS_ONLY |
|
|
|
|
|
= INCLUDE |
|
|
|
|
|
= ALL |
|
|
|
|
|
= <empty value> |
|
|
|
|
|
= "" |
|
|
|
|
|
= "Something else" |
|
|
|
|
|
Query |
|
|
|
|
|
No indexes specified (option "IndexName" omitted) |
Result data are not ordered |
|
|
|
|
Existing index (LSI) specified |
Result data are in the order described by the index |
|
|
|
|
More than one existing index (LSI) specified |
? |
|
|
|
|
Non-existent index (LSI) specified |
? |
|
|
|
|
Empty index name specified |
|
|
|
|
|
Specified index does not contain the attribute that is used in KeyConditions |
? |
|
|
|
|
|
|
|
|
|
Asynchronous Operations
Preconditions: while the just created table is in CREATING status…
|
|
|
|
|
|
|
Create table |
While the table is being created, its status is “CREATING” After that the status is “CREATED” |
|
|
|
|
Precondition: while the just created table is in CREATING status… |
|
|
|
|
|
Try reading data from this table |
error |
|
|
|
|
Create table with the same name |
error |
|
|
|
|
Delete the table |
error |
|
|
|
|
Run DescribeTable for this table |
error |
|
|
|
|
Read/Update/Remove items from the table |
error |
|
|
|
|
|
|
|
|
|
BulkWrite (PoC)
|
|
|
|
|
|
|
Table without indexes |
|
|
|
|
|
CORRECT item attributes names and content |
|
|
|
|
|
1-item portion
|
1 item was PUT into the table correctly |
|
|
|
|
25-item (max for 1 BulkWrite statement) portion |
25 items were PUT correctly and previously stored 1 item is ok |
|
|
|
|
More than 1 portion (> 25 items) |
All the items were PUT correctly and Previously stored data is ok |
|
|
|
|
INCORRECT item attributes names and content |
|
|
|
|
|
1-item portion: one incorrect KEY field name |
Error |
|
|
|
|
25-item (max for 1 BulkWrite statement) portion: 1 item with incorrect KEY field name |
24 items were PUT correctly and 1 item rejected and error code/message returned |
|
|
|
|
More than 1 portion (> 25 items): each portion contains 2 incorrect PUT statements |
All the correct items were PUT correctly and Previously stored data (24 items) is ok and error code/message returned for each (of 4) incorrect item |
|
|
|
|
Empty BulkWrite |
? |
|
|
|
|
Table with declared indexes (Same test cases as for the table without indexes) |
|
|
|
|
|
CORRECT item attributes names and content |
|
|
|
|
|
1-item portion
|
1 item was PUT into the table correctly |
|
|
|
|
25-item (max for 1 BulkWrite statement) portion |
25 items were PUT correctly and previously stored 1 item is ok |
|
|
|
|
More than 1 portion (> 25 items) |
All the items were PUT correctly and Previously stored data is ok |
|
|
|
|
INCORRECT item attributes names and content |
|
|
|
|
|
1-item portion: one incorrect KEY field name |
Error |
|
|
|
|
25-item (max for 1 BulkWrite statement) portion: 1 item with incorrect KEY field name |
24 items were PUT correctly and 1 item rejected and error code/message returned |
|
|
|
|
More than 1 portion (> 25 items): each portion contains 2 incorrect PUT statements |
All the correct items were PUT correctly and Previously stored data (24 items) is ok and error code/message returned for each (of 4) incorrect item |
|
|
|
|
Empty BulkWrite |
? |
|
|
|
|
Incorrect JSONs |
|
|
|
|
|
No items in JSON |
|
|
|
|
|
Incorrect JSON syntax |
|
|
|
|
|
Inappropriate (to the table keys structure) field names in JSON |
|
|
|
|
|
Inappropriate structure of JSON requests |
|
|
|
|
|
+ ALL PutItem TCs (as Bulk implementation of PutItem differcs from the standard one) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|