Releases: reporterplus/pytest-html-plus
v1.1.0
🚀 New Features
🔍 Universal Search Now Supports Error Messages
The report's universal search has been enhanced to index error messages and trace snippets.
Quickly find and group related failures by searching for:
TimeoutErrorNoSuchElementExceptionAssertionErrorexpected 200- Any custom error text present in failed tests
This makes investigating patterns and correlating failures across large reports much easier.
v1.0.1
v1.0.0
Added reusable configuration profiles for pytest-html-plus. ✨
You can now define named profiles in pyproject.toml and run them with --plus-profile=<name>, making it easier to reuse reporting settings across local runs and CI. CLI flags still take precedence when you want to override a profile for a specific run.
Documentation:
v0.5.2
Improvements ✨
Refinement to flaky test insights: Building on the recent flaky attempts feature, this update improves how attempt data is presented to reduce visual clutter and enhance debugging efficiency.
Optimized package footprint: Improved grouping in dependencies for a cleaner installation experience.
v0.5.1
✨ Flaky Tests — Now With Retry Insights
❌ ❌ ✅ → Passed after 3 attempts
Was it timing? cache? now you can actually see why.
🚀 What’s new
- Visualize every retry attempt for flaky and failed tests
- See failure -> number of attempts → recovery patterns clearly
- Inline error and trace per attempt
🧠 Why it matters
Flaky tests are often guesswork.
Now you can see exactly how a test behaved across retries — and debug with confidence.
🛠 Improvements
- Improved error and trace extraction
- Cleaner flaky test reporting
⚠️ Compatibility
- Dropped support for Python 3.9 (now requires Python 3.10+)
v0.5.0
What’s New:
- All report artifacts (HTML, JSON, metadata, XML, screenshots) are now consistently generated under the directory specified by --html-output. Closes #191
- JSON and XML options now accept filenames only, avoiding path-related confusion. Closes #191
pytest-html-plusCLI options are now grouped under a dedicated “pytest-html-plus reporting options” section in pytest --help instead of appearing under generic custom options. Closes #195
v0.4.9
New Features
JSON report included in CI artifacts
The generated JSON report is now bundled inside the test archive, making it easy to:
- Download from CI artifacts
- Directly load into the VS Code pytest-html-plus extension without extra steps
Helpful inline tips for missing values
When a value is missing in the report, we now show actionable guidance on how to populate it. This reduces guesswork and improves first-time setup experience
Example: suggests using --rp-env when environment data is missing
New CLI option: --rp-env
- Introduced --rp-env to explicitly pass environment context to pytest-html-plus
- Helps avoid conflicts with existing pytest flags
UI Improvements
- Warmer, more readable color palette
- Updated report colors to feel less harsh and more pleasant for longer reading sessions
- Improves overall visual clarity and comfort
Bug Fixes
- Fixed compatibility with existing --env / --environment flags
- Resolved an issue where projects already using these flags would encounter errors
- pytest-html-plus now coexists cleanly with existing CLI options
v0.4.7
✨ What’s New
Implements #178
Setup & Teardown errors are now fully captured in reports
- Fixture failures (setup, teardown)
- setup_class / teardown_class failures, fixture failures
- New “Error” status distinct from test failures
- Dedicated Error filter in the HTML report
- Errors are visually highlighted for quick identification
v0.4.6
v0.4.5
What's Changed
- Fixed the problem described in #168 (Causes pytest to abort with internal error when running pytest with fatal warnings).
Contributor(s):
- Appreciation to @ernestomehra for the contribution!
