cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From shwetaag <>
Subject [GitHub] cloudstack pull request: Customer escalations
Date Fri, 21 Aug 2015 07:31:10 GMT
GitHub user shwetaag opened a pull request:

    Customer escalations

    Automated two test cases and modified one testcase
    First one is  to verify correct guest os mapping in vmware for CentOS 5.9 and above
            Step1 :Register an CentOS 6.3 template
            Step2 :Launch a VM
            Step3: Try to attach VMware Tools ISO
            Step4: Verify VMware tools ISO attached correctly
    Second one is 
     Verify FTP modules are loaded in VR of advance zone
            step1 : create a VR in advance zone
            step2: Verify FTP modules are there in created VR
    and modified test case for listing default ISO which was not codded correctly and hence
not giving error even after failing

You can merge this pull request into a Git repository by running:

    $ git pull customer_escalations

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #724
commit d1311b90ac0764bd137f7140572a71a7b33da10c
Author: shweta agarwal <>
Date:   2015-07-30T11:57:22Z

    test case automated for list template pagination

commit 4ff606bce8d587c91a1bef2447ac109ec23b3ebc
Author: shweta agarwal <>
Date:   2015-08-10T11:18:03Z

    additional verification added

commit f05fec9044c28db6802c9c1c593b11424cf79294
Author: shweta agarwal <>
Date:   2015-08-19T05:28:02Z

    Merge branch 'master' of into customer_escalations

commit 9dacbd615276fbc33d6d37a5fe6c2a181a49ce2a
Author: shweta agarwal <>
Date:   2015-08-21T07:19:13Z

    added 3 test case 39918 38555 22659


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message