You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org> on 2011/10/31 23:13:32 UTC

[jira] [Updated] (BIGTOP-197) Package testing artifact needs to be refactored

     [ https://issues.apache.org/jira/browse/BIGTOP-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik updated BIGTOP-197:
------------------------------------

    Attachment: BIGTOP-197.patch.txt
    
> Package testing artifact needs to be refactored
> -----------------------------------------------
>
>                 Key: BIGTOP-197
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-197
>             Project: Bigtop
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 0.1.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.2.0
>
>         Attachments: BIGTOP-197.patch.txt
>
>
> No, this is not the ultimate refactoring ;-) For now I'm simply looking to make the tests easier to understand/more robust. Here's roughly what needs to be done:
>    1. Streamline the class hierarchy of entry points into TestPackagesBasics.groovy, TestPackagesPseudoDistributed.groovy, TestPackagesPseudoDistributedWithRM.groovy
>        with each next one adding some extra level of testing (and scrutiny and runtime). The difference between TestPackagesPseudoDistributed.groovy and
>        TestPackagesPseudoDistributedWithRM.groovy is that the later adds an extra step of actually trying to remove the package.
>    2. Add a state creation/verification class for Hive
>    3. Implement various hacks and workaround in order to survive our daemon scripts misbehaving (increase timeouts, implement explicit kill -9, etc).
>    4. Start generating a consumable XML output for content of the packages
>    5. Implement curl timeouts for HUE
>      

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira