Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Date: Tue, 5 Mar 2013 11:49:13 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: <JIRA.12635325.1362484046329.382759.1362484153527@arcas>
In-Reply-To: <JIRA.12635325.1362484046329@arcas>
References: <JIRA.12635325.1362484046329@arcas>
Subject: [jira] [Created] (HADOOP-9361) Write a set of tests to more
 strictly define the expected behavior of filesystems
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Steve Loughran created HADOOP-9361:
--------------------------------------

             Summary: Write a set of tests to more strictly define the expected behavior of filesystems
                 Key: HADOOP-9361
                 URL: https://issues.apache.org/jira/browse/HADOOP-9361
             Project: Hadoop Common
          Issue Type: Improvement
          Components: fs, test
    Affects Versions: 3.0.0
            Reporter: Steve Loughran


{{FileSystem}} and {{FileContract}} aren't tested rigorously enough -while HDFS gets tested downstream, other filesystems, such as blobstore bindings, don't.

The only tests that are common are those of {{FileSystemContractTestBase}}, which HADOOP-9258 shows is incomplete.

I propose 
# writing more tests which clarify expected behavior
# testing operations in the interface being in their own JUnit4 test classes, instead of one big test suite. 
# Having each FS declare via a properties file what behaviors they offer, such as atomic-rename, atomic-delete, umask, immediate-consistency -test methods can downgrade to skipped test cases if a feature is missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira