mirror of
https://github.com/apache/cloudstack.git
synced 2025-10-26 08:42:29 +01:00
uniting the READMEs
Many READMEs spread over the integration and marvin test related information can now be found in the single top-level directory
This commit is contained in:
Prasanna Santhanam
parent
d1e260032f
commit
780468659f
@ -6,3 +6,69 @@ details about your cloudstack deployment. For more help on how to write the
|
|||||||
config file and run tests check the tutorial at :
|
config file and run tests check the tutorial at :
|
||||||
|
|
||||||
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Testing+with+Python
|
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Testing+with+Python
|
||||||
|
|
||||||
|
==========================
|
||||||
|
Build Verification Testing (BVT) Cases
|
||||||
|
--------------------------------------
|
||||||
|
These test cases are the core functionality tests that ensure the application is stable and can be tested thoroughly.
|
||||||
|
These BVT cases definitions are located at : https://docs.google.com/a/cloud.com/spreadsheet/ccc?key=0Ak8acbfxQG8ndEppOGZSLV9mUF9idjVkTkZkajhTZkE&invite=CPij0K0L
|
||||||
|
|
||||||
|
Guidelines
|
||||||
|
----------
|
||||||
|
BVT test cases are being developed using Python's unittests2. Following are certain guidelines being followed
|
||||||
|
1. Tests exercised for the same resource should ideally be present under a single suite or file.
|
||||||
|
|
||||||
|
2. Time-consuming operations that create new cloud resources like server creation, volume creation etc
|
||||||
|
should not necessarily be exercised per unit test. The resources can be shared by creating them at
|
||||||
|
the class-level using setUpClass and shared across all instances during a single run.
|
||||||
|
|
||||||
|
3. Certain tests pertaining to NAT, Firewall and Load Balancing warrant fresh resources per test. Hence a call should be
|
||||||
|
taken by the stakeholders regarding sharing resources.
|
||||||
|
|
||||||
|
4. Ensure that the tearDown/tearDownClass functions clean up all the resources created during the test run.
|
||||||
|
|
||||||
|
For more information about unittests: http://docs.python.org/library/unittest.html
|
||||||
|
|
||||||
|
BVT Tests
|
||||||
|
----------
|
||||||
|
The following files contain these BVT cases:
|
||||||
|
|
||||||
|
1. test_vm_life_cycle.py - VM Life Cycle tests
|
||||||
|
2. test_volumes.py - Volumes related tests
|
||||||
|
3. test_snapshots.py - Snapshots related tests
|
||||||
|
4. test_disk_offerings.py - Disk Offerings related tests
|
||||||
|
5. test_service_offerings.py - Service Offerings related tests
|
||||||
|
6. test_hosts.py - Hosts and Clusters related tests
|
||||||
|
7. test_iso.py - ISO related tests
|
||||||
|
8. test_network.py - Network related tests
|
||||||
|
9. test_primary_storage.py - Primary storage related tests
|
||||||
|
10. test_secondary_storage.py - Secondary storage related tests
|
||||||
|
11. test_ssvm.py - SSVM & CPVM related tests
|
||||||
|
12. test_templates.py - Templates related tests
|
||||||
|
13. test_routers.py - Router related tests
|
||||||
|
|
||||||
|
==========================
|
||||||
|
|
||||||
|
P1 Cases
|
||||||
|
--------------------------------------
|
||||||
|
These test cases are the core functionality tests that ensure the application is stable and can be tested thoroughly.
|
||||||
|
These P1 cases definitions are located at : https://docs.google.com/a/clogeny.com/spreadsheet/ccc?key=0Aq5M2ldK6eyedDJBa0EzM0RPNmdVNVZOWnFnOVJJcHc&hl=en_US
|
||||||
|
|
||||||
|
P1 Tests
|
||||||
|
----------
|
||||||
|
The following files contain these P1 cases:
|
||||||
|
|
||||||
|
1. test_snapshots.py - Snapshots related tests
|
||||||
|
2. test_routers.py - Router related tests
|
||||||
|
3. test_usage.py - Usage realted tests
|
||||||
|
4. test_account.py - Account related tests
|
||||||
|
5. test_resource_limits.py - Resource limits tests
|
||||||
|
6. test_security_groups.py - Security groups related tests
|
||||||
|
7. test_templates.py - templates related tests
|
||||||
|
8. test_volumes.py - Volumes related tests
|
||||||
|
9. test_blocker_bugs.py - Blocker bugs tests
|
||||||
|
10. test_project_configs.py - Project global configuration related tests
|
||||||
|
11. test_project_limits.py - Project resource limits related tests
|
||||||
|
12. test_project_resources.py - Project resource creation related tests
|
||||||
|
13. test_project_usage.py - Project usage related tests
|
||||||
|
14. test_projects - Projects functionality tests
|
||||||
|
|||||||
@ -1,41 +0,0 @@
|
|||||||
P1 Cases
|
|
||||||
--------------------------------------
|
|
||||||
These test cases are the core functionality tests that ensure the application is stable and can be tested thoroughly.
|
|
||||||
These P1 cases definitions are located at : https://docs.google.com/a/clogeny.com/spreadsheet/ccc?key=0Aq5M2ldK6eyedDJBa0EzM0RPNmdVNVZOWnFnOVJJcHc&hl=en_US
|
|
||||||
|
|
||||||
|
|
||||||
Guidelines
|
|
||||||
----------
|
|
||||||
P1 test cases are being developed using Python's unittests2. Following are certain guidelines being followed
|
|
||||||
1. Tests exercised for the same resource should ideally be present under a single suite or file.
|
|
||||||
|
|
||||||
2. Time-consuming operations that create new cloud resources like server creation, volume creation etc
|
|
||||||
should not necessarily be exercised per unit test. The resources can be shared by creating them at
|
|
||||||
the class-level using setUpClass and shared across all instances during a single run.
|
|
||||||
|
|
||||||
3. Certain tests pertaining to NAT, Firewall and Load Balancing warrant fresh resources per test. Hence a call should be
|
|
||||||
taken by the stakeholders regarding sharing resources.
|
|
||||||
|
|
||||||
4. Ensure that the tearDown/tearDownClass functions clean up all the resources created during the test run.
|
|
||||||
|
|
||||||
For more information about unittests: http://docs.python.org/library/unittest.html
|
|
||||||
|
|
||||||
|
|
||||||
P1 Tests
|
|
||||||
----------
|
|
||||||
The following files contain these P1 cases:
|
|
||||||
|
|
||||||
1. test_snapshots.py - Snapshots related tests
|
|
||||||
2. test_routers.py - Router related tests
|
|
||||||
3. test_usage.py - Usage realted tests
|
|
||||||
4. test_account.py - Account related tests
|
|
||||||
5. test_resource_limits.py - Resource limits tests
|
|
||||||
6. test_security_groups.py - Security groups related tests
|
|
||||||
7. test_templates.py - templates related tests
|
|
||||||
8. test_volumes.py - Volumes related tests
|
|
||||||
9. test_blocker_bugs.py - Blocker bugs tests
|
|
||||||
10. test_project_configs.py - Project global configuration related tests
|
|
||||||
11. test_project_limits.py - Project resource limits related tests
|
|
||||||
12. test_project_resources.py - Project resource creation related tests
|
|
||||||
13. test_project_usage.py - Project usage related tests
|
|
||||||
14. test_projects - Projects functionality tests
|
|
||||||
@ -1,41 +0,0 @@
|
|||||||
Build Verification Testing (BVT) Cases
|
|
||||||
--------------------------------------
|
|
||||||
These test cases are the core functionality tests that ensure the application is stable and can be tested thoroughly.
|
|
||||||
These BVT cases definitions are located at : https://docs.google.com/a/cloud.com/spreadsheet/ccc?key=0Ak8acbfxQG8ndEppOGZSLV9mUF9idjVkTkZkajhTZkE&invite=CPij0K0L
|
|
||||||
|
|
||||||
|
|
||||||
Guidelines
|
|
||||||
----------
|
|
||||||
BVT test cases are being developed using Python's unittests2. Following are certain guidelines being followed
|
|
||||||
1. Tests exercised for the same resource should ideally be present under a single suite or file.
|
|
||||||
|
|
||||||
2. Time-consuming operations that create new cloud resources like server creation, volume creation etc
|
|
||||||
should not necessarily be exercised per unit test. The resources can be shared by creating them at
|
|
||||||
the class-level using setUpClass and shared across all instances during a single run.
|
|
||||||
|
|
||||||
3. Certain tests pertaining to NAT, Firewall and Load Balancing warrant fresh resources per test. Hence a call should be
|
|
||||||
taken by the stakeholders regarding sharing resources.
|
|
||||||
|
|
||||||
4. Ensure that the tearDown/tearDownClass functions clean up all the resources created during the test run.
|
|
||||||
|
|
||||||
For more information about unittests: http://docs.python.org/library/unittest.html
|
|
||||||
|
|
||||||
|
|
||||||
BVT Tests
|
|
||||||
----------
|
|
||||||
The following files contain these BVT cases:
|
|
||||||
|
|
||||||
1. test_vm_life_cycle.py - VM Life Cycle tests
|
|
||||||
2. test_volumes.py - Volumes related tests
|
|
||||||
3. test_snapshots.py - Snapshots related tests
|
|
||||||
4. test_disk_offerings.py - Disk Offerings related tests
|
|
||||||
5. test_service_offerings.py - Service Offerings related tests
|
|
||||||
6. test_hosts.py - Hosts and Clusters related tests
|
|
||||||
7. test_iso.py - ISO related tests
|
|
||||||
8. test_network.py - Network related tests
|
|
||||||
9. test_primary_storage.py - Primary storage related tests
|
|
||||||
10. test_secondary_storage.py - Secondary storage related tests
|
|
||||||
11. test_ssvm.py - SSVM & CPVM related tests
|
|
||||||
12. test_templates.py - Templates related tests
|
|
||||||
13. test_routers.py - Router related tests
|
|
||||||
|
|
||||||
@ -12,7 +12,18 @@ unittests and functional tests with Marvin makes testing with cloudstack easier
|
|||||||
3. remote ssh login/execute command
|
3. remote ssh login/execute command
|
||||||
4. mysql query
|
4. mysql query
|
||||||
|
|
||||||
3. sample code is under sandbox
|
3. sample code is under sandbox. To generate the config for a deployment.
|
||||||
|
|
||||||
|
Alter the .properties file in the sandbox. For example the
|
||||||
|
simualtordemo.properties after modification can generate the config file as
|
||||||
|
shown below
|
||||||
|
|
||||||
|
$ python simulator_setup.py -i simulatordemo.properties -o simulatordemo.cfg
|
||||||
|
|
||||||
|
To deploy the environment and run the tests
|
||||||
|
|
||||||
|
$ python -m marvin.deployAndRun -c simulatordemo.cfg -t /tmp/t.log -r /tmp/r.log -d testcase
|
||||||
|
|
||||||
4. WIKI page
|
4. WIKI page
|
||||||
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Testing+with+Python
|
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Testing+with+Python
|
||||||
|
|
||||||
|
|||||||
@ -1,8 +0,0 @@
|
|||||||
|
|
||||||
Download Marvin source from hudson
|
|
||||||
|
|
||||||
Install Marvin:
|
|
||||||
pip install Marvin-0.1.0.tar.gz
|
|
||||||
|
|
||||||
To Run the test:
|
|
||||||
python -m marvin.deployAndRun -c demo.cfg -t /tmp/t.log -r /tmp/r.log -f testSshDeployVM.py -l
|
|
||||||
@ -1,12 +0,0 @@
|
|||||||
To generate the config
|
|
||||||
Alter the .properties file to point to your simulator installed environment
|
|
||||||
|
|
||||||
python simulator_setup.py -i simulatordemo.properties -o simulatordemo.cfg
|
|
||||||
|
|
||||||
|
|
||||||
To deploy the environment and run the tests
|
|
||||||
|
|
||||||
python -m marvin.deployAndRun -c simulatordemo.cfg -t /tmp/t.log -r /tmp/r.log -d testcase
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Loading…
x
Reference in New Issue
Block a user