github.com/smugmug/godynamo@v0.0.0-20151122084750-7913028f6623/tests/README (about) 1 These tests differ from the *_test.go test files that are in the endpoint directories. 2 3 Those files are to be run with "go test" and do *not* involve accessing the live 4 DynamoDB service. It didn't seem wise to create unit tests that would involve billable 5 transactions with AWS. As a result, those unit tests merely assert the ability of 6 the endpoint libraries to be able to conform to the JSON standards published in the 7 AWS docs. 8 9 The files in this directory are LIVE tests. These programs will perform 10 transactions on the live DynamoDB service, and as a result, you will be billed for 11 them. You will need an AWS account and a ~/.aws-config.json file formatted correctly. 12 13 The filenames should explain what each test seeks to do. All tests should address 14 the same table. You should first run "create_table-livetest.go", and when you 15 are done, run "delete_table-livetest.go" to remove the table. Make sure the tablename 16 in the files does not conflict with a table name you are using already. 17 18 There are a number of programs here have "param-conf" in the filename. These are 19 variants of the tests that do not use the global conf struct. They should 20 work the same. These should be useful examples regarding the use of parameterized 21 conf variables for those wanting that functionality. For new users of this library, 22 you probably want to follow the "param-conf" examples. 23 24 Many of these tests are "noisy" - they output JSON requests and responses in many 25 cases. Just comment out parts that don't interest you. 26 27 These tests are not exhaustive. Over time hopefully they will become so. Patches welcome. 28 29 I recommend using these files more as example documentation than a test suite. Some of the 30 files make reference to items created or modified in others, so the order in which you 31 run them will be important.