he-test

Orchestrate end-to-end tests across SPEC, DEV-TEST, BROWSER, and AUTO phases.

Updated Jul 23, 2025
One-click install
npx skills add https://github.com/data-players/Marker-OCR-API --skill he-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: he-test
Source: https://github.com/data-players/Marker-OCR-API/tree/main/.heracles/agents/skills/he-test
Command: npx skills add https://github.com/data-players/Marker-OCR-API --skill he-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to coordinate and automate diverse testing activities across specification writing, development testing, browser-based validation, and automated CI processes. This skill provides a structured workflow to define tests up front, implement tests in phases, and validate software across multiple layers with consistent reporting.

Core Features & Use Cases

  • TDD-driven test spec creation before implementation to guide development.
  • Automated unit, integration, and E2E tests coordinated across DEV-TEST, TEST-SPEC, and TEST-AUTO phases.
  • Browser-based validation using Playwright with progress tracking and coverage reporting for CI pipelines.
  • Seamless handoff between phases with clear prerequisites and outputs to accelerate delivery.

Quick Start

Define your SPECs and feature tests in WORKFLOW_STATE.md and let the agent generate skeleton tests across all phases.

Frequently Asked Questions about he-test

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

FAQPage Schema
How do I orchestrate end-to-end tests with Playwright across CI/CD pipelines?

You orchestrate end-to-end tests by coordinating browser-based validation across SPEC, DEV-TEST, BROWSER, and AUTO phases. This structured workflow integrates Playwright with CI pipelines to provide automated browser checks, clear progress tracking, and coverage reporting.

What is the best way to coordinate TDD spec writing with automated browser validation?

The best way to coordinate TDD spec writing with automated browser validation is using a phased workflow. It defines test specs upfront, implements development tests, performs browser checks with Playwright, and automates CI processes with consistent reporting.

Can I use Vitest for test automation alongside Playwright in a TDD workflow?

Yes, you can use Vitest for test automation alongside Playwright. The workflow integrates both frameworks to satisfy requirements for multiple test types, coordinating unit, integration, and E2E tests across distinct project phases.

How do I start generating skeleton tests for multiple testing phases?

To start generating skeleton tests, define your SPECs and feature tests in WORKFLOW_STATE.md. The agent then generates skeleton tests across all phases, ensuring seamless handoff with clear prerequisites and outputs to accelerate delivery.

Does this approach support tracking test coverage and progress for CI pipelines?

Yes, this approach supports tracking test coverage and progress for CI pipelines. It provides browser-based validation using Playwright with built-in progress tracking and coverage reporting across the automated testing phases.

When should I use a phased E2E testing workflow instead of standalone test scripts?

Use a phased E2E testing workflow when your team needs to coordinate diverse testing activities across specification, development, browser validation, and automation. It solves coordination struggles by defining tests upfront and ensuring seamless handoff between phases.