wtf is pytest-bugzilla?

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.