hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Boudnik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-505) Convert the file including 10 minutes run's tests into the test harness test suite
Date Fri, 24 Jul 2009 21:01:16 GMT

    [ https://issues.apache.org/jira/browse/HDFS-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735156#action_12735156

Konstantin Boudnik commented on HDFS-505:

It is a feature indeed, that's why this JIRA has been opened as an improvement rather than
a bug.

I'm totally agree that tagging is a way MORE superior solution to a haness' suite constructions.
One of the best features of tagging solutions I have proposed in HADOOP-4901 is an ability
to tag a single test case which is very difficult to do with JUnit's built in Suites. I'm
adding Owen to the watcher's list for he had a very strong opinion of why JUnit suites have
to be used instead of say Spring-test framework annotations.

This whole 10 minutes test list has exposed the problem with suites vs. metadata vs. external
test lists. I'm Ok with external test lists but for two reasons:
- they require an extra maintenance step is needed
- at this moment, HDFS seems to be the only Hadoop's project which uses test lists. Thus it
creates a potential future inconsistency. 

> Convert the file including 10 minutes run's tests into the test harness test suite
> ----------------------------------------------------------------------------------
>                 Key: HDFS-505
>                 URL: https://issues.apache.org/jira/browse/HDFS-505
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: build, test
>            Reporter: Konstantin Boudnik
> This issue is created to track the conversion of external testlist for 10 minutes tests
into JUnit test suite.
> It would be consistent through the bigger Hadoop project to have 10 minutes tests to
be collected in a JUnit's test suite instead of an external file (as of now). 
> The reason is simple: with the file we'd have two points of maintenance: tests source
code and one an auxiliary text files. Besides, a general approach is to use JUnit's suites
for tagging purposes, thus having a suite here would be more uniform.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message