[HADOOP-15987] ITestDynamoDBMetadataStore should check if test ddb table set properly before initializing the test

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.0
• Component/s: fs/s3
• Assignee: Gabor Bota
• Reporter: Gabor Bota
• Created: 07/Dec/18 12:43
• Updated: 23/May/19 19:58
• Resolved: 11/Dec/18 15:31

Description

The jira covers the following:

• We should assert that the table name is configured when DynamoDBMetadataStore is used for testing, so the test should fail if it's not configured.
• We should assert that the test table is not the same as the production table, as the test table could be modified and destroyed multiple times during the test.
• This behavior should be added to the testing docs.

Assume from junit doc:

A set of methods useful for stating assumptions about the conditions in which a test is meaningful. 
A failed assumption does not mean the code is broken, but that the test provides no useful information. 
The default JUnit runner treats tests with failing assumptions as ignored.

A failed assert will cause test failure instead of just skipping the test.

Issue Links

• relates to: HADOOP-16327 s3a test docs to mention non-auth; or s3a tests to default to non-auth