Student Project GuideThis document which provides Openstack cloud computing complete documentation report of testing. You can download same testing report. A primary purpose of testing is to detect software failures so that defects may be discovered and corrected. Testing is a process used to help identify the correctness, completeness and quality of developed computer software.
Test cases:
Unit test cases for automated installation of OpenStack:
| Sl. No. | Test Case | Expected Outcome | Observed outcome | Status |
| 1 | Check the version of any OpenStack component.
$ keystone-manage –version
If it returns 2013.2.x then it means OpenStack Havana version is installed, 2014.1.x means IceHouse version, 2014.2.x means Stable Juno version is installed. |
Should give the version of keystone. | Gives the Keystone version,
2014.2.0
|
Pass |
Unit test cases for Keystone extension:
| Sl. No. | Test Case | Expected Outcome | Observed outcome | Status |
| 1 | Test for create, list, delete, assign etc operations on roles.
$ testr run tempest.api.identity.aadmin.test_roles |
Should give a success message saying all the operations are working fine for roles. | All operations on roles..ok
Errors=0 |
Pass |
| 2 | Test for create, update etc operations on tenants.
$ testr run tempest.api.identity.admin.test_tenants
|
Should give a success message saying all the operations are working fine for tenants. | All operations on tenants..ok
Errors=0 |
Pass |
| 3 | Test for create, delete etc operations on Tokens.
$ testr run tempest.api.identity.admin.test_tokens |
Should give a success message saying all the operations are working fine for tokens. | All operations on tokens..ok
Errors=0 |
Pass |
| 4 | Test for create, update, delete etc operations on users
$ testr run tempest.api.identity.admin.test_users |
Should give a success message saying all the operations are working fine for users. | All operations on users..ok
Errors=0 |
Pass |
| 5 | Test for extension developed to list the users of particular project
$ testr run Tempest.api.identity.admin.v3.test_users_project |
Should give a success message saying the extension developed works fine. | Users_project extension..ok
Errors=0 |
Pass |
Unit test cases for Logstash functionalities:
| Sl. No. | Test Case | Expected Outcome | Observed outcome | Status |
| 1 | Test for logs clean up
$ java –jar logstash.jar find . –type f –ctime +60 |
Should give empty result | Did not list any file name, ie Empty | Pass |
| 2 | Test for Clearing RAM
$ java –jar logstash.jar free -m |
Used memory should be zero | Used memory is zero | Pass |
| 3 | Test for Archiving log files
$ java –jar logstash.jar find . –type –name “*.log” |
Should give empty result | Did not list any file name, ie Empty | Pass |
| 4 | Logstash upgradation
$ java –jar logstash.jar sudo service logstash-server –version |
Should give latest version of logstash | Returned latest version of logstash | Pass |
Integration Testing For Automated OpenStack Installation
| Sl. No. | Test Case | Expected
Outcome |
Observed
Outcome |
Status
|
| 1 | Test to check whether all the components are installed
$ cd /home/openstack/devstack $ ./rejoin-stack.sh
|
Should show all the components and processes in different screens | Showed the components and processes of OpenStack in different screens | Pass |
Integration Testing For Keystone extension
| Sl. No. | Test Case | Expected
Outcome |
Observed
Outcome |
Status
|
| 1 | Test for all the extensions of Keystone component
$ testr run tempest_report.tempest_addons:KeystoneExtensionTest
|
Should give a success message saying all the extensions are working file | List of extensions..ok
Errors=0 |
Pass |
| 2 | Test to check added extension caused any defects in Keystone, ie to test entire Keystone
$ cd /opt/stack/keystone $ ./run_tests.sh |
Should give a success message saying there is no error | Ran 122 tests..ok
Errors=0 |
Pass |
Integration Testing For Logstash functionalities
| Sl. No. | Test Case | Expected
Outcome |
Observed
Outcome |
Status
|
| 1 | Test for the file to which the functionality is added
$ java –jar logstash.jar agent filename.rb
|
Should give a success message saying there are no errors | Finished in 0.13 sec
Errors=0 |
Pass |
| 2 | Test for entire Logstash to check defects
$ java –jar logstash.jar rspec |
Should give a success message saying there are no errors
|
Finished in 0.13 sec
Errors=0 |
Pass |
Download source code:
Download project report:
- Download Project synopsis
- Download project SRS
- Download system design
- Download implementation
- Download testing document
