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

jay vyas edited comment on BIGTOP-1052 at 8/26/13 4:43 PM:
-----------------------------------------------------------

Ah yes - now to clarify: 

I think these tests could run in pure scripts, but, you wont get all of the 
pretty exception assertion reporting from failsafe.   

That seems okay and makes the bigtop smokes much more useable.  

Of course, for the mvn failsafe goal, you could *still* run them in failsafe, 
so that you have the best of both worlds: 

1) Pure groovy mahout tests that run as independant scripts

2) Java/Failsafe/JUNIT freindly tests which integrate with failsafe in a way 
that maven builds can still report success/failures on individual tests
                
      was (Author: jayunit100):
    Ah yes - now to clarify: 

I think these tests could run in pure scripts, but, you wont get all of the 
pretty exception assertion reporting from failsafe.   

That seems okay and makes the bigtop smokes much more useable.
                  
> 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

Reply via email to