go-dynamock icon indicating copy to clipboard operation
go-dynamock copied to clipboard

Amazon Dynamo DB Mock Driver for Golang to Test Database Interactions

Results 16 go-dynamock issues
Sort by recently updated
recently updated
newest added

Hi! Thanks for the library! I noticed there was a problem where if the test suite calls out of order from the order that the expectations were set then we'd...

This allows partial expectations. It should solve #30

#15 identified this problem with BatchWriteItem, but I believe it applies to the other Item expectations as well. The following is a list of support for out of order execution:...

The `BatchWriteItem` method only works if requests are executed in the same order that expectations are added. I'm using `BatchWriteItem` in concurrent operations and would like to be able to...

I have a scenario I need to be able to presist the values and reload them in human readable form. Is this possible?

This enables the client to have separate references of the tableName, with the same value rather than obliging to reuse the same reference.

Hello, In my code the assignment of tableName is done when constructing the DynamoDB SDK payloads, by using a string value that is passed around the different packages of my...

The current implementation of UpdateItem / UpdateItemWithContext includes attributes that are currently not able to be asserting on by Dynamock. This PR adds the following: Adds ConditionExpression support Adds ExpressionAttributeNames...

Hello, please get rid of errors like this: `return &dynamodb.UpdateItemOutput{}, fmt.Errorf("Update Item Expectation Not Found")` and just `return &dynamodb.UpdateItemOutput{}, nil`, so this library can also be used for some stubbing...

I am testing that we gracefully handle conditional write errors. In my particular case, write an item, but don't overwrite it if already exists. * Operation = `PutItemWithContext()` * Condition...