Test classification in OpenStack
Test categories in OpenStack can be divided into the following types:
1) unit test (small test/unit tests)
- Unit tests are stored in the code library of each component. For example, unit tests of nova are stored in the nova/tests directory.
- Unit Tests are mainly aimed at testing the source code and testing the code at the function level.
- Need data or a simulated environment? Use Mock for Simulation
- Unit test is generally only applicable to public-level functions.
2) function test (Medium Tests)
- Function tests are also stored in the code library of each component. For example, unit tests of nova are stored in the nova/tests directory.
- Compared with unit testing, functional testing is based on real dependent environments (databases, file IO systems, Hypvervisor, etc)
3) integration test (Large Tests) integration test tool-SmokeStack (UI-based integration test tool) https://wiki.openstack.org/wiki/Smokestack
Ruby-Based Integrated Testing Tool
Https://github.com/dprince/torpedo
Integrated Test Tool-Tempesthttp: // docs.openstack.org/#/tempest/
- The integration test code is stored in an independent project, such as tempest.
- The integration test should be run in a complete deployment environment, such as a complete environment where OpenStack is deployed.
- Integration Testing focuses on system functions, integrity, and integration with real hardware Environments
- Fake/mock is generally not used in the integration test code.
4) UI test (UI tests)
The Community has a project for automated testing of the Horizon interface.
Https://wiki.openstack.org/wiki/Horizon/Testing/UI
- This test tool uses selenium to perform integration tests on Horizon.
- Before running the test, you must start the OpenStack Server and ensure that Horizon runs properly.
5) the stress tests/performance tests community has a project Rally for performance testing.
Https://wiki.openstack.org/wiki/Rally
- Rally automatically deploys an OpenStack environment and runs tempest to verify the environment.
- Rally simulates the generation of user load to observe performance testing problems
- Rally collects Hypervisor and VM data through Ceilomter and stores the data in Rally's database.
- Rally will generate a performance test report
6) globalization tests https://launchpad.net/openstack-i18n
- Globalization will test whether text translation can be switched normally and the syntax is correct.
- Globalization should ensure that the text is correctly encoded and meets the reading habits of different languages (for example, Arabic is a reading habit from the right to the left)
7) upgrade test (upgrade tests) Use DevStack, upgrade test https://wiki.openstack.org/wiki/Grenade for OpenStack
Install and deploy Openstack on Ubuntu 12.10
Ubuntu 12.04 OpenStack Swift single-node deployment Manual
OpenStack cloud computing quick start tutorial
Deploying OpenStack for enterprises: what should be done and what should not be done
CentOS 6.5 x64bit quick OpenStack Installation
This article permanently updates the link address: