[
https://issues.apache.org/jira/browse/BIGTOP-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jay vyas updated BIGTOP-1052:
-----------------------------
Description:
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.
was:
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>
> 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
