[
https://issues.apache.org/jira/browse/BIGTOP-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121938#comment-14121938
]
jay vyas edited comment on BIGTOP-1388 at 9/4/14 8:28 PM:
----------------------------------------------------------
Thanks for adding this patch [~dawson.choong] ..possibly, adding your classes
into the new {{bigtop-tests/smoke-tests/}} framework, leveraging the gradle
smoke utilities could make for an easier to maintain system as well. since its
one folder per test, you can easily put a stress.properties into a folder
dedicated to your specific tests, that any user can easily configure.
See the {{smoke-tests/flume/}} for an example of that... (this just a
thought/suggestion)
was (Author: jayunit100):
Thanks for adding this patch [~dawson.choong] ..possibly, adding your classes
into the new {{bigtop-tests/smoke-tests/}} framework, leveraging the gradle
smoke utilities could make for an easier to maintain system as well. since its
one folder per test, you can easily put a stress.properties into a folder
dedicated to your specific tests, that any user can easily configure.
See the {{smoke-tests/flume/}} for an example of that.
> Use cluster failure tests during other tests with command line parametrization
> ------------------------------------------------------------------------------
>
> Key: BIGTOP-1388
> URL: https://issues.apache.org/jira/browse/BIGTOP-1388
> Project: Bigtop
> Issue Type: Improvement
> Components: tests
> Affects Versions: 0.7.0
> Reporter: Dawson Choong
> Labels: patch
> Fix For: 0.8.0
>
> Attachments: BIGTOP-1388.patch
>
>
> User can run a series of cluster failures such as killing/restarting a
> service and shutting down the network during a mapr or longevity test. The
> goal is to test that the tests complete during the failures. The failures
> should be able to be specified as a command line parameter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
