VWS Mock
Mock for the Vuforia Web Services (VWS) API, the Vuforia Web Query API, and the Model Target Web API.
Mocking calls made to Vuforia
MockVWS intercepts requests made with requests, httpx or HTTPX2.
pip install vws-python-mockThis requires Python 3.14+.
"""Make a request to the Vuforia Web Services API mock."""
import requests
from mock_vws import MockVWS
from mock_vws.database import CloudDatabase
with MockVWS() as mock:
database = CloudDatabase()
mock.add_cloud_database(cloud_database=database)
# This will use the Vuforia mock.
_ = requests.get(url="https://vws.vuforia.com/summary", timeout=30)MockVWS also intercepts httpx requests:
"""Make a request to the Vuforia Web Services API mock using httpx."""
import httpx
from mock_vws import MockVWS
from mock_vws.database import CloudDatabase
with MockVWS() as mock:
database = CloudDatabase()
mock.add_cloud_database(cloud_database=database)
# This will use the Vuforia mock.
_ = httpx.get(url="https://vws.vuforia.com/summary", timeout=30)MockVWS also intercepts HTTPX2 requests, with no need for httpx2.alias_httpx():
"""Make a request to the Vuforia Web Services API mock using httpx2."""
import httpx2
from mock_vws import MockVWS
from mock_vws.database import CloudDatabase
with MockVWS() as mock:
database = CloudDatabase()
mock.add_cloud_database(cloud_database=database)
# This will use the Vuforia mock.
_ = httpx2.get(url="https://vws.vuforia.com/summary", timeout=30)Asynchronous httpx and HTTPX2 clients are intercepted as well.
By default, an exception will be raised if any requests to unmocked addresses are made.
Using Docker to mock calls to Vuforia from any language
It is possible run a Mock VWS instance using Docker containers.
This allows you to run tests against a mock VWS instance regardless of the language or tooling you are using.
See the the instructions for how to do this.
Full documentation
See the full documentation. This includes details on how to use the mock, options, and details of the differences between the mock and the real Vuforia Web Services.
1 maintainer
Metadata
1 maintainer
Release files for vws-python-mock 2026.9.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| vws_python_mock-2026.9.8.tar.gz | 400.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vws_python_mock-2026.9.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 522.1 kB
Release files / vws_python_mock-2026.9.8.tar.gz
| Download URL | vws_python_mock-2026.9.8.tar.gz |
|---|---|
| Size | 400.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fd87e20367da048d0fe849ef16e3a48149a59101e60dd9d51be51771a3a6ddc7
|
|
BLAKE2b-256 checksum How to use checksums |
e6226de53bbb2d0c8744f5a731789110c95c69e24d8a98b0649d8c591df59034
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logRelease files / vws_python_mock-2026.9.8-py3-none-any.whl
| Download URL | vws_python_mock-2026.9.8-py3-none-any.whl |
|---|---|
| Size | 121.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0f1f50361522560a4fe81fcbef55475b1e23a401818df8f686f7bd6da0955647
|
|
BLAKE2b-256 checksum How to use checksums |
8ea04dc3585b3994bf76a6fe1e7757d85fcd02f0eae12a926827367982ee6047
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency log
