Jump to: navigation, search

MagnetoDB/QA/Test cases

< MagnetoDB
Revision as of 14:57, 4 April 2014 by Max U (talk | contribs)

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

#
Description
Results
T
Status
Notes

General



BGI-1

BatchGetItem contains all the correct mandatory parameters


P


BGI-2

BatchGetItem contains all the correct parameters


P


TableName



BGI-

The only table name (existing) specified


P


BGI-

Several existing table names specified


P


BGI-

3 symbols long


P


BGI-

255 symbols long


P


BGI-

Less than 3 symbols long


N


BGI-

More than 255 symbols long


N


BGI-

Non-existent name


N


BGI-

Empty (like =)


N


BGI-

= ""


N


BGI-

Mixed case letters in the name


N


RequestItems



(AttributesToGet)



BGI-

Option not specified (by default)

All attrs are returned

P


BGI-

All existing attrs


P


BGI-

Some existing attrs


P


BGI-

Only non-existing attributes


N


BGI-

No attrs specified (whereas the Option exists)


N


BGI-

Some existing and some non-existent attrs specified


N


BGI-

Attrs list looks strange like "" or "//', 123, abc##, etc


N


(Keys)



BGI-

Single "B" key specified


P


BGI-

"B" and "N" keys specified


P


BGI-

Single "SS" key specified


P


BGI-

"SS" and "NS" keys specified


P


BGI-

"B", "S", "SS" and "NS" keys specified


P


BGI-

Incorrect key name


N


BGI-

Incorrect key type


N


BGI-

Key type omitted


N


BGI-

Key name omitted


N


BGI-

Empty key name


N


BGI-

Empty key type


N


(ConsistentRead)



BGI-

By default (if not specified)


P


BGI-

= TRUE


P


BGI-

= FALSE


P


BGI-

= ""


N


BGI-

Just = symbol


N


BGI-

= "Another_value"


N


ReturnConsumedCapasity



BGI-

By default (if not specified)


P


BGI-

= "INDEXES"


P


BGI-

= "TOTAL"


P


BGI-

= "NONE"


P


BGI-

= ""


N


BGI-

Just "="


N


BGI-

= "Another_value"


N


Exceptions



BGI-

InternalServerError


N


BGI-

ProvisionedThroughputExceededException


N


BGI-

ResourceNotFoundException


N


Limitations



(Data volume)



BGI-

Specify BatchGet to retrieve less than 1MB of data

"UnprocessedKeys" contains no items

P


BGI-

Specify BatchGet to retrieve exactly 1MB of data

"UnprocessedKeys" contains no items

P


BGI-

Specify BatchGet to retrieve more than 1MB (and < 2MB) of data

"UnprocessedKeys" contains items exceeding 1MB limit

P


BGI-

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

P


(Items number)



BGI-

Specify less than 100 items in the Request


P


BGI-

Specify exactly 100 items in the Request


P


BGI-

Specify more than 100 items in the Request

error?

N


Response



BGI-

Contains "GlobalSecondaryIndexes" section if there is (are) such for the table


P


BGI-

Contains "LocalSecondaryIndexes" section if there is (are) such for the table


P


BGI-

Contains both GSI and LSI sections if there are such for the table


P


BGI-

Result contains:

  • "ConsumedCapacity":
    • CapacityUnits
    • GSI
    • LSI
    • Table
    • TableName
  • "Responses"
  • "UnprocessedKeys"


P


BGI-





BatchWriteItem

#
Description
Results
T
Imp
Notes

General



BWI-1

Complete set of correct mandatory options


P
R


BWI-2

Complete set of correct all options


P
R


PutRequest



BWI-10

Correct Item string AND

"N" : "string" value


P


BWI-11

Non-existent Item string AND

"N" : "string" value

Error + UnprocessedItems contains unprocessed PutRequest Items

N


BWI-12

EMPTY Item string AND

"N" : "string"

Error + UnprocessedItems contains unprocessed PutRequest Items

N


BWI-13

Correct Item string and

"NS" : ["string"] values



BWI-14

Correct Item string and

"B" : "string" value



BWI-15

Correct Item string and

"BS" : ["string"] values



BWI-16

Correct Item string and

"S" : "string" value



BWI-17

Correct Item string and

"N" : EMPTY value

ValidationException + UnprocessedItems contains unprocessed PutRequest Items


BWI-18

Correct Item string and

"<SOME_STRANGE_OR_EMPTY_VALUE>" : "string" value

ValidationException + UnprocessedItems contains unprocessed PutRequest Items


BWI-19

Correct Item string and

"NS" : "non-existent_string" value

ValidationException + UnprocessedItems contains unprocessed PutRequest Items


BWI-20




DeleteRequest



BWI-30

Correct Key string and

"N" : "string" value



BWI-31

Non-existent Key string and

"N" : "string" value

Error + UnprocessedItems contains unprocessed DeleteRequest Items


BWI-32

EMPTY Key string and

"N" : "string" value

Error + UnprocessedItems contains unprocessed DeleteRequest Items


BWI-33

correct Key string and

"NS" : ["string"] values



BWI-34

correct Key string and

"B" : "string" value



BWI-35

correct Key string and

"BS" : ["string"] values



BWI-36

correct Key string and

"S" : "string" value


P
R


BWI-37

Correct Key string and

"SS" : ["string"] values



CombinedRequest



BWI-40

Specify in one statement:

correct Key string for

DeleteRequest "N" : "string" value AND

correct Item string for

PutRequest "N" : "string" value


P
R


BWI-41

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



BWI-42

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)



BWI-50

correct table name and

correct PutRequest parameters for the Item

Line(s) added correctly

P
R


BWI-51

Specify 25 correct table names and 

correct PutRequest parameters for the Items

Line(s) added correctly into all 25 tables


BWI-52

Specify 26 correct table names and 

correct PutRequest parameters for the Items

error/exception (?)


BWI-53

correct table name and

correct DeleteRequest parameters for the Key

Line(s) deleted correctly

P
R


BWI-54

INcorrect table name

correct PutRequest parameters for an Item

Check that UnprocessedItems contains unprocessed PutRequest Items:

  • TableName < 3 symbols
  • TableName > 255 symbols
  • Non-existent table name

Exception


BWI-55

Correct table name and

correct PutRequest parameters for the Item

Make total request size more than 1 MB (how to?)

error


BWI-56

correct table name and

correct PutRequest parameters for the Item

Any individual item in a batch exceeds 64 KB (how to?)

error


ReturnItemCollectionMetrics



BWI-60

is NONE (by default)

no statistics returned

N


BWI-61

is SIZE

statistics about item collections, if any, that were modified during the operation are returned in the response

N


BWI-62

is <Something_else>

error/exception

N


ReturnConsumedCapacity



BWI-63

is NONE (by default)


ConsumedCapacity is not included in the response

N


BWI-64

is TOTAL

the response includes ConsumedCapacity data for tables and indexes

N


BWI-65

is INDEXES

the response includes ConsumedCapacity for indexes only

N


BWI-66

is <Something_else> (and empty)

error/exception

N


Exceptions



BWI-70

Simulate InternalServerError



BWI-71

Simulate ItemCollectionSizeLimitExceededException



BWI-72

Simulate ProvisionedThroughputExceededException



BWI-73

Simulate ResourceNotFoundException



BWI-





CreateTable

#
Description
Results
T
Imp
Notes

General



CreT-1

Create table without any optional attributes, only all mandatory


P
R


CreT-2

Create a table specifying ALL (including mandatory) the correct parameters


P
R


CreT-3

Try to create two tables with the same name in the same region

ResourceInUseException expected.

N
P


CreT-

Try to create two tables with the same name in two different regions.


N
N


CreT-

Verify first status is CREATING, then ACTIVE


P
N


CreT-

What happens if read/write to/from table in CREATING state? Possible to reproduce?


N
N


CreT-

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?


N


CreT-

Try to create table w/o some mandatory attribute: AttributeDefinitions, KeySchema, ProvisionedThroughput, TableName.


N
R


AttributeDefinitions



Number of attributes



CreT-

create table with 1 attr


P
R


CreT-

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?


N


CreT-

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 ?

P


AttrName



CreT-

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).


P
R


CreT-

Try lengh 255+1 for key and indexes attr.


N
P


CreT-

Check size of non-key / non-index-projected attr names


N
N


CreT-

Try to send attr names without attr types.


N
P


CreT-

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).


P
R


CreT-

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?



CreT-

Try to create a table with attribute of some SET type. It should not be allowed.


P


KeySchema



CreT-

Create table with a key of HASH type.


P
R


CreT-

Create table with a key of HASH and RANGE type.


P
R


CreT-

Try to enumerate key attrs in wrong order: RANGE and then HASH attrs in the KeySchema list


N
R


CreT-

Try to create a table only with RANGE key


N
P


CreT-

Try to leave the list empty


N
P


CreT-

Try to add more than one HASH and/or RANGE attr. In general, add more than 2 attrs to the list.


N
P


CreT-

Try keytype different from HASH and RANGE.


N
P


CreT-

Try not to mention key attr in Definitions but only in KeySchema.


N
P


CreT-

Try to mention attr names not defined in AttrDefinitions.


N
P


ProvisionedThroughput

(for now, MagnetoDB ignores these values.)



CreT-

Set positive values.


P


CreT-

Try to mention not all mandatory attrs


N


CreT-

Try to pass non-number, negative number


N


TableName



CreT-

Name length is 3


P
R


CreT-

Name length is 255


P
R


CreT-

Name length < 3


N
P


CreT-

Name length > 255


N
P


CreT-

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.”


P


CreT-

Provide an empty table name.

exception ?

N
P


LocalSecondaryIndexes



CreT-

Create index without some of mandatory attributes.


N
N


Number of indexes



CreT-

Create 1 index for a table


P
N


CreT-

Create 5 indexes for the table


P
N


CreT-

Create 6 indexes for the table


N
N


CreT-

Set LSI attribute as an empty list


N


CreT-

“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



CreT-

Create an index having 3 characters long name


P
N


CreT-

Create an index having 255 characters long name


P
N


CreT-

Create an index having 2 characters long name


N
N


CreT-

Create an index having 256 characters long name


N
N


CreT-

TO BE CLARIFIED: Is it case-sensitive? non-letters?


N


CreT-

Create 2 tables with similar index names.

successful

P
N


CreT-

Try to create 2 indexes with the same name in one table

error

N
N


KeySchema



CreT-

Create LSI with Hash different from table hash key (table should have H+R key).


N


CreT-

Create LSI for table with HASH w/o RANGE. Should fail. But will work for global indexes.


N


CreT-

Create similar indexes with different names (the same keys, etc)


N


CreT-

create an index just with HASH key, w/o RANGE


N


CreT-

‘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.”


N


CreT-

Test for PutItem: Ensure range key of LSI is not a mandatory attribute.



Projection



CreT-

Check usage of all projection types: KEYS_ONLY, INCLUDE, ALL. Query tests verify that it works as expected.


P
N


CreT-

Use NonKeyAttributes but skip ProjectionType


N
N


CreT-

Use NonKeyAttributes list with one attribute in it


P
N


CreT-

Use key attrs in the NonKeyAttributes list


N
N


CreT-

Make NonKeyAttributes list empty



N
N


CreT-

Insert some non-key attrs in NonKeyAttributes list when Pr.Type is KEYS_ONLY. Then - similar but with ALL case.


N
N


CreT-

Create a table with 20 non-key attrs in one LSI.


P
N


CreT-

Create a table with 21 non-key attrs in one LSI.


N
N


CreT-

Create a table with 20 non-key attrs in multiple LSIs.


P
N


CreT-

Create a table with 21 non-key attrs in diff. LSIs, without repetitions of attr names.


N
N


CreT-

Create a table with 21 non-key attrs in diff. LSIs, with repetitions of attr names between LSI’s.


N
N


GlobalSecondaryIndexes



(out of scope now)



Response



CreT-

Most of key-values in TableDescription are equal to data from Request

Check and verify:

  • AttributeDefinitions
  • KeySchema
  • LocalSecondaryIndexes (also new attrs appear: IndexSizeBytes, IndexStatus, ItemCount)
  • ProvisionedThroughput (also new attrs appear: LastDecreaseDateTime, LastIncreaseDateTime - these two should be absent on creation, NumberOfDecreasesToday - should be 0 on creation)
  • TableName
P
R


CreT-

Attrs not present in Request but should be present in Response

  • CreationDateTime
  • ItemCount (should be 0 just after table creation)
  • TableSizeBytes (should be 0 on creation)
  • TableStatus (should be CREATING, then ACTIVE)
P
R


CreT-

If LSI are not created, should this attr be present in response as empty list?


P


CreT-

Think how to check TableSizeBytes value.



CreT-

CreationDateTime verification: Find a way to get current time from the target system


P


Exceptions



CreT-

LimitExceededException:

Is related to in-progress states. Not possible to reproduce for now.


N


CreT-

ResourceInUseException:

Recreate existing table (the case was mentioned above)


N
P


CreT-

InternalServerError:

When this error [500] is expected and when some other error should appear?


N


Additional



CreT-

Create more than 255 tables


N
N


CreT-





DeleteItem

DeleteTable

#
Description
Results
T
Imp
Notes

General



DelT-1

Delete an existing table. Check if all the Response’s fields (see Table Description object) are equal to the appropriate table parameters


P


DelT-

Delete a non-existent table

ResourceNotFoundException

N


DelT-

Delete a table specifying “” as a name


N


DelT-

Delete a table specifying NULL as a name


N


DelT-

Delete a table w/o specifying any parameters


N


DelT-

Delete a table having a name that contains only 2 or 1 symbol


N


DelT-

Delete a table specifying a name that contains more than 255 symbols

ResourceNotFoundException ?

N


DelT-

Delete an existing table and, while the status is DELETING, run DeleteTable operation for the same table once again


P


Results Verification



DelT-




Exceptions



DelT-

Simulate InternalServerError exception. Ideas?


N


DelT-

Simulate LimitExceededException exception. Ideas?

Delete more than 10 tables in the same time


N


DelT-

Simulate ResourceInUseException exception. Ideas? 

Delete a table while it is in use by some other operation


N


DelT-

Simulate ResourceNotFoundException exception. Other ideas?


N


DelT-




DelT-






DescribeTable

#
Description
Results
T
Imp
Notes

General



DesT-1

Run DescribeTable against the existing table. Check that all the required params are described correctly (see “Response Syntax” for DescribeTable statement)


P
R


DesT-

Run DescribeTable against the non-existent table (ResourceNotFoundException exception)


N
P


DesT-

Run DescribeTable specifying “” as a table name


N
P


DesT-

Run DescribeTable specifying NULL as a name


N


DesT-

Run DescribeTable w/o specifying any parameters


N


DesT-

Run DescribeTable specifying a name that contains only 2 or 1 symbol (causes an exception?)


N
P


DesT-

Run DescribeTable specifying a name that contains more than 255 symbols


N
P


DesT-

Simulate InternalServerError exception


N


DesT-




DesT-




DesT-





GetItem

#
Description
Results
T
Imp
Notes

General



GI-1

Get an item specifying correct mandatory attributes


P


GI-

Get an item specifying all the correct mandatory and optional ttributes


P


TableName



GI-

Valid (existing) table name


P
R


GI-

Existing table name of 3 symbols


P
R


GI-

Existing table name of 255 symbols


P
R


GI-

From non-existent table name


N


GI-

Empty name (“”)


N


GI-

Less than 3 symbols long


N


GI-

More than 255 symbols long


N


AttributesToGet:



GI-

Specified, correct items in the list


P
R


GI-

Section not specified


P
R


GI-

“AttributesToGet” term not specified, but there is a list of items in the section

Exception/error

N


GI-

Section AttributesToGet is specified, but there is just an empty list (no items)

Exception/error

N


GI-

Specified more attributes than exist in the table

Exception/error

N


GI-

Incorrect attributes: Wrong names

Exception/error


GI-

Incorrect attributes: Empty values like ""

Exception/error

N


Key



GI-

One Key specified: “B”


P
R


GI-

One Key specified: “N”


P
R


GI-

One Key specified: “S”


P
R


GI-

One key: “BS”



GI-

One key: “NS”



GI-

One key: “SS”



GI-

Combination of "B", "N", "S" types



GI-

Combination of "B", "N", "S", "BS", "NS", "SS" types



GI-

Combination of “B”, “B”, "N", "N", “S”, “S”, “BS”, “BS”, "NS", "NS", “SS”, “SS” types



GI-

The whole section “Key” not specified

Exception/error

N


GI-

Section “Key” specified, but the section content is empty

Exception/error

N


GI-

One incorrect key specified: something that is not in ("B", "N", "S", "BS", "NS", "SS")

Exception/error

N


GI-

In section “Key” there is a key of type “N” but a non-existent value specified for it

No items returned in Response

N
R


ConsistentRead



GI-

= True


P


GI-

= False


P


GI-

Not specified


P


GI-

= <Something_else>


N


ReturnConsumedCapacity



GI-

= INDEXES


P


GI-

= TOTAL


P


GI-

= NONE


P


GI-

= <Something_else>


N


Exceptions



GI-

Simulate ConditionalCheckFailedException


N


GI-

Simulate InternalServerError


N


GI-

Simulate ItemCollectionSizeLimitExceededException


N


GI-

Simulate ProvisionedThroughputExceededException


N


GI-

Simulate ResourceNotFoundException


N


GI-





ListTables

#
Description
Results
T
Imp
Notes

General



LisT-1

Neither Limit nor ExclusiveStartTableName specified:

Empty result (if there are no tables in this Tenant and Datacenter were created)


P
R


LisT-2

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)


P
R


LisT-3

Neither Limit nor ExclusiveStartTableName specified:

The List does not contain the tables having “CREATING” status


P


LisT-4

Incorrect spelling of ListTables specified like: LisTables or Listables or ListTable, etc


N


LisT-

There is no “{” or “}” in the statement


N


Limit



LisT-
 
The limit option is not specified and

The number of existing tables is 5

1 page containing all 5 tables

P
R


LisT-

The limit option is not specified and

The number of tables is 100

1 page containing all 100 tables

P
R


LisT-

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

P
P


LisT-

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

P
P


LisT-

Limit = 0

Error/exception

N
P


LisT-

Limit = -2

Error/exception

N
P


LisT-

Limit = "Some_strange_string"

Error/exception

N
P


LisT-

Limit = ""

Error/exception

N
P


LisT-

Limit = <nothing>

Error/exception

N
P


LisT-

Case sensitivity (?)



ExclusiveStartTableName



LisT-

The "ExclusiveStartTableName" option not specified


P
R


LisT-

An existing "ExclusiveStartTableName" specified


P
P


LisT-

An existing "ExclusiveStartTableName" specified when:

There were no previous runs of ListTables statement


P
P


LisT-

An existing "ExclusiveStartTableName" specified when:

Previous run of ListTables statement returned just one page


P
P


LisT-

"ExclusiveStartTableName" is 3 symbols long


P
P


LisT-

Table name is 255 symbols long


P
R


LisT-

Table name is 1 or 2 symbols long


N
P


LisT-

Table name is 256 or more symbols long


N
P


LisT-

A non-existent table name specified


N
P


LisT-

No table names specified


N
P


LisT-

An empty (like "ExclusiveStartTableName" :) table name specified


N
P


Tenant



LisT-

Switch to another tenant and

Perform ListTables operations:

The "ExclusiveStartTableName" option not specified

A unique (pertinent to this specific Tenant) list of tables returned

P


LisT-

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

P


DataCenter (endpoint)

Switch to another Datacenter and

Perform ListTables operations:



LisT-

The "ExclusiveStartTableName" option not specified

A unique (pertinent to this specific Datacenter) list of tables returned

P


LisT-

An existing table name specified in "ExclusiveStartTableName"

A unique (pertinent to this specific Datacenter) list of tables returned starting from the specified table name

P


LisT-





PutItem

Note: For each test, check the ResponseValue for required options and values

#
Description
Results
T
Imp
Notes

General



(Correct names of required fields)



PI-1

put item to INSERT 1 attribute (an existing table, 1 correct attribute “S”)


P
R


PI-2

put item to INSERT N attributes (an existing table, 1 correct attribute “S”)


P
R


PI-3

put item to UPDATE 1 attribute (an existing table, 1 correct attribute “S”), Exists = true


P
P


PI-4

put item to UPDATE N attributes (an existing table, 1 correct attribute “S”), Exists = true


P
P


PI-5

put item to UPDATE N attributes (an existing table, N correct attributes “S”), no “Exists” option specified (should be True by default)


P
P


(Put item to UPDATE N attributes)



PI-10

an existing table, N correct attributes of type “B”


P
P


PI-11

an existing table, N correct attributes of type “BS”


P
P


PI-12

an existing table, N correct attributes of type “N”


P
R


PI-13

an existing table, N correct attributes of type “NS”


P
R


PI-14

an existing table, N correct attributes of type “SS”


P
R


PI-15

an existing table, N correct attributes of types “B”, “BS”, “N”, “NS”, “S”, “SS”


P
P


PI-16

Put item to UPDATE N attributes (an existing table, N correct attributes “SS”)


P


PI-17

Put the item having the same HASH and RANGE as the already existing one

ok (Replacement with the new item)

P


PI-18

Put the item having the same HASH as the already existing one

?


PI-19

Put the item having the same RANGE as the already existing one

?


(Expected conditions (all combinations))


P


PI-30

CORRECT field name and "N" : "string" value



PI-31

NON-EXISTENT field name and "N" : "string" value



PI-32

EMPTY field name and "N" : "string" value



PI-33

CORRECT field name and "NS" : ["string"] values



PI-34

CORRECT field name and "B" : "string" value



PI-35

CORRECT field name and "BS" : ["string"] values



PI-36

CORRECT field name and "S" : "string" value



PI-37

CORRECT field name and "SS" : ["string"] values



PI-38

CORRECT field name and "N" : EMPTY value



PI-39

CORRECT field name and "<SOME_STRANGE_OR_EMPTY_VALUE>" : "string" value



PI-40

CORRECT field name and "NS" : "NON-EXISTENT_string" value



(Exists value)



PI-50

Option omitted (by default)


P


PI-51

= True


P


PI-52

= False


P


PI-53

= “”


N


PI-54

= “something else”


N


PI-55

= <something_else>


N


ReturnConsumedCapacity:



PI-60

= INDEXES



PI-61

= TOTAL



PI-62

= NONE



PI-63

= “something_else”



PI-64

= “”



PI-65

<no_value>



PI-66

incorrect spelling of RCC



ReturnItemCollectionMetrics



PI-70

= SIZE



PI-71

= NONE



PI-72

= “something_else”



PI-73

= “”



PI-74

<no_value>



PI-75

incorrect spelling of RCM



ReturnValues



PI-80

= NONE


R


PI-81

= ALL_OLD


P


PI-82

= UPDATED_OLD



PI-83

= ALL_NEW



PI-84

=s UPDATED_NEW



PI-85

= “”



PI-86

= “something_else”



PI-87

= empty



PI-88

<empty>



PI-89

incorrect spelling of “ReturnValues”



Others



PI-100

Update an existing line while the key-value to be updated is in UPDATING status


N


PI-101

Update a non-existent table


N
P


PI-102

Update a table titled as “”


N
P


PI-103

Update a table by specifying only 2 letters of its title


N
P


PI-104

Update a table by specifying more than 256 letters of its title


N
P


PI-105

Update a table having no name


N
P


(Insert an item)



PI-110

Specifying PrimaryKey as equal to the already existing line (this scenario update existing line)


N


PI-111

Specifying strange data type (not in B, BS, S, SS, N, NS) for a Value to be inserted


N
P


PI-112

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)


N


PI-113

Specifying no values for a Key


N
P


PI-114

Specifying non-existent Keys in “Expected” option


N
P


Exceptions



PI-120

Simulate: ConditionalCheckFailedException exception


P


PI-121

Simulate: ItemCollectionSizeLimitExceededException exception



PI-122

Simulate: ProvisionedThroughputExceededException exception



PI-123

Simulate: ResourceNotFoundException exception (implements in "Update a non-existent table")



TTL parameter tests



PI-





Query

#
Description
Results
T
Imp
Notes

General



Q-1

Query statement contains the correct mandatory parameters only


P
R


Q-2

Query statement contains ALL the correct parameters


P
R


TableName



Q-5

Valid name specified


P
R


Q-6

Non-existent name


N
R


Q-7

Empty name


N
R


Q-8

Less than 3 symbols long


N
P


Q-9

More than 255 symbols long


N
P


Q-10

Exactly 3 and 255 symbols long


P
P


Q-11

Upper and lower cases


P
R


AttributesToGet



Q-13

Specified correct attributes


P
R


Q-14

Not specified


R


Q-15

Specified more attributes than exist in the table


N
R

It’s positive

Q-16

Specified incorrect attributes: wrong names


N
R

It’s positive

Q-17

Specified incorrect attributes: empty values like ""


N
P


Q-18

Exact correct list:

Select = SPECIFIC_ATTRIBUTES

Correct result

P
R


Q-19

Exact correct list:

Select = ALL_ATTRIBUTES

error

N
P


Q-20

Exact correct list:

Select = ALL_PROJECTED_ATTRIBUTES

error

N
P


Q-21

Exact correct list:

Select = COUNT

error

N
P


Q-22

Exact correct list:

Select = “”

error

N
P


Q-23

Exact correct list:

Select = “something_else”

error

N
P


Q-24

The option is not specified


R


Q-25

Completely incorrect list


N
R

It’s positive

Q-26

Some correct and some incorrect names in the list


N
R

It’s positive

Q-27

Empty list


N
P


Q-28

Not specified


P
P


KeyConditions



Q-31

Key "B" specified


P
R


Q-32

Key "N" specified


P
R


Q-33

Key "S" specified


P
R


Q-34

Key "BS" specified


P


Q-35

Key "NS" specified


P


Q-36

Key "SS" specified


P


Q-37

Combination of "B" + "N" + "S"


P


Q-38

Combination of all 6 types ("B" + "N" + "S" + "BS" + "NS" + "SS")


P


Q-39

Not specified


N
P


Q-40

One incorrect key specified: something that is not in ("B", "N", "S", "BS", "NS", "SS")


N


ConsistentRead



Q-43

= True


P
R


Q-44

Option not specified


P
R


Q-45

= “Something else”

error

N
R


ReturnConsumedCapacity



Q-49

= "INDEXES"


P


Q-50

= "TOTAL"


P


Q-51

= "NONE"


P


Q-52

= “Something_else”


N


Q-53

= “”


N


Q-54

= <Empty value>


N


ExclusiveStartKey



Q-57

is String

Records are taken starting by LastKeyValue of the previous operation

P


Q-58

is Number

Records are taken starting by LastKeyValue of the previous operation

P


Q-59

is Binary

Records are taken starting by LastKeyValue of the previous operation

P


is S or N or B, but there was no previous operations

What’s the content of ExclusiveStartKey?


Q-62

is Set of S or N or B

error

N


Q-63

Not specified


P


Q-64

Incorrect ExclusiveStartKey

Error

N


IndexName



Q-67

correct Local SI (Secondary Index)


P


Q-68

correct Global SI


P


Q-69

non-existent LSI


N


Q-70

non-existent GSI


N


Q-71

Not specified


P


Q-72

Name length < 3 symbols

error

N


Q-73

Name length > 255 symbols

error

N


Q-74

Empty index name

error


Q-75

Upper case index name

?


Q-76

Lower case index name

?


Q-77

Mix of Upper/lower case letters in index name

?


Limit



Q-80

Valid statement that returns > 10 lines, 

Limit = 5

5 lines returned and LastEvaluatedKey points to the last returned line

P
R


Q-81

Valid statement that returns N lines

Limit = N*2

N lines returned and LastEvaluatedKey points to the last returned line

P
R


Q-82

Valid statement that returns N (< 5) lines

Limit = 5

N lines returned and LastEvaluatedKey points to the last returned line

P
R


Q-83

Valid statement that returns N (< 5) lines

Limit = 0

?

R


Q-84

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

N


ScanIndexForward



Q-87

= TRUE (by default)

data are sorted by ascending of the index key

P


Q-88

= FALSE

data are sorted by descending of the index key

P


Q-89

= “Another value”

error

N


Q-90

= <empty value>

?


Select



Q-93

= ALL_ATTRIBUTES

Returns all of the item attributes from the specified table or index

P


Q-94

= ALL_PROJECTED_ATTRIBUTES

Retrieves all attributes which have been projected into the index

P


Q-95

= COUNT

Returns the number of matching items, rather than the matching items themselves


Q-96

= SPECIFIC_ATTRIBUTES

Returns only the attributes listed in AttributesToGet

P


Q-97

= <empty value>

error

N


Q-98

= “”

error

N


Q-99

= “Something else”

error

N


KeyConditions



Q-102

One correct field name 

ComparisonOperator = "EQ"

Existing record should be returned (STRING, NUMBER, BOOLEAN)

P
R


Q-103

One correct field name

ComparisonOperator = "EQ"

AttributeValue is SET of Number or String or Boolean


P
P


Q-104

One correct field name

ComparisonOperator = "EQ"

Two AttributeValues specified (NUMBER and STRING)


P
P


Q-105

One correct field name (BINARY)

ComparisonOperator = "EQ"

AttributeValue is of type NUMBER or STRING

error?

N
P


Q-106

One INcorrect field name

ComparisonOperator = "EQ"

Valid comparison value

error ?

N
R


Q-107

One correct field name

ComparisonOperator = "EQ"

Comparison expression represents a combination that does not exist in the actual table

No records returned

P
R


Q-108

One correct field name

INVALID ComparisonOperator

Valid comparison value

error?

N
P


Q-109

One correct field name (Number or String or Boolean)

ComparisonOperator = "LE"

Valid comparison value (STRING or NUMBER or BOOLEAN)

ok

P
R


Q-110

One correct field name

ComparisonOperator = "LE"

Two AttributeValues specified

error?

N
P


Q-111

One correct field name

ComparisonOperator = "LE"

AttributeValue is SET of Number or String or Boolean

error?

N


Q-112

One correct field name (Number or String or Boolean)

ComparisonOperator = "LT"

Valid comparison value (STRING or NUMBER or BOOLEAN)

ok

P
R


Q-113

One correct field name

ComparisonOperator = "LT"

Two AttributeValues specified

error?

N
P


Q-114

One correct field name (a set)

ComparisonOperator = "LT"

AttributeValue is SET of the same type

error?

N


Q-115

One correct field name

ComparisonOperator = "GE"

Valid comparison value (STRING or NUMBER or BOOLEAN)

ok

P
R


Q-116

One correct field name (N type)

ComparisonOperator = "GE"

Two (N and S) AttributeValues specified

error

N
P


Q-117

One correct field name

ComparisonOperator = "GE"

AttributeValue is SET of Number or String or Boolean

error

N


Q-118

One correct field name (Number or String or Boolean)

ComparisonOperator = "GT"

Valid comparison value (STRING or NUMBER or BOOLEAN)

ok

P
R


Q-119

One correct field name

ComparisonOperator = "GT"

Two AttributeValues specified

error?

N
P


Q-120

One correct field name (Number or String or Boolean)

ComparisonOperator = "GT"

AttributeValue is SET of Number or String or Boolean

ok

P


Q-121

One correct field name

ComparisonOperator = "BEGINS_WITH"

Valid comparison value (STRING, BOOLEAN)

ok

P
R


Q-122

One non-existent field name

ComparisonOperator = "BEGINS_WITH"

Valid comparison value (STRING, BOOLEAN)


P
P


Q-123

One correct field name

ComparisonOperator = "BEGINS_WITH"

Two AttributeValues specified

error

N
P


Q-124

One correct field name

ComparisonOperator = "BEGINS_WITH"

AttributeValue is SET of Number or String or Boolean

error

N
P


Q-125

One correct field name

ComparisonOperator = "BETWEEN"

Two valid comparison values

ok

P
R


Q-126

One non-existent field name

ComparisonOperator = "BETWEEN"

Two valid comparison values

error

N
P


Q-127

One correct field name

ComparisonOperator = "BETWEEN"

Only one AttributeValue specified

error

N
P


Q-128

One correct field name

ComparisonOperator = "BETWEEN"

AttributeValue is SET of Number or String or Boolean

error

N
P


Q-129

One correct field name

ComparisonOperator = ""

error

N
P


Q-130

One correct field name

ComparisonOperator = <empty_value>

error

N
P


Q-131

One correct field name

ComparisonOperator = “something_else”

error

N
P


Q-





Scan

#
Description
Results
T
Imp
Notes

General



Sc-1

scan stops and returns results if processed data size exceeds 1 MB


P


Sc-

Reproduce: Scan result is empty


P


Sc-

Parallel scan topic - out of scope for now



TableName



Sc-

scan with only required parameter (table name)


P


Sc-

scan if name length is 3


P


Sc-

scan if name length is 255


P


Sc-

scan with name length < 3

error?

N


Sc-

scan with name length is > 255

error?

N


Sc-

upper-lower case in t.name

?


Sc-

non-existent table name


N


Sc-

diff. symbols in t. name


N


Sc-

scan request without required parameter - table name


N


AttributesToGet



Sc-

Skip it: all attrs should be returned


P


Sc-

include all params

?

P


Sc-

empty list of attrs


N


Sc-

the only attr in the list is non-key attr


P


Sc-

the only attr in the list is attr that does not participate in a filter


P


Sc-

try nonexistent attrs

should not be displayed in results?


Sc-

Filter can find items, but selected attrs are not present in those items:

selected attrs are present in some other items



Sc-

Filter can find items, but selected attrs are not present in those items:

selected attrs are not present in any items



Sc-

Repeat the same attr[s] in this list


N


ExclusiveStartKey



Sc-

Use LastEvaluatedKey from the previous scan. How to ensure that the scan really starts from this item?


P


Sc-

What if assign some existing key but scan operation was not executed before? No difference I think.


N


Sc-

Assign nonexistent value of key attr.


N


Sc-

Assign non-key attributes and their values. Try attrs of SET type?


N


Limit



Sc-

Verify just the Limit number of items was scanned and LastEvaluatedKey is present in response


P


Sc-

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


P


Sc-

Try empty, negative value, zero.


P


ReturnConsumedCapacity



Sc-

Ensure response does not contain ConsumedCapacity (neither for table nor index(es)) if ReturnConsumedCapacity not present or equal to None in request


P


Sc-

Ensure response contains Capacity for table and indexes if TOTAL in request


P


Sc-

Ensure response contains Capacity for indexes only (not table) if INDEXES in request


P


Sc-

Try empty, invalid values.


N


ScanFilter



Sc-

Ensure ScanFilter really filters?



Sc-

Ensure multiple conditions are treated as "AND" operations


P


Sc-

Try nonexistent attribute name (let’s assume it will be added with some item later)


N


Sc-

Try empty line instead of attribute name


N


Sc-

Assign empty line, None to ScanFilter


N


(AttributeValueList)



Sc-

Use single value for appropriate comparison


P


Sc-

Use 2-element list for BETWEEN and IN


P


Sc-

Try to use 2+ element for IN

?


Sc-

Try to use 2-element-list for operation like EQ


N


Sc-

Try empty list


N


Sc-

Try to skip this parameter at all


N


Sc-

Try data type different from attribute data type. For example,

{"S":"6"} vs {"N":"6"}.

does-not-match expected.

N


Sc-

About SETs: most of operators do not support SET types:

Try to insert SET value for operator that does not support SET


N


Sc-

About SETs: most of operators do not support SET types:

Ensure appropriate operators really support SETs.


P


(ComparisonOperator)



Sc-

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.


P


Sc-

Verify each comparison operator is supported and compares correctly.


P


Sc-

Try invalid value for comp. operator (like EQINVALID)


N


Select



Sc-

Ensure ALL_ATTRIBUTES return all attributes, especially if different items have different attributes.


P


Sc-

Ensure COUNT return just count, not items themselves.


P


Sc-

Ensure ALL_PROJECTED_ATTRIBUTES returns all attrs projected to the index. Should I request table or index?


P


Sc-

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).


P


Sc-

Try to set Select=SPECIFIC_ATTRIBUTES if AttributesToGet was not set.


N


Sc-

How ALL_PROJECTED_ATTRIBUTES should work?



Sc-

Set Select to empty line or other invalid value.


N


Sc-

Use AttributesToGet together with Select equal to ALL_ATTRIBUTES or COUNT. What about ALL_PROJECTED_ATTRIBUTES?


N


Segment



Sc-

parallel scan is out of scope for now. Should be ignored by MagnetoDB?



TotalSegments



Sc-

parallel scan is out of scope for now. Should be ignored by MagnetoDB?



Response



Sc-

ConsumedCapacity: is returned only if requested and corresponds to requested data



P


Sc-

ConsumedCapacity: is empty if provisioned throughput is ignored now?


P


Sc-

Count: Ensure the value is correct


P


Sc-

Items: its length correspond to Count



Sc-

Items: should it be present if Select=COUNT?



Sc-

Items: ensure the items are correct



Sc-

LastEvaluatedKey:

Ensure it’s present if limit was used and/or reached



Sc-

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)



Sc-

ScannedCount: Ensure the value is correct.



Exceptions



Sc-

Simulate ProvisionedThroughputExceededException



Sc-

ProvisionedThroughputExceededException: unable to reproduce w/o ProvisionedThroughput



Sc-

ResourceNotFoundException: request nonexistent table



Sc-

ResourceNotFoundException:

request nonexistent index



Sc-

ResourceNotFoundException:

request table in non Active state



Sc-





UpdateItem

UpdateTable

==

Indexing

#
Description
Results
T
Status
Notes

CreateTable



(LocalSecondaryIndexes)



I-1

No LSIs specified for a table



I-2

5 LSI specified for a table



I-3

6 LSIs specified for a table

error

N


(IndexName)



I-10

Some correct name specified



I-11

Name is 3 symbols long



I-12

Name is 255 symbols long



I-13

Empty name

error

N


I-14

Option not specified

error

N


I-15

Name is 2 symbols long

error

N


I-16

Name is 256 symbols long

error

N


(KeySchema)



I-20

Create 1 LSI for a table:

- KeySchema (just 1 HASH key)

- No projection

error (REGION key not specified)

N


I-21

Create 1 LSI for a table:

- KeySchema (just 1 REGION key)

- No projection

error (HASH key not specified)

N


I-22

Create 1 LSI for a table:

- KeySchema (neither HASH nor REGION keys specified)

- No projection

error

N


I-23

Non-existent (in the table declaration) attribute specified as a HASH key

error

N


I-24

Non-existant (in the table declaration) attribute specified as REGION key

error

N


I-25

The same attribute specified as both HASH and REGION keys

error

N


I-26

Option not specified

error

N


I-27

Create 1 LSI for a table:

- KeySchema (1 HASH key, 1 REGION key)

- No projection

DescribeTable reports the same 1 LSI structure


I-28

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


I-29

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


I-30

Create 1 LSI for a table:

- KeySchema (1 HASH key, 1 REGION key)

- Projection: one KEY (HASH) attribute mentioned

error


I-31

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


I-32

Create 1 LSI for a table:

- KeySchema (1 HASH key, 1 REGION key)

- Projection: one KEY (REGION) attribute mentioned

error

N


I-33

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


I-34

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



I-35

Create 1 LSI for a table:

- KeySchema (1 HASH key, 1 REGION key)

- Projection: 21 non-key attributes mentioned

error

N


I-36

Create 1 LSI for a table:

- KeySchema (1 HASH key, 1 REGION key)

- Projection: 1 NON-EXISTENT non-key attribute mentioned

error (?)


I-37

Create 1 LSI for a table:

- KeySchema (1 HASH key, 1 REGION key)

- Projection: several NON-EXISTENT non-key attributes mentioned

error (?)

N


(ProjectionType)



I-40

Option not specified (omitted)



I-41

= KEYS_ONLY



I-42

= INCLUDE



I-43

= ALL



I-44

= <empty value>


N


I-45

= ""


N


I-46

= "Something else"


N


Query



I-50

No indexes specified (option "IndexName" omitted)

Result data are not ordered


I-51

Existing index (LSI) specified

Result data are in the order described by the index


I-52

More than one existing index (LSI) specified

?


I-53

Non-existent index (LSI) specified

?

N


I-54

Empty index name specified


N


I-55

Specified index does not contain the attribute that is used in KeyConditions

?


I-56





Asynchronous Operations

Preconditions: while the just created table is in CREATING status…


#
Description
Results
T
Status
Notes
AsO-1

Create table

While the table is being created, its status is “CREATING”

After that the status is “CREATED”

P


Precondition: while the just created table is in CREATING status…



AsO-10

Try reading data from this table

error

N


AsO-11

Create table with the same name

error

N


AsO-12

Delete the table

error

N


AsO-13

Run DescribeTable for this table

error

N


AsO-14

Read/Update/Remove items from the table

error

N






BulkWrite (PoC)

#
Description
Results
T
Status
Notes

Table without indexes



CORRECT item attributes names and content



BulkW-1

1-item portion


1 item was PUT into the table correctly

P


BulkW-2

25-item (max for 1 BulkWrite statement) portion

25 items were PUT correctly and

previously stored 1 item is ok

P


BulkW-3

More than 1 portion (> 25 items)

All the items were PUT correctly and

Previously stored data is ok

P


INCORRECT item attributes names and content



BulkW-4

1-item portion: one incorrect KEY field name

Error

N


BulkW-5

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


BulkW-6

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


BulkW-7

Empty BulkWrite

?


Table with declared indexes

(Same test cases as for the table without indexes)



CORRECT item attributes names and content



BulkW-8

1-item portion


1 item was PUT into the table correctly

P


BulkW-9

25-item (max for 1 BulkWrite statement) portion

25 items were PUT correctly and

previously stored 1 item is ok

P


BulkW-10

More than 1 portion (> 25 items)

All the items were PUT correctly and

Previously stored data is ok

P


INCORRECT item attributes names and content



BulkW-11

1-item portion: one incorrect KEY field name

Error

N


BulkW-12

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


BulkW-13

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


BulkW-14

Empty BulkWrite

?


Incorrect JSONs



BulkW-15

No items in JSON


N


BulkW-16

Incorrect JSON syntax


N


BulkW-17

Inappropriate (to the table keys structure) field names in JSON


N


BulkW-18

Inappropriate structure of JSON requests


N


+ ALL PutItem TCs

(as Bulk implementation of PutItem differcs from the standard one)



BulkW-19







Retrieved from "https://wiki.openstack.org/w/index.php?title=MagnetoDB/QA/Test_cases&oldid=47753"