e2e-tester

Automate browser and end-to-end testing workflows with framework detection and artifact capture.

Updated May 6, 2026

Search Tags:#automation #testing #debugging #e2e #artifacts #fixtures

Ready to run

npx skills add https://github.com/htayj/src --skill e2e-tester-htayj

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e-tester
Source: https://github.com/htayj/src/tree/main/dotfiles/pi/.pi/agent/packages/general-dev-suite/skills/e2e-tester
Command: npx skills add https://github.com/htayj/src --skill e2e-tester-htayj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the process of creating, running, and debugging browser or end-to-end tests, reducing manual effort and enhancing test reliability.

Core Features & Use Cases

E2E Framework Detection: Identifies the testing tools in use within a project to facilitate tailored testing procedures.
Fixture and Page Object Reuse: Reuses existing test fixtures and page objects to save development time and maintain consistency.
Debugging Artifacts: Captures screenshots, logs, and other artifacts during test execution to assist debugging and review processes.
Use Case: A QA engineer running complex tests on a web application can leverage this skill to automate test setup, execution, and artifact collection for faster feedback.

Quick Start

Use the e2e-tester skill to detect your current testing framework and run your focused test specs, then collect debugging artifacts.

Frequently Asked Questions about e2e-tester

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

FAQPage Schema

How do I automate end-to-end browser testing and capture debugging artifacts?▼

Automating end-to-end browser testing and capturing debugging artifacts is achieved by detecting existing testing frameworks, reusing fixtures, and automatically collecting screenshots and logs during execution.

How does e2e testing framework detection work for reusing existing page objects?▼

E2e testing framework detection works by scanning your project to identify the active testing tools, enabling the targeted reuse of existing test fixtures and page objects to maintain consistency and save setup time.

Can I integrate this browser testing workflow with my existing test fixtures?▼

Yes, you can integrate this workflow with your existing test fixtures. The process specifically detects your current tools and reuses available page objects to ensure seamless integration within your development pipelines.

What is the best way to collect screenshots and logs during automated test execution?▼

The best way to collect screenshots and logs during automated test execution is to use an automated e2e workflow that captures these debugging artifacts natively during the test run for faster review and bug investigation.

Why should I use automated artifact collection in my QA and development pipelines?▼

Automated artifact collection in QA and development pipelines improves test reliability and accelerates bug investigation accuracy by systematically capturing debugging evidence like screenshots and logs without requiring manual effort.

Do I need specific dependencies to run focused end-to-end test specs?▼

No specific external dependencies are required to run focused end-to-end test specs. The workflow operates autonomously to detect your project's current testing frameworks and manage the execution and artifact collection process.