Upstream software project

pytest-bdd

BDD for pytest

About pytest-bdd

BDD for pytest

This project links 5 native package records across 4 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

pytest-bdd repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; openSUSE Leap 15.6: 1 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.pytest-bdd: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsopenSUSE Leap 15.61 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
pytest-bdd
Publisher
Not authoritatively mapped
Native package records
5
Operating systems
debian-12, debian-13, opensuse-leap-15-6, opensuse-tumbleweed
License expression
MIT
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

BDD library for the py.test runner pytest-bdd implements a subset of Gherkin language for the automation of the project requirements testing and easier behavioral driven development. Unlike many other BDD tools it doesn't require a separate runner and benefits from the power and flexibility of the pytest. It allows to unify your unit and functional tests, easier continuous integration server configuration and maximal reuse of the tests setup. Pytest fixtures written for the unit tests can be reused for the setup and actions mentioned in the feature steps with dependency injection, which allows a true BDD just-enough specification of the requirements without maintaining any context object containing the side effects of the Gherkin imperative declarations.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. Package python3-pytest-bdd

    bookworm (Debian 12 (Bookworm)) (python): BDD plugin for py.test

    5.0.0-1: all

    Source: pytest-bdd

Debian 13 (Trixie)

  1. Package python3-pytest-bdd

    trixie (Debian 13 (Trixie)) (python): BDD plugin for py.test

    7.1.2-2: all

    Source: pytest-bdd

openSUSE Leap 15.6

  1. Package python3-pytest-bdd

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): BDD for pytest

    3.3.0-bp156.3.2: noarch

    Source: python-pytest-bdd

openSUSE Tumbleweed

  1. Package python313-pytest-bdd

    tumbleweed (openSUSE Tumbleweed) (Unspecified): BDD for pytest

    8.1.0-2.4: noarch

    Source: python-pytest-bdd

  2. Package python314-pytest-bdd

    tumbleweed (openSUSE Tumbleweed) (Unspecified): BDD for pytest

    8.1.0-2.4: noarch

    Source: python-pytest-bdd

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.