This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
Update moto to return proper information #531
Comments
bbangert
added a commit
that referenced
this issue
Jul 19, 2016
moto's testing harness is a bit buggy, it was returning errors in a semi-random manner during test-runs and failing to do validation checks that DynamoDB performs. As such we now spin up the Java DynamoDB local server for these test files to ensure consistent responses. Closes #531
bbangert
added a commit
that referenced
this issue
Jul 19, 2016
moto's testing harness is a bit buggy, it was returning errors in a semi-random manner during test-runs and failing to do validation checks that DynamoDB performs. As such we now spin up the Java DynamoDB local server for these test files to ensure consistent responses. Closes #531
bbangert
added a commit
that referenced
this issue
Jul 19, 2016
moto's testing harness is a bit buggy, it was returning errors in a semi-random manner during test-runs and failing to do validation checks that DynamoDB performs. As such we now spin up the Java DynamoDB local server for these test files to ensure consistent responses. Closes #531
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Two tests in websocket.py can fail due to odd heisenbugs in moto. In one case the Attributes response is a list, which is completely invalid per AWS. In the second case a conflict occurs for no apparent reason.
Moto is quite a few versions ahead of my fork, and has added some dynamodb features, but not the expression attributes we use, so my changes need to be merged back into the latest moto.
The text was updated successfully, but these errors were encountered: