reportforge-playwright-pdf

Designed PDF reports for Playwright pytest runs. Three templates cover three audiences: minimal for PR checks, detailed for QA deep dives, executive for stakeholder reviews.

Same product as the npm reporter @reportforge/playwright-pdf. One subscription key works across Node.js and Python, and machines share one cap.

Install

pip install reportforge-playwright-pdf

Requires playwright with browsers installed (python -m playwright install chromium). The plugin reuses Playwright's own Node runtime and Chromium, so there is nothing else to install.

Quick start

export RF_LICENSE_KEY=RFSU-XXXX-XXXX-XXXX-XXXX
pytest --pdf

The PDF lands at reports/report.pdf by default. Your tests always run in full; without an active subscription only the PDF is skipped.

Configuration

Flags for the common cases:

pytest --pdf --pdf-template=executive --pdf-output="reports/{date}-report.pdf"

Project defaults in pyproject.toml:

[tool.reportforge]
enabled = true
template = "detailed"
outputFile = "reports/{date}-{branch}-report.pdf"
projectName = "Checkout suite"

Every option of the npm reporter is accepted with the same camelCase names. The full reference lives at reportforge.org/docs/configuration; Python specifics at reportforge.org/docs/python.

What you get

• Pass/fail/flaky/timeout KPIs, suite breakdown, charts, and a release recommendation
• Failure deep dive with error text, on-device ML failure clustering, and screenshots from --screenshot=only-on-failure
• Run history trend and run-over-run diff
• Notifications to Slack, Teams, Discord, or email after the run
• Display redaction and AES-256 PDF encryption when you need them

Live run streaming and step trees are available in the Node.js reporter today and are on the roadmap here.

License

Elastic License 2.0. A paid subscription is required to generate PDFs: reportforge.org/pricing.