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

jay vyas edited comment on BIGTOP-1222 at 3/25/14 5:37 PM:
-----------------------------------------------------------

great point:  Smoke functional tests don't need maven to run ! w00t.  

So [~cos] : Shall we have the codebase reflect this by creating 
smokes/functional tests, which are non maven, raw groovy scripts, splitting the 
smokes like this:

1) smokes/integration  (direct API calling tests, like what happens in 
test-artifacts/..../hbase/smoke/TestImportTsv.groovy)  (this can stay the exact 
same , use maven, and keep directory structure)

2) smokes/functional (iTest based tests which don't make direct API calls,  For 
example TestMahoutExamples.groovy and TestHadoopExamples.groovy) (this can be a 
new folder or subproject in bigtop?)

The target of this JIRA could be the LAtter. Hows that sound?  if you agree we 
can come up with a plan for how this can be done 


was (Author: jayunit100):
great point:  Smoke functional tests don't need maven to run ! w00t.  

So [~cos] 

1) smokes/integration  (direct API calling tests, like what happens in 
test-artifacts/..../hbase/smoke/TestImportTsv.groovy) 

2) smokes/functional (iTest based tests which don't make direct API calls,  For 
example TestMahoutExamples.groovy and TestHadoopExamples.groovy)

The target of this JIRA could be the LAtter. Hows that sound?  IF you agree ill 
sketch up a plan for it

> Completely gradleize the bigtop smokes
> --------------------------------------
>
>                 Key: BIGTOP-1222
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1222
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 0.7.0
>            Reporter: jay vyas
>
> Currently, there is a JIRA underway to make running the maven based smoke 
> tests easier:  BIGTOP-1195.  
> Eventually, however, maybe we could run these smokes from gradle.    I think 
> that will obviate BIGTOP-1195 (Although i still assert a bash driver is a big 
> win/gain for bigtop's goals : which are to unify the hadoop packaging and 
> deployment paradigm).
> - run the smokes using a simple gradle goal
> - smokes should be easily runnable as scripts, with no need for jar file 
> intermediates.
> - The bash driver for BIGTOP-1195 (if accepted, still under debate) should be 
> upgraded to use the new gradle smokes
> - Delete old maven smokes. 
> This might be a little ambitious, if so others chime in.  I'm not a 
> gradle/groovy expert but getting more well versed.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to