allure-pytest-default-results
Generate default "unknown" results to show in Allure Report if test case does not run
Decision gist · record as of 2026-08-14
Yes, if you use Allure Report and need visibility into unrun tests. Install friction is low and maintenance is active. However, verify the current license status before use, and confirm that the "unknown" status integration with allure-pytest has been implemented (the package notes it was not yet in use as of 2025-01-31). Also watch for potential upstream replacement via allure-python issue #821.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires pytest and allure-pytest to be installed; the plugin generates results but does not itself run tests.
- Low friction install with only pytest and allure-pytest as runtime dependencies.
- Active maintenance as of 2026-04-06 with recent commits, though the package is very new (first release 2025-01-31).
License · maintenance · safety
(unclear) — License status is unclear—no SPDX identifier or raw license text is available. Verify licensing before use in proprietary or restricted contexts.
last release 2026-04-06 (130 days) · last repo commit 2026-04-06
0 known vulnerabilities (OSV.dev, 2026-08-14) · 143,058 downloads/mo, #11,185 on PyPI
Alternatives
Verify before relying
pip install allure-pytest-default-results
pytest --allure-default-dir=allure-default-results- Whether the "unknown" status integration with allure-pytest has been implemented since the 2025-01-31 note stating it was not yet used.
- Compatibility with allure-pytest versions and any specific Allure Report versions.
- Whether this plugin will be superseded by upstream allure-python feature (GitHub issue #821).
What it is and what it does
This pytest plugin extends allure-pytest to handle test cases that never execute—cases skipped due to setup failures, timeouts, or CI interruptions. By default, allure-pytest only reports tests that actually ran, leaving gaps in the Allure Report. This plugin generates placeholder "unknown" status results for each expected test case before the test run, then merges them with actual results afterward, so unrun tests appear in the report instead of vanishing.
The plugin is a thin wrapper around pytest's --allure-default-dir flag and works by creating default result JSON files that can be moved into the final results directory. It targets a specific gap in test reporting visibility and is maintained by Canonical, though it remains very early in its lifecycle (first release January 2025).
Use it for
- Ensure test cases show as "unknown" in Allure Report when a CI job times out mid-run.
- Track which tests never executed due to setup or fixture failures.
- Generate complete test inventory reports even when some test cases don't run.
- Diagnose gaps in test coverage by seeing which cases were skipped or never attempted.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you use Allure Report and need visibility into unrun tests.
Install friction is low and maintenance is active. However, verify the current license status before use, and confirm that the "unknown" status integration with allure-pytest has been implemented (the package notes it was not yet in use as of 2025-01-31). Also watch for potential upstream replacement via allure-python issue #821.
Install
allure-pytest-default-results on PyPI
Before you install
Low friction install with only pytest and allure-pytest as runtime dependencies. Active maintenance as of 2026-04-06 with recent commits, though the package is very new (first release 2025-01-31).
Requires pytest and allure-pytest to be installed; the plugin generates results but does not itself run tests.
License in practice
License status is unclear—no SPDX identifier or raw license text is available. Verify licensing before use in proprietary or restricted contexts.
Quickstart
pip install allure-pytest-default-results
pytest --allure-default-dir=allure-default-resultsVerify before relying
- Whether the "unknown" status integration with allure-pytest has been implemented since the 2025-01-31 note stating it was not yet used.
- Compatibility with allure-pytest versions and any specific Allure Report versions.
- Whether this plugin will be superseded by upstream allure-python feature (GitHub issue #821).
Package facts
| License | Not declared unclear |
| Python support | Supports the current Python release >=3.8 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 2 packagesallure-pytestpytest |
| Maintenance | Actively maintained 130 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 143,058 / month, #11,185 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Framework :: PytestProgramming Language :: Python :: 3Programming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.8Programming Language :: Python :: 3.9 |
Evidence: allure_pytest_default_results-0.1.4-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “allure report missing tests”
- allure-pytest-default-resultsGenerates default "unknown" status results for test cases that don't…
- allure-robotframeworkIntegrates Robot Framework test execution with Allure Report,…
- allure-pytest-bddIntegrates Allure Report with Pytest-BDD to capture and visualize…
Give your agent the search over MCP, or paste the wish link into any chat.
More Quality Assurance packages
Coverage.py measures which lines of Python code are executed during test runs, reporting coverage percentages and identifying untested code paths.
Install it if you want to measure test completeness or enforce coverage thresholds in your project.
Ruff is a Python linter and code formatter written in Rust that combines linting, formatting, and code fixing into a single tool, replacing Flake8, Black, isort, and related utilities.
Pexpect spawns and controls interactive console applications by sending input and matching output patterns, automating tasks that would otherwise require manual interaction.
Black reformats Python source code to a consistent style by parsing entire files and rewriting them according to an opinionated, deterministic set of rules, eliminating manual formatting decisions.
pytest-xdist distributes pytest tests across multiple CPU cores or machines to speed up test execution, with the simplest usage being `pytest -n auto` to spawn workers equal to available CPUs.
Install it if your test suite takes long enough that parallelization would save meaningful time.
Validates AWS CloudFormation templates in YAML or JSON format against resource provider schemas and best practices, checking property values and configuration correctness.
Install it if you work with CloudFormation templates.
See also allure-pytest · allure-pytest-bdd · allure-combine · allure-python-commons · allure-robotframework · allure-behave · pytest-watch · pytest-html · pytest-reportlog · behavex