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

["jay vyas (JIRA)" <ji...@apache.org>]

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

jay vyas edited comment on BIGTOP-1052 at 8/23/13 10:55 PM:
------------------------------------------------------------

which one : separating groovy scripts and using MAHOUT_HOME (idea 1 and 2) or using @Category notations (idea 3) ...

:) or just some reasonable combination of all of the above which makes the tests easier to run ? :) 
                
      was (Author: jayunit100):
    which one : separating groovy scripts (idea 1) or using @Category notations (idea 2) ...

or just some reasonable combination of both?
                  
> 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 
> 1) 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>
> And as another convenience for the purpose of easing the running of these tests, I suggest
> 2) Utilizing MAHOUT_HOME environmental variable in the tests if it is provided, so that the mahout package installation can be tested directly from tarballs.

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