@arghajit/dummy 0.1.0-beta-16 → 0.1.0-beta-18
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +49 -1
- package/dist/reporter/playwright-pulse-reporter.js +16 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -55,6 +55,21 @@ _The ultimate Playwright reporter — Interactive dashboard with historical tren
|
|
|
55
55
|
|
|
56
56
|
[](https://ocpaxmghzmfbuhxzxzae.supabase.co/storage/v1/object/public/images//pulse-email-summary.html.png)
|
|
57
57
|
|
|
58
|
+
## Available Scripts
|
|
59
|
+
|
|
60
|
+
The project provides these utility commands:
|
|
61
|
+
|
|
62
|
+
| Command | Description |
|
|
63
|
+
|------------------------|-----------------------------------------------------------------------------|
|
|
64
|
+
| `generate-report` | Generates playwright-pulse-report.html, Loads screenshots and images dynamically from the attachments/ directory, Produces a lighter HTML file with faster initial load, Requires attachments/ directory to be present when viewing the report |
|
|
65
|
+
| `generate-pulse-report`| Generates `playwright-pulse-static-report.html`, Self-contained, no server required, Preserves all dashboard functionality |
|
|
66
|
+
| `merge-pulse-report` | Combines multiple parallel test json reports, basically used in sharding |
|
|
67
|
+
| `generate-trend` | Analyzes historical trends in test results |
|
|
68
|
+
| `generate-email-report`| Generates email-friendly report versions |
|
|
69
|
+
| `send-email` | Generates email-friendly report versions & Distributes report via email |
|
|
70
|
+
|
|
71
|
+
Run with `npm run <command>`
|
|
72
|
+
|
|
58
73
|
## 🛠️ How It Works
|
|
59
74
|
|
|
60
75
|
1. **Reporter Collection**:
|
|
@@ -260,6 +275,39 @@ The dashboard includes AI-powered test analysis that provides:
|
|
|
260
275
|
npm install @arghajit/playwright-pulse-report@latest
|
|
261
276
|
```
|
|
262
277
|
|
|
278
|
+
---
|
|
279
|
+
|
|
280
|
+
<img src="https://ocpaxmghzmfbuhxzxzae.supabase.co/storage/v1/object/public/images//pulse-logo.png" alt="pulse dashboard" title="pulse dashboard" height="50px" width="80px" align="left" padding="10px"/>
|
|
281
|
+
<h2>Pulse Dashboard</h2>
|
|
282
|
+
|
|
283
|
+
**Real-time Playwright Test Monitoring & Analysis**
|
|
284
|
+
|
|
285
|
+
A Next.js component & CLI tool for visualizing Playwright test executions. Provides real-time insights, historical trends, and failure analysis.
|
|
286
|
+
|
|
287
|
+
**Key Features**:
|
|
288
|
+
|
|
289
|
+
- Interactive test result visualization
|
|
290
|
+
- Historical trend analysis
|
|
291
|
+
- Failure pattern identification
|
|
292
|
+
|
|
293
|
+
**Quick Start**:
|
|
294
|
+
|
|
295
|
+
```bash
|
|
296
|
+
npx pulse-dashboard
|
|
297
|
+
or,
|
|
298
|
+
npm run pulse-dashboard
|
|
299
|
+
```
|
|
300
|
+
|
|
301
|
+
*(Run from project root containing `pulse-report/` directory)*
|
|
302
|
+
|
|
303
|
+
**NPM Package**: [pulse-dashboard on npm](https://www.npmjs.com/package/pulse-dashboard)
|
|
304
|
+
|
|
305
|
+
**Tech Stack**: Next.js, TypeScript, Tailwind CSS, Playwright
|
|
306
|
+
|
|
307
|
+
*Part of the Playwright Pulse Report ecosystem*
|
|
308
|
+
|
|
309
|
+
---
|
|
310
|
+
|
|
263
311
|
## 📬 Support
|
|
264
312
|
|
|
265
313
|
For issues or feature requests, please [Contact Me](mailto:arghajitsingha47@gmail.com).
|
|
@@ -268,7 +316,7 @@ For issues or feature requests, please [Contact Me](mailto:arghajitsingha47@gmai
|
|
|
268
316
|
|
|
269
317
|
## 🙌🏼 Thank you
|
|
270
318
|
|
|
271
|
-
Special Thanks to [@
|
|
319
|
+
Special Thanks to [@Suman Vishwakarma](https://www.linkedin.com/in/suman-vishwakarma-426108185/), for continuous UAT feedback.
|
|
272
320
|
|
|
273
321
|
---
|
|
274
322
|
|
|
@@ -247,14 +247,24 @@ class PlaywrightPulseReporter {
|
|
|
247
247
|
const uniqueTestId = test.id;
|
|
248
248
|
// --- REFINED THIS SECTION for testData ---
|
|
249
249
|
const maxWorkers = this.config.workers;
|
|
250
|
-
|
|
251
|
-
//
|
|
252
|
-
|
|
253
|
-
|
|
254
|
-
|
|
255
|
-
|
|
250
|
+
let mappedWorkerId;
|
|
251
|
+
// First, check for the special case where a test is not assigned a worker (e.g., global setup failure).
|
|
252
|
+
if (result.workerIndex === -1) {
|
|
253
|
+
mappedWorkerId = -1; // Keep it as -1 to clearly identify this special case.
|
|
254
|
+
}
|
|
255
|
+
else if (maxWorkers && maxWorkers > 0) {
|
|
256
|
+
// If there's a valid worker, map it to the concurrency slot...
|
|
257
|
+
const zeroBasedId = result.workerIndex % maxWorkers;
|
|
258
|
+
// ...and then shift it to be 1-based (1 to n).
|
|
259
|
+
mappedWorkerId = zeroBasedId + 1;
|
|
260
|
+
}
|
|
261
|
+
else {
|
|
262
|
+
// Fallback for when maxWorkers is not defined: just use the original index (and shift to 1-based).
|
|
263
|
+
mappedWorkerId = result.workerIndex + 1;
|
|
264
|
+
}
|
|
256
265
|
const testSpecificData = {
|
|
257
266
|
workerId: mappedWorkerId,
|
|
267
|
+
uniqueWorkerIndex: result.workerIndex, // We'll keep the original for diagnostics
|
|
258
268
|
totalWorkers: maxWorkers,
|
|
259
269
|
configFile: this.config.configFile,
|
|
260
270
|
metadata: this.config.metadata
|
package/package.json
CHANGED