E2E Testing

Automate Playwright-based end-to-end testing workflows for UI verification before CI.

455|69|Updated Apr 3, 2024
One-click install
npx skills add https://github.com/iota-uz/iota-sdk --skill e2e-testing-iota-uz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: E2E Testing
Source: https://github.com/iota-uz/iota-sdk/tree/main/.claude/skills/e2e-testing
Command: npx skills add https://github.com/iota-uz/iota-sdk --skill e2e-testing-iota-uz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers run and debug Playwright-based E2E tests locally, making it easier to catch UI regressions before pushing changes.

Core Features & Use Cases

  • Local test execution: Run Playwright tests against a local ERP UI to validate end-to-end flows.
  • Debugging tooling: Access detailed logs, traces, and screenshots to diagnose failures quickly.
  • Test maintenance: Guidance for updating and seeding test data, re-running specific tests, and integrating with CI.

Quick Start

Run the entire end-to-end test suite locally to validate changes.

Frequently Asked Questions about E2E Testing

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

FAQPage Schema
How do I debug Playwright E2E tests locally?

You can debug Playwright E2E tests locally by accessing detailed logs, traces, and screenshots to diagnose failures quickly. This approach helps catch UI regressions before pushing changes to CI.

What is the best way to run Playwright tests against a local server environment?

The best way to run Playwright tests locally is to execute the end-to-end test suite against your running test environment. This requires a local Node.js toolchain and access to test data to validate changes.

Do I need a specific toolchain to run end-to-end testing for web UI?

Yes, you need a local Node.js toolchain, a running test environment, and access to test data to perform end-to-end testing. These prerequisites allow you to verify server endpoints and UI interactions locally.

Can I use Playwright to test authentication flows and ERP UI interactions?

Yes, Playwright can test authentication flows and ERP UI interactions locally. The testing workflow applies to feature branches and debugging sessions to verify end-to-end changes before CI integration.

How do I maintain test data for automated E2E testing in CI?

You can maintain test data for automated E2E testing by using guidance for updating and seeding test data. This allows you to re-run specific tests and integrate smoothly with your CI pipeline.

Why run E2E tests on a feature branch before pushing to CI?

Running E2E tests on a feature branch before CI helps catch UI regressions early in local development. This reduces CI failures by validating server endpoints and UI interactions before changes are pushed.