explaingit

davehunt/pytest-bugzilla

Analysis updated 2026-08-14 · repo last pushed 2010-05-05

3PythonAudience · developerComplexity · 2/5DormantSetup · moderate

TLDR

A pytest plugin that links Python tests to Bugzilla bug IDs so known failures are marked as analysed instead of failed, helping teams distinguish new regressions from already-documented issues.

Mindmap

mindmap
  root((repo))
    What it does
      Links tests to Bugzilla bugs
      Marks known failures as analysed
      Warns on closed bug still failing
    How to use
      Install package
      Add bug ID to test docstrings
      Run tests with bugzilla flag
      Provide Bugzilla URL and credentials
    Use cases
      Large test suites
      Cleaner test reports
      QA triage automation
    Tech stack
      Python
      pytest
      Bugzilla API
    Audience
      QA engineers
      Developers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Tag failing tests with Bugzilla bug IDs so known issues are auto-marked as analysed instead of failed.

USE CASE 2

Get warnings when a bug is closed in Bugzilla but the corresponding test still fails, signalling a possible incomplete fix or stale test.

USE CASE 3

Keep large test suite reports clean by separating new regressions from already-documented bugs.

What is it built with?

PythonpytestBugzilla

How does it compare?

davehunt/pytest-bugzilla0marildo/imago0xdfi/glm-5.2-1m-4x-dgx-spark
Stars333
LanguagePythonPythonPython
Last pushed2010-05-05
MaintenanceDormant
Setup difficultymoderateeasyhard
Complexity2/52/55/5
Audiencedevelopergeneralresearcher

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires access to a Bugzilla server URL and login credentials, provided via command-line options or by editing the plugin file directly.

No license information is provided in the repository, so usage rights are unclear.

In plain English

pytest-bugzilla is a plugin that connects your Python testing workflow to Bugzilla, the bug-tracking system. It lets you tag individual tests with the ID of the bug they're meant to verify, so your test results automatically reflect the current status of that bug in your tracker. When you run your test suite, the plugin checks Bugzilla for the status of each tagged bug. If a test fails but the corresponding bug is still open in Bugzilla, the test gets marked as "analysed" instead of "Failed", a signal that the failure is already a known issue under investigation, not a surprise regression. If the bug has been closed but the test still fails, the plugin generates a warning, alerting you that something might be wrong: either the fix didn't fully work, or the test needs to be updated. This is useful for teams that run large test suites and want cleaner, more meaningful test reports. Instead of seeing a wall of "Failed" tests every time the suite runs, some of which are just known bugs waiting to be fixed, you get a report that distinguishes between new failures and ones you've already documented. A QA engineer or developer can then focus on the unexpected failures rather than re-triaging known issues. To use it, you install the package, run your tests with a --bugzilla flag, and add the bug ID (like #12345) to the docstring of any test function you want to track. You'll need to provide your Bugzilla server URL and login credentials, either via command-line options or by editing the plugin file directly to set defaults. The README doesn't go into detail on advanced configuration or supported Bugzilla versions, but the core workflow is straightforward: tag your tests, run the suite, and get smarter reporting.

Copy-paste prompts

Prompt 1
I run a large pytest suite and many failures are known bugs tracked in Bugzilla. Set up pytest-bugzilla so those tests are marked as analysed instead of failed, and warn me if a closed bug still has a failing test.
Prompt 2
Help me integrate pytest-bugzilla into my project: I need to add Bugzilla bug IDs to my test docstrings, configure the Bugzilla server URL and credentials, and run my suite with the --bugzilla flag.
Prompt 3
Write a pytest test function that is linked to Bugzilla bug #12345 using the pytest-bugzilla plugin, including the correct docstring annotation so the plugin checks that bug's status during the test run.

Frequently asked questions

What is pytest-bugzilla?

A pytest plugin that links Python tests to Bugzilla bug IDs so known failures are marked as analysed instead of failed, helping teams distinguish new regressions from already-documented issues.

What language is pytest-bugzilla written in?

Mainly Python. The stack also includes Python, pytest, Bugzilla.

Is pytest-bugzilla actively maintained?

Dormant — no commits in 2+ years (last push 2010-05-05).

What license does pytest-bugzilla use?

No license information is provided in the repository, so usage rights are unclear.

How hard is pytest-bugzilla to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is pytest-bugzilla for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.