[jira] [Commented] (BIGTOP-1195) Higher level interface to smokes.

["Mikhail Antonov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BIGTOP-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888859#comment-13888859 ] 

Mikhail Antonov commented on BIGTOP-1195:
-----------------------------------------

A question/thought. What about separation between

 - smoke tests as "validating the binaries built from the source code downloaded from apache.org", e.g. that the code is not broken 
 and
 - smoke tests to validate that a particular *deployment* is of packages, deployed thru Puppet, is not broken?

and also separation between binaries built as jar files vs. rpms?

For latter case we obviously need to have access to some provisioning API, to run more or less complex tests, for example for HA, for former we need probably to simplify test setup as much as possible, including testing all what's possible on local machine, 

> Higher level interface to smokes.
> ---------------------------------
>
>                 Key: BIGTOP-1195
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1195
>             Project: Bigtop
>          Issue Type: Improvement
>            Reporter: jay vyas
>         Attachments: BIGTOP-1195.1.very-raw.patch
>
>
> Running all the smokes with mvn verify is painful:
> 1) Diving into the XML files when stuff breaks
> 2) Remembering to use TRACE level logging 
> 3) Leaving out export PIG_HOME , etc... leads to smokes failing late in the test run. 
> 4) Hopefully we can specify more env variables to control size of smokes in the future.  That will make a script for running the whole thing even more useful. 
> 5) when hacking the groovy scripts:: To Compile or not to compile?  Always forget to specify. 
> A simple bash script could serve as a better tutorial/solution/template for users that want to run smokes.  I'm attaching a very raw patch that we can rewrite in python and flesh out some more to do better error reporting, more verification, etc. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)