@reportforge/playwright-pdf 0.24.0 → 0.26.1

package/README.md

@@ -58,6 +58,7 @@ Three templates, one reporter. Every PDF is fully offline: fonts, charts, and sc
 - **Notifications**: post pass/fail summaries to Slack, Teams, Discord, or email after each run; configurable trigger (`always` / `failure` / `success`) per channel; email and Discord support optional PDF attachment via `attachPdf`
 - **Flakiness trend**: top-N flakiest tests table with per-test dot sparkline across stored history runs in the `detailed` template; `flakinessTopN` option (default 5, `0` disables)
 - **Pass-rate trend**: cross-run trend chart from stored history; opt-in `remoteHistory` keeps the trend alive on ephemeral CI runners by storing aggregate numbers only (pass rate, counts, duration, verdict; no test titles or error text, and the branch name never travels in plaintext), with no extra network calls
+- **Run-over-run diff**: every report shows what changed since the previous run on the same branch: new failures, fixed tests, and still-failing tests, and the same summary rides along in Slack, Teams, Discord, and email notifications
 - **Offline failure analysis**: sorts each failure into one of 7 root-cause buckets and renders a root-cause chip under each failed test in the `detailed` PDF (dominant-cause one-liner in `executive`). No network, no AI service: a small embedded classifier with automatic updates; pin it any time. Full details at [reportforge.org/docs/advanced/failure-analysis](https://reportforge.org/docs/advanced/failure-analysis).
 - **On-device training**: teach the classifier your team's failures without any data leaving your machine. Label locally-collected samples (`npx @reportforge/playwright-pdf label-feedback`), then `train-model` trains and cross-validates a personal layer on-device; it activates only when it measurably beats the base model on your own labeled set (`evaluate-model` shows the comparison any time). Commit the model file to your repo via `failureAnalysis.localModelPath` to share it with CI. Training data, the trained model, and evaluation are all local files; the analysis code cannot even name a network primitive (enforced by an automated source audit).
 - `npx @reportforge/playwright-pdf export-feedback`: merges your locally-collected feedback (tokenized + redacted) into one CSV for review or moving between machines. Local file only; there is no upload.
@@ -213,14 +214,14 @@ All options are the second element of the reporter tuple.
 | `slowTestThreshold` | `number` | `10` | Minimum timed-test count before `SLOW` badges appear in the suite breakdown: below this, every test is trivially the "slowest" so badges stay hidden. On larger runs only genuine outliers (at least 2× the median test duration) are badged, so the badge stays rare. Set to `0` to drop the run-size gate (outliers still required). |
 | `requirementTagPattern` | `string` | `'^@?[A-Z][A-Z0-9]*-\\d+$'` | Regex deciding which tags count as requirement IDs in the Requirements Traceability section (`detailed` template). Matching tags (ticket shapes like `@ODP-5328`, `REQ-001`) get the traceability matrix; everything else (`@regression`, `@sanity`) collapses into a compact tag summary instead of repeating identical rows. Set to `''` to disable the split and list every tag in the matrix. |
 | `templatePath` | `string \| string[]` | n/a | Path to a custom Handlebars (`.hbs`) template file. Takes precedence over `template`. Pass an array to generate one PDF per custom template. See the Custom Templates docs. |
-| `sections` | `object` | per-template | Override which report sections appear, on top of the chosen template's defaults. Flat keys are the baseline for every chosen template; per-template keys (`minimal`\|`detailed`\|`executive`) override per template. Block toggles: `coverPage`, `analysisOneliner`, `releaseGate`, `summary`, `charts`, `trend`, `requirementsMatrix`, `ciEnvironment`, `suiteBreakdown`, `failureDeepDive`, `failureAnalysis`, `slowTests`, `defectLog`, `briefBand`. Display modifiers: `passRate`, `fullEnvironment`, `retries`, `fullFailures`, `stackTraces`. See the Report Sections docs. |
+| `sections` | `object` | per-template | Override which report sections appear, on top of the chosen template's defaults. Flat keys are the baseline for every chosen template; per-template keys (`minimal`\|`detailed`\|`executive`) override per template. 20 keys total. Block toggles: `coverPage`, `analysisOneliner`, `releaseGate`, `summary`, `charts`, `trend`, `requirementsMatrix`, `ciEnvironment`, `suiteBreakdown`, `failureDeepDive`, `failureAnalysis`, `slowTests`, `defectLog`, `briefBand`, `runDiff`. Display modifiers: `passRate`, `fullEnvironment`, `retries`, `fullFailures`, `stackTraces`. `runDiff` (block toggle, on by default in all three templates) shows new failures, fixed tests, and still-failing tests compared with the previous run on the same branch. See the Report Sections docs. |
 <!-- AUTOGEN:options-table END -->
 
 Full reference: [reportforge.org/docs/configuration](https://reportforge.org/docs/configuration).
 
 ### Live Runs
 
-Watch a run as it happens. With `live` enabled, the reporter prints an unguessable watch link (boxed under a `Live Tracker` heading) to your CI logs at run start and streams per-test progress to a hosted dashboard while tests execute. All shards of one CI run converge on a single live view. Each test shows its steps and assertions as sub-lines beneath its row: each step once, as it settles, indented under its parent `test.step` in source order (Playwright's hooks, fixtures, and teardown are filtered out). The PDF is still generated at the end, unchanged.
+Watch a run as it happens. With `live` enabled, the reporter prints an unguessable watch link (boxed under a `Live Tracker` heading) to your CI logs at run start and streams per-test progress to a hosted dashboard while tests execute. All shards of one CI run converge on a single live view. Tests are grouped by spec file and describe block into collapsible suites, failures first. While a test runs you see its steps settle live under the row; once it finishes, the row expands into the full step tree: your `test.step` names with the Playwright calls and assertions nested beneath them, and on failure the complete error message, code frame, and stack attached to the exact step that failed (Playwright's hooks, fixtures, and teardown are filtered out unless the failure happened inside one). The PDF is still generated at the end, unchanged.
 
 > The watch link is entitlement-gated. If you enable `live` but see no `Live Tracker` line, the reporter logs why (missing `RF_LICENSE_KEY`, or a cached token without the `live` entitlement; delete `~/.reportforge/license.json` to force re-activation).
 
@@ -239,13 +240,13 @@ reporter: [
 ],
 ```
 
-`steps: 'intent'` shows only your `test.step` names (plus any failing step): the cleanest, most readable trail. `'all'` adds every action and assertion beneath its parent step; `'failed'` (default) keeps intent + assertions + failures.
+`steps: 'intent'` shows only your `test.step` names (plus any failing step): the cleanest, most readable trail. `'all'` adds every action and assertion beneath its parent step; `'failed'` (default) keeps intent + assertions + failures. The mode shapes only the live trail while a test is still running; the full step tree a finished test expands into is always sent.
 
 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.
 
 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 (and step titles when `steps` is on) to anyone holding it — no login needed, which is the point: share it with whoever should watch. 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).
+> **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).
 
 ### Shard Merging
 
@@ -316,7 +317,7 @@ The `on` trigger controls when the message fires:
 
 **PDF attachment** (`attachPdf: true`) is available on `email` and `discord`: Slack and Teams webhooks cannot carry file uploads. On Discord the PDF is uploaded with the message; if the upload fails or the PDF exceeds Discord's file-size cap, the summary still posts without the attachment. With multiple templates, the first PDF is attached.
 
-The summary includes pass rate, test counts, duration, and the report filename. Notifications require a valid license and fire after PDF generation (or after a PDF failure; you still get the ping).
+The summary includes pass rate, test counts, duration, and the report filename. When a previous run on the same branch exists, the message also carries a run-over-run diff line: new failures, fixed tests, and tests still failing. Notifications require a valid license and fire after PDF generation (or after a PDF failure; you still get the ping).
 
 ### Data Protection
 
@@ -364,6 +365,8 @@ Full details at [reportforge.org/docs/advanced/security](https://reportforge.org
 
 After each run the reporter appends a summary entry to a local JSON file and renders a pass-rate sparkline + verdict row in the `detailed` template.
 
+**Since Last Run**: every report also gets a section (`runDiff`, on by default in all three templates) comparing the current run against the previous run on the same branch: new failures, fixed tests, and tests still failing, with the same summary line carried into Slack, Teams, Discord, and email notifications. The first run after upgrading has no comparable prior run to diff against, so the section starts appearing from the second run onward. It reads only the local history file, so test names never leave your machine; see the ephemeral-CI note below for keeping that file around between runs. Like the flakiness table, it rides history tracking (`showTrend`, on by default), and the notification line follows history availability rather than the `runDiff` section toggle.
+
 **Local dev (zero config)**: history is written automatically to `~/.reportforge/{projectKey}/history.json`. The sparkline appears once two or more runs have been recorded.
 
 **CI with ephemeral runners (recommended)**: enable the server-side trend store; the local file is wiped with the workspace, leaving the chart stuck at one data point:
@@ -375,7 +378,7 @@ reporter: [['@reportforge/playwright-pdf', {
 }]]
 ```
 
-One small authenticated request per run, carrying aggregate numbers only (pass rate, counts, duration, verdict; no test titles, no error text, and the branch name never travels in plaintext). The server keeps roughly the last 100 runs per project + branch, expiring after 180 days, and returns them for the chart; any failure falls back to the local file. The flakiness table stays local-only by design (it needs test titles, which never leave your machine). Bitbucket Pipelines users especially: Bitbucket caches are immutable once written, so `remoteHistory` is the practical path there.
+One small authenticated request per run, carrying aggregate numbers only (pass rate, counts, duration, verdict; no test titles, no error text, and the branch name never travels in plaintext). The server keeps roughly the last 100 runs per project + branch, expiring after 180 days, and returns them for the chart; any failure falls back to the local file. This feeds the trend chart only: the flakiness table and the Since Last Run diff both stay local-only by design (they need test titles, which never leave your machine); to keep either alive on ephemeral runners, use the CI caching alternative below to persist `historyFile` instead. Bitbucket Pipelines users especially: Bitbucket caches are immutable once written, so `remoteHistory` is the practical path for the trend chart there.
 
 **CI caching alternative** (keeps even aggregate numbers off the server): set `historyFile` to a project-relative path and cache it between runs:
 

package/ci-templates/azure-devops/azure-pipelines.yml

@@ -1,58 +1,58 @@
-# Add this to your azure-pipelines.yml
-# Requires Node.js tool installed on the agent
-
-trigger:
-  branches:
-    include:
-      - main
-      - develop
-
-pr:
-  branches:
-    include:
-      - main
-
-pool:
-  vmImage: 'ubuntu-latest'
-
-variables:
-  - group: reportforge-secrets  # Variable group containing RF_LICENSE_KEY
-
-stages:
-  - stage: Test
-    displayName: 'Playwright Tests + PDF Report'
-    jobs:
-      - job: PlaywrightTest
-        displayName: 'Run Tests'
-        steps:
-          - task: NodeTool@0
-            displayName: 'Install Node.js'
-            inputs:
-              versionSpec: '22.x'
-
-          - script: npm ci
-            displayName: 'Install dependencies'
-
-          - script: npx playwright install chromium --with-deps
-            displayName: 'Install Playwright browsers'
-
-          - script: npx playwright test
-            displayName: 'Run Playwright tests'
-            env:
-              RF_LICENSE_KEY: $(RF_LICENSE_KEY)
-
-          - task: PublishPipelineArtifact@1
-            displayName: 'Upload PDF Report'
-            condition: always()
-            inputs:
-              targetPath: playwright-report
-              artifact: playwright-pdf-report
-              publishLocation: pipeline
-
-          - task: PublishTestResults@2
-            displayName: 'Publish Test Results'
-            condition: always()
-            inputs:
-              testResultsFormat: 'JUnit'
-              testResultsFiles: 'test-results/results.xml'
-              failTaskOnFailedTests: false
+# Add this to your azure-pipelines.yml
+# Requires Node.js tool installed on the agent
+
+trigger:
+  branches:
+    include:
+      - main
+      - develop
+
+pr:
+  branches:
+    include:
+      - main
+
+pool:
+  vmImage: 'ubuntu-latest'
+
+variables:
+  - group: reportforge-secrets  # Variable group containing RF_LICENSE_KEY
+
+stages:
+  - stage: Test
+    displayName: 'Playwright Tests + PDF Report'
+    jobs:
+      - job: PlaywrightTest
+        displayName: 'Run Tests'
+        steps:
+          - task: NodeTool@0
+            displayName: 'Install Node.js'
+            inputs:
+              versionSpec: '22.x'
+
+          - script: npm ci
+            displayName: 'Install dependencies'
+
+          - script: npx playwright install chromium --with-deps
+            displayName: 'Install Playwright browsers'
+
+          - script: npx playwright test
+            displayName: 'Run Playwright tests'
+            env:
+              RF_LICENSE_KEY: $(RF_LICENSE_KEY)
+
+          - task: PublishPipelineArtifact@1
+            displayName: 'Upload PDF Report'
+            condition: always()
+            inputs:
+              targetPath: playwright-report
+              artifact: playwright-pdf-report
+              publishLocation: pipeline
+
+          - task: PublishTestResults@2
+            displayName: 'Publish Test Results'
+            condition: always()
+            inputs:
+              testResultsFormat: 'JUnit'
+              testResultsFiles: 'test-results/results.xml'
+              failTaskOnFailedTests: false

package/ci-templates/github-actions/basic-workflow.yml

@@ -1,44 +1,44 @@
-# Copy this file to .github/workflows/playwright.yml in your project
-name: Playwright Tests + PDF Report
-
-on:
-  push:
-    branches: [main, develop]
-  pull_request:
-    branches: [main]
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: '22'
-          cache: 'npm'
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Install Playwright browsers
-        run: npx playwright install chromium --with-deps
-
-      - name: Run Playwright tests
-        run: npx playwright test
-        env:
-          RF_LICENSE_KEY: ${{ secrets.RF_LICENSE_KEY }}
-
-      - name: Upload PDF Report
-        if: always()
-        uses: actions/upload-artifact@v4
-        with:
-          name: playwright-pdf-report
-          path: playwright-report/*.pdf
-          retention-days: 30
-
-      - name: Comment PR
-        if: always() && github.event_name == 'pull_request'
-        uses: ./.github/actions/playwright-pdf-report
-        with:
-          github-token: ${{ secrets.GITHUB_TOKEN }}
+# Copy this file to .github/workflows/playwright.yml in your project
+name: Playwright Tests + PDF Report
+
+on:
+  push:
+    branches: [main, develop]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '22'
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Install Playwright browsers
+        run: npx playwright install chromium --with-deps
+
+      - name: Run Playwright tests
+        run: npx playwright test
+        env:
+          RF_LICENSE_KEY: ${{ secrets.RF_LICENSE_KEY }}
+
+      - name: Upload PDF Report
+        if: always()
+        uses: actions/upload-artifact@v4
+        with:
+          name: playwright-pdf-report
+          path: playwright-report/*.pdf
+          retention-days: 30
+
+      - name: Comment PR
+        if: always() && github.event_name == 'pull_request'
+        uses: ./.github/actions/playwright-pdf-report
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}

package/ci-templates/gitlab-ci/.gitlab-ci.yml

@@ -1,42 +1,42 @@
-# Add this job to your .gitlab-ci.yml
-# Uses the official Playwright Docker image which includes Chromium
-
-variables:
-  RF_LICENSE_KEY: $REPORTFORGE_LICENSE  # Set in GitLab CI/CD Settings > Variables
-
-playwright-tests:
-  image: mcr.microsoft.com/playwright:v1.49.0-jammy
-  stage: test
-  script:
-    - npm ci
-    - npx playwright test
-  artifacts:
-    name: "playwright-pdf-${CI_COMMIT_SHORT_SHA}"
-    paths:
-      - playwright-report/*.pdf
-    expire_in: 30 days
-    when: always
-    expose_as: 'Playwright PDF Report'
-  variables:
-    PUPPETEER_EXECUTABLE_PATH: /usr/bin/chromium-browser
-  rules:
-    - if: $CI_MERGE_REQUEST_ID
-    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
-
-# Optional: Post merge request note with report link
-notify-mr:
-  stage: .post
-  image: alpine:latest
-  script:
-    - |
-      if [ -n "$CI_MERGE_REQUEST_IID" ]; then
-        curl -s --request POST \
-          --header "PRIVATE-TOKEN: $CI_API_TOKEN" \
-          --header "Content-Type: application/json" \
-          --data "{\"body\": \"📄 Playwright PDF report available: [Download](${CI_JOB_URL}/artifacts/download)\"}" \
-          "${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/merge_requests/${CI_MERGE_REQUEST_IID}/notes"
-      fi
-  rules:
-    - if: $CI_MERGE_REQUEST_ID
-      when: always
-  needs: [playwright-tests]
+# Add this job to your .gitlab-ci.yml
+# Uses the official Playwright Docker image which includes Chromium
+
+variables:
+  RF_LICENSE_KEY: $REPORTFORGE_LICENSE  # Set in GitLab CI/CD Settings > Variables
+
+playwright-tests:
+  image: mcr.microsoft.com/playwright:v1.49.0-jammy
+  stage: test
+  script:
+    - npm ci
+    - npx playwright test
+  artifacts:
+    name: "playwright-pdf-${CI_COMMIT_SHORT_SHA}"
+    paths:
+      - playwright-report/*.pdf
+    expire_in: 30 days
+    when: always
+    expose_as: 'Playwright PDF Report'
+  variables:
+    PUPPETEER_EXECUTABLE_PATH: /usr/bin/chromium-browser
+  rules:
+    - if: $CI_MERGE_REQUEST_ID
+    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
+
+# Optional: Post merge request note with report link
+notify-mr:
+  stage: .post
+  image: alpine:latest
+  script:
+    - |
+      if [ -n "$CI_MERGE_REQUEST_IID" ]; then
+        curl -s --request POST \
+          --header "PRIVATE-TOKEN: $CI_API_TOKEN" \
+          --header "Content-Type: application/json" \
+          --data "{\"body\": \"📄 Playwright PDF report available: [Download](${CI_JOB_URL}/artifacts/download)\"}" \
+          "${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/merge_requests/${CI_MERGE_REQUEST_IID}/notes"
+      fi
+  rules:
+    - if: $CI_MERGE_REQUEST_ID
+      when: always
+  needs: [playwright-tests]

package/ci-templates/jenkins/Jenkinsfile

@@ -1,54 +1,54 @@
-// Add this stage to your existing Jenkinsfile
-// Requires: Node.js tool configured, Chrome/Chromium installed on agent
-
-pipeline {
-    agent { label 'linux' }
-
-    environment {
-        RF_LICENSE_KEY = credentials('reportforge-license-key')
-    }
-
-    stages {
-        stage('Install') {
-            steps {
-                sh 'npm ci'
-                sh 'npx playwright install chromium'
-            }
-        }
-
-        stage('Playwright Tests + PDF Report') {
-            steps {
-                sh 'npx playwright test'
-            }
-            post {
-                always {
-                    // Archive the PDF report as a build artifact
-                    archiveArtifacts(
-                        artifacts: 'playwright-report/*.pdf',
-                        allowEmptyArchive: true,
-                        fingerprint: true
-                    )
-                    // Publish HTML alongside (optional)
-                    publishHTML(target: [
-                        allowMissing: true,
-                        alwaysLinkToLastBuild: true,
-                        keepAll: true,
-                        reportDir: 'playwright-report',
-                        reportFiles: '*.pdf',
-                        reportName: 'Playwright PDF Report'
-                    ])
-                }
-            }
-        }
-    }
-
-    post {
-        failure {
-            emailext(
-                subject: "FAILED: ${env.JOB_NAME} #${env.BUILD_NUMBER}",
-                body: "Build failed. PDF report: ${env.BUILD_URL}artifact/playwright-report/",
-                recipientProviders: [[$class: 'DevelopersRecipientProvider']]
-            )
-        }
-    }
-}
+// Add this stage to your existing Jenkinsfile
+// Requires: Node.js tool configured, Chrome/Chromium installed on agent
+
+pipeline {
+    agent { label 'linux' }
+
+    environment {
+        RF_LICENSE_KEY = credentials('reportforge-license-key')
+    }
+
+    stages {
+        stage('Install') {
+            steps {
+                sh 'npm ci'
+                sh 'npx playwright install chromium'
+            }
+        }
+
+        stage('Playwright Tests + PDF Report') {
+            steps {
+                sh 'npx playwright test'
+            }
+            post {
+                always {
+                    // Archive the PDF report as a build artifact
+                    archiveArtifacts(
+                        artifacts: 'playwright-report/*.pdf',
+                        allowEmptyArchive: true,
+                        fingerprint: true
+                    )
+                    // Publish HTML alongside (optional)
+                    publishHTML(target: [
+                        allowMissing: true,
+                        alwaysLinkToLastBuild: true,
+                        keepAll: true,
+                        reportDir: 'playwright-report',
+                        reportFiles: '*.pdf',
+                        reportName: 'Playwright PDF Report'
+                    ])
+                }
+            }
+        }
+    }
+
+    post {
+        failure {
+            emailext(
+                subject: "FAILED: ${env.JOB_NAME} #${env.BUILD_NUMBER}",
+                body: "Build failed. PDF report: ${env.BUILD_URL}artifact/playwright-report/",
+                recipientProviders: [[$class: 'DevelopersRecipientProvider']]
+            )
+        }
+    }
+}

package/dist/cli/index.js

@@ -311,6 +311,24 @@ function buildDemoCharts(passed, failed, skipped, flaky, total) {
     ]
   };
 }
+function buildDemoRunDiff() {
+  return {
+    newFailures: [
+      { id: "auth-5", title: "should block brute-force attempts after 5 tries" },
+      { id: "cat-7", title: "should lazy-load images on scroll" }
+    ],
+    stillFailing: [
+      { id: "co-3", title: "should reject expired promo code" }
+    ],
+    fixed: [
+      { id: "co-5", title: "should complete Stripe checkout" }
+    ],
+    noLongerRun: [],
+    baselineRunId: "demo-1d",
+    baselineTimestamp: DEMO_BASE_TS - 864e5,
+    baselineTruncated: false
+  };
+}
 function buildDemoReportData(template = "detailed") {
   const projects = [
     makeProject("chromium", [
@@ -362,7 +380,8 @@ function buildDemoReportData(template = "detailed") {
       projectCount: 2,
       workerCount: 4
     },
-    charts
+    charts,
+    runDiff: buildDemoRunDiff()
   };
 }
 var DEMO_BASE_TS, DEMO_LICENSE_INFO, DEMO_AUTH_TESTS, DEMO_CHECKOUT_TESTS, DEMO_CATALOG_TESTS;
@@ -6498,6 +6517,7 @@ var init_sections = __esm({
       "slowTests",
       "defectLog",
       "briefBand",
+      "runDiff",
       // display modifiers
       "passRate",
       "fullEnvironment",
@@ -6521,6 +6541,7 @@ var init_sections = __esm({
         slowTests: false,
         defectLog: false,
         briefBand: false,
+        runDiff: true,
         passRate: true,
         fullEnvironment: false,
         retries: true,
@@ -6542,6 +6563,7 @@ var init_sections = __esm({
         slowTests: true,
         defectLog: true,
         briefBand: false,
+        runDiff: true,
         passRate: true,
         fullEnvironment: true,
         retries: true,
@@ -6568,6 +6590,7 @@ var init_sections = __esm({
         slowTests: true,
         defectLog: false,
         briefBand: true,
+        runDiff: true,
         passRate: true,
         fullEnvironment: false,
         retries: false,

package/dist/index.d.mts

@@ -1,11 +1,11 @@
 import { Reporter, FullConfig, Suite, TestCase, TestResult, TestStep, FullResult } from '@playwright/test/reporter';
 
 /**
- * Canonical section catalog. 14 block toggles (section present/absent) followed
+ * Canonical section catalog. 15 block toggles (section present/absent) followed
  * by 5 display modifiers (tweak a section that is on). Single source of truth —
  * the Zod schema in src/config/schema.ts builds its flag shape from this array.
  */
-declare const SECTION_KEYS: readonly ["coverPage", "analysisOneliner", "releaseGate", "summary", "charts", "trend", "requirementsMatrix", "ciEnvironment", "suiteBreakdown", "failureDeepDive", "failureAnalysis", "slowTests", "defectLog", "briefBand", "passRate", "fullEnvironment", "retries", "fullFailures", "stackTraces"];
+declare const SECTION_KEYS: readonly ["coverPage", "analysisOneliner", "releaseGate", "summary", "charts", "trend", "requirementsMatrix", "ciEnvironment", "suiteBreakdown", "failureDeepDive", "failureAnalysis", "slowTests", "defectLog", "briefBand", "runDiff", "passRate", "fullEnvironment", "retries", "fullFailures", "stackTraces"];
 type SectionKey = (typeof SECTION_KEYS)[number];
 /** A partial map of section flags — used both as the flat baseline and per-template. */
 type SectionFlags = Partial<Record<SectionKey, boolean>>;
@@ -406,12 +406,18 @@ interface ReporterOptions {
      * every chosen template; per-template keys (`minimal` / `detailed` /
      * `executive`) override the baseline for that template only.
      *
+     * 20 keys total: 15 block toggles, 5 display modifiers.
+     *
      * Block toggles: `coverPage`, `analysisOneliner`, `releaseGate`, `summary`,
      * `charts`, `trend`, `requirementsMatrix`, `ciEnvironment`, `suiteBreakdown`,
-     * `failureDeepDive`, `failureAnalysis`, `slowTests`, `defectLog`, `briefBand`.
+     * `failureDeepDive`, `failureAnalysis`, `slowTests`, `defectLog`, `briefBand`,
+     * `runDiff`.
      * Display modifiers: `passRate`, `fullEnvironment`, `retries`, `fullFailures`,
      * `stackTraces`.
      *
+     * `runDiff` shows new failures, fixed tests, and still-failing tests against
+     * the previous run on the same branch; on by default in all three templates.
+     *
      * `trend` renders only when `charts` is also on and history data exists (`showTrend` enabled). Sections gated on data
      * (`failureAnalysis`, `requirementsMatrix`, `slowTests`, `defectLog`) appear
      * only when matching data exists — this option never changes data collection.

package/dist/index.d.ts

@@ -1,11 +1,11 @@
 import { Reporter, FullConfig, Suite, TestCase, TestResult, TestStep, FullResult } from '@playwright/test/reporter';
 
 /**
- * Canonical section catalog. 14 block toggles (section present/absent) followed
+ * Canonical section catalog. 15 block toggles (section present/absent) followed
  * by 5 display modifiers (tweak a section that is on). Single source of truth —
  * the Zod schema in src/config/schema.ts builds its flag shape from this array.
  */
-declare const SECTION_KEYS: readonly ["coverPage", "analysisOneliner", "releaseGate", "summary", "charts", "trend", "requirementsMatrix", "ciEnvironment", "suiteBreakdown", "failureDeepDive", "failureAnalysis", "slowTests", "defectLog", "briefBand", "passRate", "fullEnvironment", "retries", "fullFailures", "stackTraces"];
+declare const SECTION_KEYS: readonly ["coverPage", "analysisOneliner", "releaseGate", "summary", "charts", "trend", "requirementsMatrix", "ciEnvironment", "suiteBreakdown", "failureDeepDive", "failureAnalysis", "slowTests", "defectLog", "briefBand", "runDiff", "passRate", "fullEnvironment", "retries", "fullFailures", "stackTraces"];
 type SectionKey = (typeof SECTION_KEYS)[number];
 /** A partial map of section flags — used both as the flat baseline and per-template. */
 type SectionFlags = Partial<Record<SectionKey, boolean>>;
@@ -406,12 +406,18 @@ interface ReporterOptions {
      * every chosen template; per-template keys (`minimal` / `detailed` /
      * `executive`) override the baseline for that template only.
      *
+     * 20 keys total: 15 block toggles, 5 display modifiers.
+     *
      * Block toggles: `coverPage`, `analysisOneliner`, `releaseGate`, `summary`,
      * `charts`, `trend`, `requirementsMatrix`, `ciEnvironment`, `suiteBreakdown`,
-     * `failureDeepDive`, `failureAnalysis`, `slowTests`, `defectLog`, `briefBand`.
+     * `failureDeepDive`, `failureAnalysis`, `slowTests`, `defectLog`, `briefBand`,
+     * `runDiff`.
      * Display modifiers: `passRate`, `fullEnvironment`, `retries`, `fullFailures`,
      * `stackTraces`.
      *
+     * `runDiff` shows new failures, fixed tests, and still-failing tests against
+     * the previous run on the same branch; on by default in all three templates.
+     *
      * `trend` renders only when `charts` is also on and history data exists (`showTrend` enabled). Sections gated on data
      * (`failureAnalysis`, `requirementsMatrix`, `slowTests`, `defectLog`) appear
      * only when matching data exists — this option never changes data collection.