skills.rest
Kuba312
Kuba312COMMUNITY
Explore all skills by this author →
GitHub

10x-e2e

Execute browser-level E2E test phases for identified application risks.

Updated Jun 9, 2024
Search Tags:#test automation#risk management#e2e testing#browser testing#application testing
One-click install
npx skills add https://github.com/Kuba312/daily-board --skill 10x-e2e-kuba312
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 10x-e2e
Source: https://github.com/Kuba312/daily-board/tree/main/frontend/.agents/skills/10x-e2e
Command: npx skills add https://github.com/Kuba312/daily-board --skill 10x-e2e-kuba312

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures thorough browser-level testing of applications by driving end-to-end (E2E) test phases for each risk, providing a comprehensive yet focused approach to application testing.

Core Features & Use Cases

  • Risk-Driven E2E Testing: Automates the execution of E2E test phases for each identified risk in the application.
  • Phase-Based Execution: Executes the PLAN → GENERATE → REVIEW → VERIFY cycle for each risk, ensuring all aspects are tested.
  • Integration with Other Skills: Integrates with skills like /10x-implement and /10x-tdd for a seamless testing workflow.

Quick Start

Run /10x-e2e <change-id> [phase N] to start executing E2E test phases for a specific change and phase.

Frequently Asked Questions about 10x-e2e

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

FAQPage Schema
How do I automate browser-level E2E testing for specific application risks?▼

You can automate risk-driven E2E testing by running phased execution cycles that plan, generate, review, and verify browser tests for each identified application risk individually.

What is risk-driven E2E testing and how does it improve application test coverage?▼

Risk-driven E2E testing is an approach that isolates individual application risks and executes dedicated browser test phases for each one. This focused method prevents overlooked scenarios and ensures thorough end-to-end validation.

Do I need Playwright configured to run automated E2E test phases?▼

Yes, Playwright is a required dependency. You must have a running application environment with Playwright and its related configurations properly set up before executing the E2E test phases.

What's the best way to structure end-to-end test execution for thorough validation?▼

The best way to structure end-to-end test execution is through a four-phase cycle: PLAN, GENERATE, REVIEW, and VERIFY. Running this sequence for each application risk guarantees a comprehensive and focused testing workflow.

How do I start executing E2E test phases for a specific application change?▼

To start executing E2E test phases for a specific application change, run the command with the target change ID and optional phase number. This initiates the risk-driven PLAN, GENERATE, REVIEW, and VERIFY testing cycle.

Can I integrate E2E testing with existing test-driven development workflows?▼

Yes, E2E testing can integrate with existing test-driven development workflows. It coordinates seamlessly with implementation and TDD skills to provide continuous, risk-focused validation throughout the application development lifecycle.

Related Skills

Explore More Software Engineering Skills→
PixelSculptorPixelSculptor

10x-e2e

Automate end-to-end browser tests for application risk coverage using Playwright.

Community
Advanced
VectorInstituteVectorInstitute

fix-test-failures

Diagnose test failures from dependency updates and apply targeted fixes.

Official
Advanced
abudhahirabudhahir

dev-tdd

Enforce the RED-GREEN-REFACTOR cycle for unit and E2E testing.

Community
Advanced
imyousufimyousuf
12

atr-behavior

Execute natural language browser behavior tests from .test.txt files.

Community
Intermediate