pytest mit Homebrew, apt, dnf installieren

Projektlinks

• Homepage
• Paketmanager-Seite

Befehle und Aliase

• py.test
• pytest

Projektgeschichte

pytest traces its roots to testing experiments around PyPy and Holger Krekel’s complementary-standard-library work in 2004. The std.utest component became py.test when the std project was renamed py around September or October 2004.

The 2009 py 1.0 release introduced foundational funcargs/fixtures and a plugin architecture. In November 2010, pytest 2.0 became a package separate from py, although the command was still named py.test. Pytest 3.0 in August 2016 established pytest as the recommended command-line entry point.

Adoptionsgeschichte

pytest grew from the PyPy and py-library communities into a general-purpose Python test framework. Its fixture and plugin architecture enabled an extensive surrounding ecosystem, while compatibility with unittest-style tests eased adoption in existing Python projects. Distribution through PyPI and operating-system package managers made it common in development environments and CI systems.

Wie es verwendet wird

Developers write test functions using ordinary Python assertions, request reusable fixtures through function arguments, and run discovery with the pytest command. Plugins extend collection, reporting, coverage, parallelization, frameworks, and other behavior. Pytest can also execute unittest-based test suites.

Warum Paket-Nerds sich dafür interessieren

pytest is a package-ecosystem landmark: it popularized plain assert statements with rich failure introspection, composable fixtures, automatic test discovery, and a broad plugin model. Its long migration from the py library to an independent pytest package also explains legacy names such as py.test and historical dependencies encountered in older environments.

Zeitleiste

• 2004: std.utest became py.test as the std project was renamed py.
• 2009: py 1.0 introduced foundational fixtures and the enduring plugin architecture.
• 2010: pytest 2.0 was released separately from the py package.
• 2016: pytest 3.0 made pytest the recommended command name.
• 2020: pytest 6.0 added pyproject.toml configuration support.
• 2025: pytest 9.0 added pytest.toml and native TOML configuration.

Related projects

• The py library originally housed py.test before pytest became a separate distribution.
• PyPy community testing work helped shape pytest’s origins.
• tox commonly invokes pytest across managed Python environments and can also host pytest configuration.
• pluggy underpins pytest’s plugin and hook system.

Quellen

• Official configuration reference: https://docs.pytest.org/en/stable/reference/customize.html
• Official history: https://docs.pytest.org/en/stable/history.html
• Official unittest compatibility guide: https://docs.pytest.org/en/stable/unittest.html
• source_facts.package-manager