[BIGTOP-1052] Increase environment configurability/debugging of Mahout Tests

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.6.0
• Fix Version/s: 0.7.0
• Component/s: tests
• Assignee: jay vyas
• Reporter: jay vyas
• Created: 23/Aug/13 18:42
• Updated: 26/Mar/14 22:19
• Resolved: 27/Aug/13 17:32

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) [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.