You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2017/03/18 22:52:42 UTC

[jira] [Commented] (BIGTOP-1410) improve and further migrate to new testing framework

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

Konstantin Boudnik commented on BIGTOP-1410:
--------------------------------------------

[~jayunit100] do you think this is still an issue? We have moved a significant part of the old tests into new smoke framework. Perhaps, this ticket needs to be a Story or something to keep track over all other related tickets? Thoughts? 

> improve and further migrate to new testing framework
> ----------------------------------------------------
>
>                 Key: BIGTOP-1410
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1410
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: build, tests
>    Affects Versions: 0.8.0
>            Reporter: jay vyas
>             Fix For: 1.3.0
>
>
> Now that BIGTOP-1222 is finally in, we should iterate again on it.
> - Lets move the simple smoke tests (like hadoopExamples) into bigtop-1222 exclusively.
> - Lets also add better parameterizations for stuff like groovy , and a good way for users to update them (not just updating the parameters in build.gradle)
> - Finally, lets also integrate it to run from top level directory.  Right now you have to run from inside bigtop-tests/smoke-tests
> [~cos] can provide some more details on how we'd like to see it evolve.  My preference is towards maintaining scripts in the smoke-tests directories whereever possible and starting to thin out the deeply nested maven stuff, except where maven is absolutely essential (i.e. jar packaging).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)