OpenStack-In-A-Box
Stack-In-A-Box-based OpenStack Services for use with Testing Framesworks
Overview
Stack-In-A-Box provides the ability to use mocked RESTful APIs naturally inside unit tests by using modules such as HTTPretty or Requests-Mock. OpenStack-In-A-Box provides a series of mocked OpenStack Services inside the Stack-In-A-Box framework, thus providing a reliable mock-up of the OpenStack Services that can be utilized by applications written against them.
Installing
Installation is simple:
pip install openstackinabox
Goals
Enable Python modules to be unit tested against OpenStack services in an environment controlled by the unit tests.
Provide reliable, accurate mock-ups of the services
Enable unit testing to not have to mock the various tools, e.g KeystoneClient API, to perform their tests.
Support both Positive and Negative testing
Testing should be easy to do:
you should not necessarily need to know the ins and outs of each service
you should be able to register what you need (f.e authenticaiton, storage) and have it just work
should be usable on systems like Travis (https://travis-ci.org/)
should be light on requirements
we do not want to bloat your testing to fit our needs
if we have many requirements they could interfere with your requirements
The code being unit-tested should not be able to tell the difference of whether it is working with OpenStack-In-A-Box or the real thing
there should be nothing special about setting up the test
if you don’t turn on OpenStack-In-A-Box (and Stack-In-A-Box upon which it is built) then the code should be able to call the real thing
caveat: the utility tools (f.e httpretty, requests-mock) will determine the URL for the services being provided; see Stack-In-A-Box for details.
Why not use framekwork X?
This is a natural extension of Stack-In-A-Box to provide OpenStack services to the unit testing being done. If you are using Stack-In-A-Box then it makes sense to also use OpenStack-In-A-Box as it is simply providing a compatible set of OpenStack services that simply need to be registered with Stack-In-A-Box.
What’s Provided?
Current work is on supporting the OpenStack Keystone v2 services. See the Issues and Milestone for more details.
Working with Frameworks
OpenStack-In-A-Box builds on Stack-In-A-Box. Simply instantiate the desired service and register it with Stack-In-A-Box.
References
Stack-In-A-Box - https://github.com/TestInABox/stackInABox/
OpenStack - https://www.openstack.org/
OpenStack Keystone - http://docs.openstack.org/developer/keystone/
Metadata
Release files for openstackinabox 0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| openstackinabox-0.2.tar.gz | 61.7 kB | Without provenance | Details for openstackinabox-0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| openstackinabox-0.2-py3-none-any.whl | Python 3 | none | any | Details for openstackinabox-0.2-py3-none-any.whl |
Total release size: 161.3 kB
Release files / openstackinabox-0.2.tar.gz
| Download URL | openstackinabox-0.2.tar.gz |
|---|---|
| Size | 61.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b49b81b195650fdbe65a45cfc5503ac1afa647c0208647adaab3a0fa8788693b
|
|
BLAKE2b-256 checksum How to use checksums |
b227dc73e70b8707cb9f0d430dcf08b4f225aceb26859465a0a8833caa6474e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / openstackinabox-0.2-py3-none-any.whl
| Download URL | openstackinabox-0.2-py3-none-any.whl |
|---|---|
| Size | 99.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
175b789824d5ee1eb3a689289510741fbe00cde51afc1b24aa527eca7e95cd6c
|
|
BLAKE2b-256 checksum How to use checksums |
b8736127b56242c24b15db8cdfee8f5b61f4f26bf6b0a41190e862f5a395a91e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for openstackinabox 0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.