Why use PM2 for Playwright reports?

PM2 keeps report servers and trace viewers running in the background persistently after tests finish, providing easy access via stable or dynamic URLs without blocking your terminal.

Can I manage multiple test services at once?

Yes, the skill supports PM2 ecosystem files to orchestrate multiple services, such as running the report server and trace viewer simultaneously on different ports.

How do I view the test service logs?

You can use standard PM2 log commands or specific skill triggers to stream or fetch the last 50 lines of logs to troubleshoot server startup or access issues.

Does this skill work with GitHub Codespaces?

Yes, it includes specific logic to generate accessible preview URLs for Codespaces, Coder, and other remote development environments where port forwarding is required.

PM2 Playwright Test Services

Name: PM2 Playwright Test Services
Author: jovermier

byjovermier

Security & Testing

Automates the management of PM2 processes for serving Playwright test reports and trace viewers in development environments.

About

This skill streamlines the testing workflow by utilizing PM2 to manage persistent background services for Playwright artifacts. It allows developers to easily start, stop, and monitor report servers and trace viewers, while also providing advanced capabilities for generating dynamic workspace URLs in cloud IDEs like Coder or GitHub Codespaces. Whether troubleshooting failed tests or sharing reports, this skill ensures test data is always accessible and services are properly managed without manual process configuration.

Key Features

Real-time log streaming and monitoring for test-related processes
Automated PM2 service lifecycle management for Playwright reports
Simplified troubleshooting with port conflict detection and health checks
Support for PM2 ecosystem configurations and custom test scripts
Dynamic URL generation for cloud environments like Coder and Codespaces
0 GitHub stars

Use Cases

Running the Playwright Trace Viewer in the background to debug failures
Managing multiple test-related microservices in remote workspace environments
Serving persistent Playwright HTML reports after test execution

About

Key Features

Real-time log streaming and monitoring for test-related processes
Automated PM2 service lifecycle management for Playwright reports
Simplified troubleshooting with port conflict detection and health checks
Support for PM2 ecosystem configurations and custom test scripts
Dynamic URL generation for cloud environments like Coder and Codespaces
0 GitHub stars

Use Cases

Running the Playwright Trace Viewer in the background to debug failures
Managing multiple test-related microservices in remote workspace environments
Serving persistent Playwright HTML reports after test execution