[
https://issues.apache.org/jira/browse/BIGTOP-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942702#comment-13942702
]
Konstantin Boudnik commented on BIGTOP-1257:
--------------------------------------------
Great minds think alike apparently ;) I've asking Dasha to look into how we can
suite up (as in test suite) longevity runs. My line of thinking was to have a
JUnit Suite class that will combine DFSIO, SLive (possibly others) so that one
can variate the load and time of the runs by simply setting some external
parameters.
Looks like you're thinking of reusing some of the hadoop examples for the same
purpose, right? I presume you have an aim at teragen/terasort and others of the
kind?
> Make TestHadoopExamples modular enough to support longevity tests.
> ------------------------------------------------------------------
>
> Key: BIGTOP-1257
> URL: https://issues.apache.org/jira/browse/BIGTOP-1257
> Project: Bigtop
> Issue Type: Improvement
> Components: Tests
> Affects Versions: 0.7.0
> Reporter: jay vyas
>
> TestHadoopExamples is really just a super of what we eventually will add in
> the Longevity suite. It will be good to create a super class, then, which
> wraps the hadoop examples jars, whic BOTH the smoke tests AND longevity tests
> can both use and customize to suite their needs.
> Advantages:
> - less code duplication
> - easier to add in new longevity tests
> - longevity tests focus on customizing , rather than defining the tests
> classes.
> We can go about this two ways:
> 1) Use the approach of TestHadoopExamples: define all examples in a k/v map,
> with parameters or
> 2) Write individual unit tests for each benchmark (i.e. TestDFSIO), as is
> done in Dasha's BIGTOP-1208 patch.
> Part of this JIRA i think is to audit the longevity suite for other
> duplications, to see where we can merge efforts.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
