hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-15987) ITestDynamoDBMetadataStore should check if test ddb table set properly before initializing the test
Date Tue, 11 Dec 2018 15:50:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-15987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717419#comment-16717419

Hudson commented on HADOOP-15987:

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15588 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/15588/])
HADOOP-15987. ITestDynamoDBMetadataStore should check if table (mackrorysd: rev c35de95a22e9f3dceae2ac5363f9d798415e8cb7)
* (edit) hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
* (edit) hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/s3guard/ITestDynamoDBMetadataStore.java

> ITestDynamoDBMetadataStore should check if test ddb table set properly before initializing
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
>         Attachments: HADOOP-15987.001.patch
> 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
> 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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message