You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bigtop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2013/08/23 20:47:51 UTC

[jira] [Commented] (BIGTOP-1052) Increase pom.xml configurability of Mahout Tests

    [ https://issues.apache.org/jira/browse/BIGTOP-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748847#comment-13748847 ] 

jay vyas commented on BIGTOP-1052:
----------------------------------

An alternative could be using the "@Category" annotations for some of the tests, and then having each test manage its own download of input data 
                
> Increase pom.xml configurability of Mahout Tests
> ------------------------------------------------
>
>                 Key: BIGTOP-1052
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1052
>             Project: Bigtop
>          Issue Type: Bug
>          Components: Tests
>            Reporter: jay vyas
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The TestMahoutExamples.groovy file is very comprehensive :) but also very long and complex.  There are other JIRA's that suggest that some of the tests in it fail.  It is different from TestHadoopExamples in that it is not easy to comment out the subtests to only run a subset.  
> I suggest refactoring tests into separate groovy scripts so that they can be filtered in the Pom, using the includes. i.e. 
> <includes>
>    <include>**/*Test*MovieLens*</include>
> </includes>

--
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