Mox3 - Mock object framework for Python 3
Mox3 is an unofficial port of the Google mox framework (http://code.google.com/p/pymox/) to Python 3. It was meant to be as compatible with mox as possible, but small enhancements have been made. The library was tested on Python version 3.2, 2.7 and 2.6.
Use at your own risk ;)
To install:
$ python setup.py install
Running Tests
The testing system is based on a combination of tox and testr. The canonical approach to running tests is to simply run the command tox. This will create virtual environments, populate them with depenedencies and run all of the tests that OpenStack CI systems run. Behind the scenes, tox is running testr run –parallel, but is set up such that you can supply any additional testr arguments that are needed to tox. For example, you can run: tox – –analyze-isolation to cause tox to tell testr to add –analyze-isolation to its argument list.
It is also possible to run the tests inside of a virtual environment you have created, or it is possible that you have all of the dependencies installed locally already. In this case, you can interact with the testr command directly. Running testr run will run the entire test suite. testr run –parallel will run it in parallel (this is the default incantation tox uses.) More information about testr can be found at: http://wiki.openstack.org/testr
Basic Usage
The basic usage of mox3 is the same as with mox, but the initial import should be made from the mox3 module:
from mox3 import mox
To learn how to use mox3 you may check the documentation of the original mox framework:
Original Copyright
Mox is Copyright 2008 Google Inc, and licensed under the Apache License, Version 2.0; see the file COPYING.txt for details. If you would like to help us improve Mox, join the group.
OpenStack Fork
Free software: Apache license
Documentation: https://docs.openstack.org/mox3/latest/
1 maintainer
Metadata
1 maintainer
Release files for mox3 0.25.0
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 |
|---|---|---|---|---|
| mox3-0.25.0.tar.gz | 44.4 kB | Without provenance | Details for mox3-0.25.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mox3-0.25.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for mox3-0.25.0-py2.py3-none-any.whl |
Total release size: 85.1 kB
Release files / mox3-0.25.0.tar.gz
| Download URL | mox3-0.25.0.tar.gz |
|---|---|
| Size | 44.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b7476f7a2dfe4d7ad743e3cbbf04ade624b3a208a0042f3f8b2ae7b00559543a
|
|
BLAKE2b-256 checksum How to use checksums |
459438860d7e32553924362507c3e4754659edaffaa34baa144fc193f3653d4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / mox3-0.25.0-py2.py3-none-any.whl
| Download URL | mox3-0.25.0-py2.py3-none-any.whl |
|---|---|
| Size | 40.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
987361a19315cb3899c59b21c4f85cb59b207779ff02fe41ff240947e285f493
|
|
BLAKE2b-256 checksum How to use checksums |
89772a003fdbaa01994469228fa6d8331f5cfb9226c67ba91aa59cf6d4f5badd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for mox3 0.25.0
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.
