[
https://issues.apache.org/jira/browse/BIGTOP-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated BIGTOP-1052:
---------------------------------------
Affects Version/s: 0.6.0
> Increase environment configurability/debugging of Mahout Tests
> --------------------------------------------------------------
>
> Key: BIGTOP-1052
> URL: https://issues.apache.org/jira/browse/BIGTOP-1052
> Project: Bigtop
> Issue Type: Bug
> Components: Tests
> Affects Versions: 0.6.0
> Reporter: jay vyas
> Assignee: jay vyas
> Fix For: 0.7.0
>
> Attachments: BIGTOP-1052.1.patch
>
> 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) [TO BE MOVED TO A SEPARATE JIRA] 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) [THIS JIRA: 1052] 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 was sent by Atlassian JIRA
(v6.2#6252)
