@testrelic/playwright-analytics 2.3.10 → 2.3.11

package/README.md

@@ -359,6 +359,23 @@ Each navigation in the timeline includes detailed network statistics:
 
 Disable with `includeNetworkStats: false`.
 
+## Viewing Reports
+
+For **small test suites** (< 50 tests), the report is a self-contained HTML file — just open it in your browser.
+
+For **large test suites** (50+ tests), TestRelic uses streaming mode to avoid memory issues. Test details are stored as separate files and loaded on demand via a local server. After tests complete, the terminal shows:
+
+```
+[testrelic] View report: npx testrelic serve ./test-results/.testrelic-report
+```
+
+Run that command and open `http://127.0.0.1:9323` in your browser. The server auto-starts after test runs when not in CI, but if you need to restart it later:
+
+```bash
+npx testrelic serve ./test-results/.testrelic-report
+npx testrelic serve ./test-results/.testrelic-report --port 9400  # custom port
+```
+
 ## Merging Shard Reports
 
 When running Playwright with sharding, each shard produces its own report. Merge them with the CLI:
@@ -415,6 +432,31 @@ test('CRUD operations', { tag: ['@api'] }, async ({ request }) => {
 });
 ```
 
+### Custom Page Fixtures (authenticated pages, etc.)
+
+If your tests create pages manually via `browser.newContext()` / `context.newPage()` (e.g., for auth with `storageState`), the built-in `page` fixture is bypassed and **no network/console/navigation data is captured**. Use `trackPage()` to enable tracking on any manually-created page:
+
+```typescript
+import { test as base, expect, trackPage } from '@testrelic/playwright-analytics/fixture';
+
+type MyFixtures = {
+  authenticatedPage: Page;
+};
+
+export const test = base.extend<MyFixtures>({
+  authenticatedPage: async ({ browser }, use, testInfo) => {
+    const ctx = await browser.newContext({ storageState: 'auth.json' });
+    const page = await ctx.newPage();
+    const cleanup = await trackPage(page, testInfo); // ← enables tracking
+    await use(page);
+    await cleanup(); // ← flushes data to report
+    await ctx.close();
+  },
+});
+```
+
+> **Important:** Without `trackPage()`, custom page fixtures will only show screenshots, videos, and action steps — but no network requests, console logs, or navigation timeline.
+
 ### Unified Testing (Browser + API)
 
 Use the unified fixture which provides **both** `page` and `request` — the TestRelic report shows navigation timeline AND API call details for the same test. This is ideal for:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@testrelic/playwright-analytics",
-  "version": "2.3.10",
+  "version": "2.3.11",
   "description": "Playwright test analytics reporter with E2E navigation tracking, API call capture, network stats, failure diagnostics, and interactive HTML reports",
   "keywords": [
     "playwright",
@@ -81,7 +81,7 @@
     "@playwright/test": ">=1.35.0"
   },
   "dependencies": {
-    "@testrelic/core": "2.3.10"
+    "@testrelic/core": "2.3.11"
   },
   "devDependencies": {
     "@playwright/test": "^1.35.0",