A highly customizable and extensible Playwright test reporter with interactive tree-grid reports, coverage analysis, and rich integrations.
Monocart Reporter is a customizable HTML reporter for Playwright Test that generates interactive, feature-rich test reports. It solves the problem of limited reporting in default Playwright reporters by providing a tree-grid interface, custom fields, code coverage integration, and extensible data collection.
Playwright users, QA engineers, and development teams who need detailed, customizable test reports for monitoring test execution, coverage, and performance in CI/CD pipelines.
Developers choose Monocart Reporter for its high degree of customization, performance with large datasets, and rich integrations like coverage reports, Lighthouse audits, and third-party tool hooks, which go beyond basic Playwright reporting.
A playwright test reporter (Node.js)
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Allows adding and styling custom fields like owner and JIRA keys directly in the report grid, with formatter functions for dynamic content, as detailed in the Custom Columns section.
Built-in support for generating and attaching V8 and Istanbul coverage reports, enabling seamless visualization of test coverage alongside results through the coverage options and APIs.
Supports multiple methods to collect custom metadata, including code comments, setMetadata() API, and custom visitor functions, making it flexible for various use cases like parsing titles or annotations.
Includes attachments for Lighthouse audits, network HAR files, Markdown, and Mermaid diagrams, enriching reports with performance data and visualizations, as shown in the Attach sections.
Setting up custom columns, hooks, global state, and coverage requires extensive configuration in Playwright config files, which can be time-consuming and error-prone for new users.
Exclusively designed for Playwright Test, so it cannot be used with other testing frameworks, limiting its applicability in mixed or non-Playwright environments.
Column formatter functions are serialized into strings via JSON, meaning closures and contexts do not work, restricting advanced dynamic formatting and requiring workarounds.