skills.rest
Intellifill
IntellifillOFFICIAL
Explore all skills by this author →
WebsiteGitHub

e2e-testing

Coordinate end-to-end testing for IntelliFill across Cypress and Playwright.

1|Updated Aug 8, 2025
Search Tags:#automation#playwright#cypress#ci-cd#e2e-testing#test-patterns
One-click install
npx skills add https://github.com/Intellifill/IntelliFill --skill e2e-testing-intellifill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/Intellifill/IntelliFill/tree/main/.claude/skills/e2e-testing
Command: npx skills add https://github.com/Intellifill/IntelliFill --skill e2e-testing-intellifill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end testing for IntelliFill is often time-consuming and flaky without a structured approach. This Skill provides a comprehensive, ready-to-use blueprint for writing end-to-end tests using Cypress and Playwright, accelerating QA and CI workflows.

Core Features & Use Cases

  • Dual framework support: Cypress for interactive development and Playwright for CI/CD, cross-browser coverage, and headless execution.
  • Predefined test patterns and example suites: authentication, documents, templates, and API checks.
  • CI/CD friendly: configuration samples, Docker-based runs, and parity between local development and CI environments.
  • Custom commands and fixtures: reusable actions to speed up test authoring and data setup.

Quick Start

Run the end-to-end test suite for IntelliFill locally with npm run test:e2e or npm run cypress:open, and in CI with docker-compose.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I structure end-to-end tests using Cypress and Playwright together?▼

Structuring end-to-end tests with Cypress and Playwright involves using Cypress for interactive development and Playwright for CI/CD. This dual framework approach streamlines QA workflows and cross-browser coverage.

What's the best way to manage authentication and fixtures in E2E testing?▼

The best way to manage authentication and fixtures in E2E testing is by using predefined test patterns and custom commands. Reusable actions speed up test authoring and data setup.

Can I run E2E tests in Docker and maintain local CI parity?▼

Yes, you can run E2E tests in Docker and maintain local CI parity. Configuration samples and Docker-based runs ensure environment parity between local development and CI.

Does this E2E testing approach include patterns for API checks and documents?▼

Yes, this E2E testing approach includes patterns for API checks and documents. Predefined test suites cover authentication, documents, templates, and API checks.

Why use Playwright over Cypress for cross-browser test coverage?▼

Use Playwright over Cypress for cross-browser test coverage because Playwright supports CI/CD, cross-browser coverage, and headless execution, while Cypress is better suited for interactive development.

How do I configure environments for CI integration with npm and Docker?▼

You configure environments for CI integration by using standard npm tooling and Docker. This satisfies requirements for framework orchestration, fixture management, and environment configuration.

Related Skills

Explore More Software Engineering Skills→
mikemikulamikemikula
2

docker-dev-setup

Configure Docker Compose with Postgres 17, Redis 8, and environment variables.

Community
Intermediate
JaiminVadadoriyaJaiminVadadoriya
1

qa-dashboard

Generate test reports and dashboards with Allure, Grafana, and ReportPortal.

Community
Advanced
MatrixFounderMatrixFounder
4

testing-best-practices

Provide guidelines for implementing maintainable software tests across testing hierarchies.

Community
Intermediate
dglijin-ossdglijin-oss
10

browser-use

Automate browser navigation, form filling, screenshots, and data extraction.

Community
Advanced