Upstream software project

python-stestr

A parallel Python test runner built around subunit

About python-stestr

A parallel Python test runner built around subunit

This project links 7 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

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

Project identity

Project
python-stestr
Publisher
Not authoritatively mapped
Native package records
7
Operating systems
debian-12, debian-13, opensuse-leap-15-6, opensuse-tumbleweed
License expression
Apache-2.0
Source repository
Open source repository

Source-reported description

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

stestr is parallel Python test runner designed to execute unittest test suites using multiple processes to split up execution of a test suite. It also will store a history of all test runs to help in debugging failures and optimizing the scheduler to improve speed. To accomplish this goal it uses the subunit protocol to facilitate streaming and storing results from multiple workers. stestr originally started as a fork of the testrepository project. But, instead of being an interface for any test runner that used subunit, like testrepository, stestr concentrated on being a dedicated test runner for python projects. While stestr was originally forked from testrepository it is not backwards compatible with testrepository. At a high level the basic concepts of operation are shared between the two projects but the actual usage is not exactly the same.

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-stestr

    bookworm (Debian 12 (Bookworm)) (python): test runner similar to testrepository - Python 3.x

    3.2.1-1: all

    Source: python-stestr

  2. Package python-stestr-doc

    bookworm (Debian 12 (Bookworm)) (doc): test runner similar to testrepository - doc

    3.2.1-1: all

    Source: python-stestr

Debian 13 (Trixie)

  1. Package python3-stestr

    trixie (Debian 13 (Trixie)) (python): test runner similar to testrepository - Python 3.x

    4.1.0-3: all

    Source: python-stestr

  2. Package python-stestr-doc

    trixie (Debian 13 (Trixie)) (doc): test runner similar to testrepository - doc

    4.1.0-3: all

    Source: python-stestr

openSUSE Leap 15.6

  1. Package python3-stestr

    leap-15.6 (openSUSE Leap 15.6) (Development/Languages/Python): A test runner runner similar to testrepository

    2.6.0-8.4.10: noarch

    Source: python-stestr

openSUSE Tumbleweed

  1. Package python313-stestr

    tumbleweed (openSUSE Tumbleweed) (Unspecified): A parallel Python test runner built around subunit

    4.2.1-1.3: noarch

    Source: python-stestr

  2. Package python314-stestr

    tumbleweed (openSUSE Tumbleweed) (Unspecified): A parallel Python test runner built around subunit

    4.2.1-1.3: noarch

    Source: python-stestr

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.