test-execution

Execute and validate unit, integration, and end-to-end tests.

5|1|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/Disaster-Terminator/RewardsCore --skill test-execution-disaster-terminator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-execution
Source: https://github.com/Disaster-Terminator/RewardsCore/tree/main/.trae/archive/multi-agent/skills/test-execution
Command: npx skills add https://github.com/Disaster-Terminator/RewardsCore --skill test-execution-disaster-terminator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured and robust process for executing and validating tests, ensuring code quality and identifying issues early in the development cycle.

Core Features & Use Cases

  • Automated Testing: Executes unit, integration, and end-to-end tests.
  • Environment Diagnosis: Verifies the testing environment and dependencies.
  • Error Attribution: Precisely identifies the root cause of test failures (environment vs. code logic).
  • Forensic Evidence Collection: Gathers detailed logs, screenshots, and DOM snapshots upon failure.
  • Use Case: When a new feature is developed, this Skill can be invoked to run all relevant tests, report success or failure, and provide detailed diagnostics if any test fails, enabling rapid debugging.

Quick Start

Execute the test-execution skill to run all tests and report the findings.

Frequently Asked Questions about test-execution

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

FAQPage Schema
How do I automate test execution and collect forensic evidence on failure?

Automating test execution runs unit, integration, and end-to-end tests while gathering forensic evidence like tracebacks, accessibility trees, and network requests upon failure to streamline debugging.

What is the best way to diagnose environmental issues during automated testing?

Diagnosing environmental issues during automated testing involves verifying the testing environment and dependencies to precisely attribute test failures to environmental configuration rather than code logic.

How do I identify if a test failure is caused by code logic or configuration?

Identifying the root cause of test failures requires error attribution, which analyzes environmental diagnosis and forensic evidence like tracebacks to distinguish between code logic faults and configuration issues.

How do I validate unit and end-to-end tests in a CI/CD pipeline?

Validating unit and end-to-end tests in a CI/CD pipeline automates execution to report success or failure, providing detailed diagnostics and DOM snapshots to enable rapid debugging and maintain code quality.

What forensic data do I need to capture when a software test fails?

Capturing forensic data when a software test fails involves collecting detailed logs, screenshots, DOM snapshots, accessibility trees, and network requests to provide comprehensive diagnostics for rapid debugging.