cbplaywright

Write end-to-end browser tests for ColdBox applications using cbplaywright.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ColdBox/skills --skill cbplaywright
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cbplaywright
Source: https://github.com/ColdBox/skills/tree/main/modules/cbplaywright
Command: npx skills add https://github.com/ColdBox/skills --skill cbplaywright

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ColdBox end-to-end browser tests require consistent browser lifecycle management, robust selectors, network mocking, and CI-friendly configuration; cbplaywright consolidates patterns and APIs to reduce flaky tests and boilerplate so teams can confidently validate UI flows.

Core Features & Use Cases

  • Test bundle setup and lifecycle integration for BoxLang and ColdBox E2E specs.
  • Navigation, waiting strategies, resilient selectors, form interactions, assertions, screenshots, traces, and network interception for isolating external APIs.
  • Page Object pattern examples and CI recommendations to structure maintainable, scalable test suites and run headless in pipelines.

Quick Start

Use the cbplaywright skill to scaffold and run a headless Playwright E2E test that navigates to /login, fills credentials, and asserts a successful login.

Frequently Asked Questions about cbplaywright

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write end-to-end browser tests for a ColdBox application?

You can write end-to-end browser tests for ColdBox by using the cbplaywright Playwright wrapper to handle navigation, form interactions, assertions, and browser lifecycle management. It provides patterns to reduce flaky tests and boilerplate for validating UI flows.

Can I run headless Playwright E2E tests in a CI pipeline for BoxLang?

Yes, you can run headless Playwright E2E tests in CI pipelines for BoxLang. The cbplaywright wrapper includes CI recommendations and controls the browser page lifecycle to ensure tests run reliably in automated environments.

How do I use Page Object patterns to structure maintainable ColdBox test suites?

You structure maintainable ColdBox test suites by applying Page Object pattern examples provided by the cbplaywright wrapper. This organizes selectors and form interactions into scalable modules, reducing boilerplate and improving test reliability.

Does cbplaywright support network interception for isolating external APIs during E2E testing?

Yes, cbplaywright supports network interception for isolating external APIs during E2E testing. It allows you to mock network requests within your ColdBox and BoxLang specs to prevent external dependencies from causing flaky tests.

What do I need to set up before running Playwright browser tests for ColdBox?

Before running Playwright browser tests, you need the cbplaywright module installed and Playwright browsers downloaded. You also need to configure the test bundle setup and lifecycle integration for your ColdBox or BoxLang environment.

How do I capture screenshots and traces when a Playwright E2E test fails in ColdBox?

You capture screenshots and traces in failing ColdBox tests by utilizing the built-in screenshot and trace features of the cbplaywright wrapper. These are integrated into the test lifecycle to help debug resilient selectors and waiting strategies.