pytest_pyramid
pytest_pyramid provides basic fixtures for testing pyramid applications with pytest test suite.
By default, pytest_pyramid will create two fixtures: pyramid_config, which creates configurator based on config.ini file, and pyramid_app, which creates TestApp based on Configurator returned by pyramid_config.
Command line options
–pc - pyramid configuration file based on which pytest_pyramid will create test app
Usage
For the most basic usage, pytest_pyramid provides pyramid_app and pyramid_config fixtures, that can be used to test your pyramid app. Simply pass your pyramid config *.ini file to –pc command-line option, and include pytest_app fixture into your test suite to be able to use it for integration tests.
Fixtures
pytest_pyramid provides two fixtures to be used in pytest tests:
pyramid_config - fixture providing pyramid’s Configurator instance as defined in pyramid config’s file
pyramid_app - pyramid application for testing - a webtest.app.TestApp
Both of these fixtures depend on the Config file passed in the command line.
Fixture factories
If you’re developing a module, package meant to extend functionalities of other applications, it’s not necessary to create a full-blown application to test functionalities provided in packages. To do this, pytest_pyramid provides you with fixture pytest_pyramid.factories.
There are two factories:
pytest_pyramid.factories.pyramid_config provides you with Configuration object based on either settings, config_file argument, or by –pc command-line option config file.
pytest_pyramid.factories.pyramid_app creates a webtest.app.TestApp based on Configurator class instance as returned from fixture passed by name to it. It also accepts additional fixtures that should be loaded before the pyramid_app. See the example with postgresql below.
from pytest_postgresql.plugin import postgresql
from pytest_pyramid import factories
app_config = factories.pyramid_config(config_path="development.ini")
app_with_postgres = factories.pyramid_app("app_config", "postgresql")
def test_pyramid_app(app_with_postgres):
res = app_with_postgres.get('/', status=404)
assert res.status_code == 404
TODO
provide a pyramid_proc fixture that will start pyramid app process using summon_process
Tests
To run tests run this command:
pytest –pc tests/pyramid.test.ini
Release files for pytest-pyramid 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pytest_pyramid-1.1.1.tar.gz | 6.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytest_pyramid-1.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.6 kB
Release files / pytest_pyramid-1.1.1.tar.gz
| Download URL | pytest_pyramid-1.1.1.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f24c0bcce66aacf2754fc4409560c07af7f034e07384a90f814eb61583316fe3
|
|
BLAKE2b-256 checksum How to use checksums |
85265c51be902532364267832ec215e04b52622e3bbbd0c8f4338b55de1a97c1
|
| 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 5, 2026.
Transparency logRelease files / pytest_pyramid-1.1.1-py3-none-any.whl
| Download URL | pytest_pyramid-1.1.1-py3-none-any.whl |
|---|---|
| Size | 6.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b42d958598652a1c94d7b545b6b04b1fdf4bd57cedc2f5b422c6b4cb6c65d068
|
|
BLAKE2b-256 checksum How to use checksums |
71e30536862fb97756d470ab7e3892f0a62d3ac610eebf3085ab9d054c8e6b98
|
| 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 5, 2026.
Transparency log