You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Gabor Bota (JIRA)" <ji...@apache.org> on 2018/12/07 12:45:00 UTC
[jira] [Updated] (HADOOP-15987) ITestDynamoDBMetadataStore should
check if test ddb table set properly before the test
[ https://issues.apache.org/jira/browse/HADOOP-15987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabor Bota updated HADOOP-15987:
--------------------------------
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|http://junit.sourceforge.net/javadoc/org/junit/Assume.html]:
{noformat}
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.
{noformat}
A failed assert will cause test failure instead of just skipping the test.
was:
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|http://junit.sourceforge.net/javadoc/org/junit/Assume.html]:
{noformat}
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.
{noformat}
A failed assert will cause test failure instead of just skipping the test.
> ITestDynamoDBMetadataStore should check if test ddb table set properly before the test
> --------------------------------------------------------------------------------------
>
> Key: HADOOP-15987
> URL: https://issues.apache.org/jira/browse/HADOOP-15987
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.1.0
> Reporter: Gabor Bota
> Assignee: Gabor Bota
> Priority: Major
>
> 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|http://junit.sourceforge.net/javadoc/org/junit/Assume.html]:
> {noformat}
> 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.
> {noformat}
> A failed assert will cause test failure instead of just skipping the test.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org