run-tests

Name: run-tests
Availability: InStock
Author: Valynt

Automate test execution, coverage reporting, and CI validation with Vitest and Playwright.

Updated Nov 17, 2025

Search Tags:#automation #vitest #testing #playwright #coverage #test #ci

Ready to run

npx skills add https://github.com/Valynt/ValueOS --skill run-tests-valynt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: run-tests
Source: https://github.com/Valynt/ValueOS/tree/main/.windsurf/skills/run-tests
Command: npx skills add https://github.com/Valynt/ValueOS --skill run-tests-valynt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes test execution, coverage reporting, and CI validation across the codebase, reducing manual setup and ensuring consistent quality signals.

Core Features & Use Cases

Centralized test orchestration for unit, integration, and end-to-end tests using Vitest, Playwright, and related tooling.
Automatic coverage enforcement with predefined thresholds and per-package reporting to guide releases.
CI integration and pipeline validation to catch regressions before merging.

Quick Start

Run the full test suite locally with pnpm test and generate coverage reports with pnpm test:coverage.

Frequently Asked Questions about run-tests

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

FAQPage Schema

How do I automate test execution and coverage reporting across Vitest and Playwright?▼

You can automate test execution and coverage reporting by orchestrating Vitest and Playwright through a centralized workflow that enforces predefined coverage thresholds and generates per-package artifacts. This standardizes quality signals across local, CI, and release environments.

What's the best way to enforce coverage thresholds in a CI pipeline?▼

Enforcing coverage thresholds in a CI pipeline requires automated validation against predefined limits during test runs. This Skill applies threshold checks across unit, integration, and end-to-end workflows to catch regressions and block merges before release validation.

Can I unify unit, integration, and end-to-end test workflows without manual setup?▼

Unifying unit, integration, and end-to-end test workflows is possible by centralizing test orchestration with Vitest and Playwright. This eliminates manual setup and ensures consistent test runs and artifact generation across local development and CI pipelines.

Does CI validation support both local development and release test runs?▼

CI validation supports local development, CI pipelines, and release validation by applying standardized test execution. It generates consistent coverage reports and validates regressions across all environments using Vitest, Playwright, and related CI tooling.

How do I generate per-package coverage reports to guide releases?▼

Generating per-package coverage reports to guide releases involves running the full test suite with coverage enabled. This automates per-package reporting and enforces predefined thresholds to ensure codebase quality before merging or releasing.

Why standardize test runs instead of using separate configurations?▼

Standardizing test runs reduces manual setup and ensures consistent quality signals across the codebase. Centralized orchestration for Vitest and Playwright prevents configuration drift and catches regressions uniformly during CI validation.