@reportforge/playwright-pdf 0.30.0 → 0.31.0

package/README.md

@@ -68,7 +68,7 @@ Three templates, one reporter. Every PDF is fully offline: fonts, charts, and sc
 - **Executive report brief band**: leads with a plain-language brief (trend + root causes) and one hero pass-rate number instead of a flat KPI grid
 - **Data protection**: AES-256 password-protected PDFs (no external tools) and opt-in redaction of credentials/PII in report content and live streams
 - **Hybrid licensing**: one short key unlocks it; reports keep rendering offline via a locally cached license between refreshes
-- **Python and .NET support**: the same reports for pytest-playwright (`reportforge-playwright-pdf` on PyPI) and for NUnit/MSTest/xUnit (`ReportForge.Playwright.Pdf` on NuGet); one subscription key covers every ecosystem (live runs and step trees are Node.js-only today)
+- **Python and .NET support**: the same reports for pytest-playwright (`reportforge-playwright-pdf` on PyPI) and for NUnit/MSTest/xUnit (`ReportForge.Playwright.Pdf` on NuGet); one subscription key covers every ecosystem, and live runs stream from all three (step trees are Node.js-only today)
 - **Update notice**: when a newer reporter version is published, each run ends with one info line naming it and the update command; no extra network calls
 
 ---
@@ -180,7 +180,7 @@ template = "detailed"
 outputFile = "reports/{date}-{branch}-report.pdf"
 ```
 
-The plugin reuses the Node runtime and Chromium that Playwright for Python already ships, so there is nothing else to install. pytest-xdist and pytest-rerunfailures are supported; failure screenshots from `--screenshot only-on-failure` are embedded, and trace/video artifacts from `--tracing` / `--video` feed the defect log's evidence links (pair with `evidenceUrlTemplate` for clickable CI links). Passing `--browser` more than once splits the report into one project per browser and unlocks the cross-browser comparison section. Live runs and step trees are Node.js-only today. Full guide: [reportforge.org/docs/python](https://reportforge.org/docs/python).
+The plugin reuses the Node runtime and Chromium that Playwright for Python already ships, so there is nothing else to install. pytest-xdist and pytest-rerunfailures are supported; failure screenshots from `--screenshot only-on-failure` are embedded, and trace/video artifacts from `--tracing` / `--video` feed the defect log's evidence links (pair with `evidenceUrlTemplate` for clickable CI links). Passing `--browser` more than once splits the report into one project per browser and unlocks the cross-browser comparison section. Enable `[tool.reportforge.live] enabled = true` and the run streams to a shareable watch page, same as Node.js; step trees stay Node.js-only today. Full guide: [reportforge.org/docs/python](https://reportforge.org/docs/python).
 
 ---
 
@@ -195,7 +195,7 @@ set RF_LICENSE_KEY=RFSU-XXXX-XXXX-XXXX-XXXX
 dotnet test --logger "reportforge;output=reports/run.pdf;template=detailed"
 ```
 
-Full options come from a JSON file with the same camelCase names as this reporter: `--logger "reportforge;optionsFile=rf-options.json"`. The logger reuses the Node runtime Microsoft.Playwright places in your test output and a Playwright-managed Chromium, so there is nothing else to install. Retried tests render as flaky with their attempt history; categories become tags. Trace archives and videos attached via `TestContext.AddTestAttachment` feed the defect log's evidence links (pair with `evidenceUrlTemplate` for clickable CI links). A `dotnet test` run drives one browser, so the cross-browser comparison section stays hidden here; live runs and step trees are Node.js-only today. Full guide: [reportforge.org/docs/dotnet](https://reportforge.org/docs/dotnet).
+Full options come from a JSON file with the same camelCase names as this reporter: `--logger "reportforge;optionsFile=rf-options.json"`. The logger reuses the Node runtime Microsoft.Playwright places in your test output and a Playwright-managed Chromium, so there is nothing else to install. Retried tests render as flaky with their attempt history; categories become tags. Trace archives and videos attached via `TestContext.AddTestAttachment` feed the defect log's evidence links (pair with `evidenceUrlTemplate` for clickable CI links). A `dotnet test` run drives one browser, so the cross-browser comparison section stays hidden here. Add `"live": { "enabled": true }` to the options file and the run streams to a shareable watch page (rows appear as tests finish); step trees stay Node.js-only today. Full guide: [reportforge.org/docs/dotnet](https://reportforge.org/docs/dotnet).
 
 ---
 
@@ -288,6 +288,8 @@ reporter: [
 
 Sharded runs need no extra config: every shard of one CI run converges on the same live view automatically. Set `RF_LIVE_RUN_ID` to override when your CI is not auto-detected.
 
+**Python and .NET stream too.** Enable live the same way (`[tool.reportforge.live] enabled = true` in `pyproject.toml`, or `"live": { "enabled": true }` in the .NET options file) with `RF_LICENSE_KEY` set, and the run prints the same watch link and streams per-test progress to the same page. pytest rows appear as tests start and finish; .NET's test platform reports results only on completion, so rows appear as each test finishes. Adapter runs are single-shard: parallel CI matrix jobs in one workflow should set a distinct `RF_LIVE_RUN_ID` per job so each gets its own watch page. The live step trail and console streaming remain Node.js-only.
+
 Live streaming is best-effort and entitlement-gated: if the server is unreachable the run is unaffected, and an active subscription with the `live` feature is required. If you've configured Slack/Teams/Discord notifications, the watch link is also posted to those channels when the run starts.
 
 > **Security:** the watch link exposes test titles, statuses, step titles, and failure details (error messages, code frames, stacks) to anyone holding it — no login needed, which is the point: share it with whoever should watch. Your `redact` rules apply to everything on the link, error text included. The token is scoped to that one run, and rotating your license key never breaks an already-shared link. Leaving `console: false` is recommended: enabling it streams your tests' stdout/stderr to anyone holding the link. Full details at [reportforge.org/docs/advanced/live](https://reportforge.org/docs/advanced/live).

package/dist/index.js

@@ -15457,7 +15457,7 @@ var PdfReporter = class {
     if (this.options.redact.enabled) {
       this.redactor = new Redactor(this.options.redact);
     }
-    this.version = true ? "0.30.0" : "0.x";
+    this.version = true ? "0.31.0" : "0.x";
     logger.info(`@reportforge/playwright-pdf v${this.version} initialised`);
     this.licenseClient = new LicenseClient({
       licenseKey: this.options.licenseKey,

package/dist/index.mjs

@@ -15458,7 +15458,7 @@ var PdfReporter = class {
     if (this.options.redact.enabled) {
       this.redactor = new Redactor(this.options.redact);
     }
-    this.version = true ? "0.30.0" : "0.x";
+    this.version = true ? "0.31.0" : "0.x";
     logger.info(`@reportforge/playwright-pdf v${this.version} initialised`);
     this.licenseClient = new LicenseClient({
       licenseKey: this.options.licenseKey,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reportforge/playwright-pdf",
-  "version": "0.30.0",
+  "version": "0.31.0",
   "description": "Playwright Test reporter that generates designed PDF reports: minimal, detailed, and executive templates with CI/CD integrations",
   "license": "Elastic-2.0",
   "author": "ReportForge",