playwright-e2e-tests

Write and maintain Playwright E2E tests for the Onyx application.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/meethelio/Cortex --skill playwright-e2e-tests-meethelio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-e2e-tests
Source: https://github.com/meethelio/Cortex/tree/main/.cursor/skills/playwright
Command: npx skills add https://github.com/meethelio/Cortex --skill playwright-e2e-tests-meethelio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation, debugging, and maintenance of end-to-end (E2E) tests for the Onyx application, ensuring robust and reliable user experiences.

Core Features & Use Cases

  • E2E Test Development: Write new E2E tests for various application features.
  • Debugging Test Failures: Analyze and fix issues causing E2E tests to fail.
  • Test Coverage Enhancement: Add new tests to improve the overall test coverage of the application.
  • Use Case: When a new chat feature is developed, use this Skill to write comprehensive Playwright E2E tests that cover user interactions, message sending, and AI responses.

Quick Start

Use the playwright skill to write a new E2E test for the user authentication flow.

Frequently Asked Questions about playwright-e2e-tests

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

FAQPage Schema
How do I write Playwright E2E tests for application features like chat and authentication?

Playwright E2E tests are automated end-to-end tests that validate user experiences across application features like authentication, chat, and administration. They ensure robust application behavior by simulating real user interactions and verifying AI responses function correctly.

How do I debug failing Playwright tests in my web testing workflow?

Playwright E2E tests require specific test projects for administration and exclusive features. These projects organize test execution by using API-based authentication and absolute imports, ensuring tests run in isolated environments for efficient and reliable feature validation.

How do I add E2E test coverage for new web application features using Playwright?

Adding E2E test coverage involves writing new Playwright tests that validate user interactions and feature behaviors. This Skill enhances coverage by generating comprehensive tests for features like chat, assistants, connectors, and MCP using absolute imports and API-based authentication.

Why do my Playwright E2E tests fail when running across different test projects?

Playwright E2E tests may fail across different test projects due to authentication or isolation issues. This Skill addresses these failures by utilizing API-based authentication and absolute imports within specific test projects like admin and exclusive to maintain test isolation.