pgpro-pytest-html-merger
A professional tool to merge multiple pytest-html reports into a single, consistent HTML report. Developed and maintained by Postgres Professional.
Key Features
- Smart Merging: Combines test results, logs, and metadata from multiple sources.
- Flexible Input: Supports individual files and entire directories.
- Customizable: Set your own report title and output filename.
- Modern Support: Fully compatible with Python 3.8 through 3.14.
Installation
You can install the package directly from the repository (until it's published to PyPI):
pip install pgpro-pytest-html-merger
Usage
After installation, the tool is available via the pgpro-pytest-html-merger command.
Basic Examples
Merge all reports in a directory:
pgpro-pytest-html-merger -i ./reports -o summary.html
Merge specific files with a custom title:
pgpro-pytest-html-merger report1.html report2.html -o final.html --title "Nightly Build"
Combine directories and individual files:
pgpro-pytest-html-merger -i ./unit-tests -i ./e2e-tests extra-report.html -o full-report.html
Command Line Arguments
| Argument | Shorthand | Description | Default |
|---|---|---|---|
--version |
Show program's version number and exit | None | |
--input-dir |
-i |
Directory containing HTML reports (can be used multiple times) | None |
--out |
-o |
Name of the output HTML report | merged.html |
--title |
-t |
Title of the output HTML report | None |
--verbose |
-v |
Level of logging verbosity | 3 |
html_files |
Positional arguments for individual HTML files | None |
Contributing
- Fork the repository.
- Create your feature branch (
git checkout -b feature/amazing-feature). - Commit your changes (
git commit -m 'feat: add some amazing feature'). - Push to the branch (
git push origin feature/amazing-feature). - Open a Pull Request.
License
This project is licensed under the MIT License - see the LICENSE file for details.
© 2026 Postgres Professional
Metadata
Release files for pgpro-pytest-html-merger 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pgpro_pytest_html_merger-0.4.0.tar.gz | 11.5 kB | With provenance | Details for pgpro_pytest_html_merger-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pgpro_pytest_html_merger-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for pgpro_pytest_html_merger-0.4.0-py3-none-any.whl |
Total release size: 22.5 kB
Release files / pgpro_pytest_html_merger-0.4.0.tar.gz
| Download URL | pgpro_pytest_html_merger-0.4.0.tar.gz |
|---|---|
| Size | 11.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
760d825f1f7015af313024794a962e6dececf82d6d4970c20da6c4b3a2c751af
|
|
BLAKE2b-256 checksum How to use checksums |
8d0244f89c5ac3043d97560b4c86169b596080afb4de2ed7faa52e47eb4be44d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 12, 2026.
Transparency logRelease files / pgpro_pytest_html_merger-0.4.0-py3-none-any.whl
| Download URL | pgpro_pytest_html_merger-0.4.0-py3-none-any.whl |
|---|---|
| Size | 10.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8043a770afadd67da8e02d907b7228163e9b5b0c9a14056dad7514d594d85164
|
|
BLAKE2b-256 checksum How to use checksums |
0a694b4765ad66778266220b98bec1ff40cd37445bf7a663e2e0a34bdec5ab4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 12, 2026.
Transparency logSecurity for pgpro-pytest-html-merger 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pgpro_pytest_html_merger-0.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.