e2e-testing

Create and review Playwright end-to-end tests for Langflow's frontend UI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bayazknn/elciai-platform-analysis --skill e2e-testing-bayazknn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/bayazknn/elciai-platform-analysis/tree/main/langflow/.agents/skills/e2e-testing
Command: npx skills add https://github.com/bayazknn/elciai-platform-analysis --skill e2e-testing-bayazknn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams write, fix, and review end-to-end Playwright tests to catch regressions and ensure Langflow's full UI flows work reliably across releases and CI environments.

Core Features & Use Cases

  • E2E test authoring and review: Guidance for writing Playwright .spec.ts tests that exercise complete user flows and templates.
  • Flakiness mitigation and debugging: Recommendations for timeouts, retries, tracing, and using custom fixtures that detect API and flow execution errors.
  • Test hygiene and CI integration: Enforces tagging, selector strategies (data-testid), helper utilities in src/frontend/tests/utils, and Playwright configuration for parallelism and reporting.
  • Use Case: Add or fix a failing run-flow.spec.ts test after a UI change to data-testid attributes or update test helpers to restore CI stability.

Quick Start

Write or update a Playwright E2E test that exercises the full UI flow, imports helpers from src/frontend/tests/fixtures, includes appropriate tags like @release and @workspace, and runs with the repository's Playwright configuration.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I write reliable Playwright E2E tests for Langflow UI flows?

Playwright E2E tests for Langflow use custom fixtures from src/frontend/tests/fixtures.ts that automatically detect API errors, require data-testid attributes for selectors, and apply tags like @release and @workspace for CI filtering.

What is the best way to fix flaky Playwright UI tests in CI?

Fix flaky Playwright UI tests by configuring retries, enabling tracing, and using custom test fixtures in src/frontend/tests/fixtures.ts that automatically detect API and flow execution errors to surface hidden failures.

Does this Playwright testing setup require a specific version or browser?

Yes, this Playwright testing setup requires Playwright 1..57.0 specifically configured with the Chromium browser, alongside custom test fixtures and standardized helper utilities located in src/frontend/tests/utils.

Why do my Playwright tests fail after updating data-testid attributes in the frontend?

Playwright tests fail after data-testid updates because E2E spec files reference these attributes as selectors; you must update the corresponding test selectors in .spec.ts files and helper utilities to restore test stability.

How do I organize Playwright test helpers and fixtures for tag-based CI filtering?

Organize Playwright test helpers in src/frontend/tests/utils and custom fixtures in src/frontend/tests/fixtures.ts, applying tags like @release and @workspace in .spec.ts files to enable tag-based CI filtering and parallel execution.