testing-workflow

Run TypeScript checks, production builds, and browser health checks for octaneWebR projects.

1|Updated Jul 9, 2025
One-click install
npx skills add https://github.com/ultrafish22L/grpcSamples --skill testing-workflow-ultrafish22l
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-workflow
Source: https://github.com/ultrafish22L/grpcSamples/tree/main/octaneWebR/.openhands/skills/testing-workflow
Command: npx skills add https://github.com/ultrafish22L/grpcSamples --skill testing-workflow-ultrafish22l

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a complete, repeatable development and testing workflow for octaneWebR projects, including server management, debugging techniques, and visual debugging strategies, reducing manual setup and common errors during builds and deployments.

Core Features & Use Cases

  • Proven development and testing routine for stopping running servers, TypeScript checks, building production bundles, starting development servers, health checks, and browser validation.
  • Deterministic troubleshooting with structured steps for diagnosing build, type, and runtime issues.
  • Rapid validation of changes in CI-like workflows before merges or deployments.

Quick Start

  • Stop Running Servers: Kill processes on development ports (57341, 49019) if any are active.
  • TypeScript Type Check: From the project root, run npx tsc --noEmit to verify types without emitting files.
  • Build Production Bundle: Run npm run build to create the production assets.
  • Start Development Server: Run npm run dev (optionally in background) and verify the server starts correctly.
  • Health Check & Verification: Query http://localhost:57341/api/health to ensure status is ok and Octane is connected.

Frequently Asked Questions about testing-workflow

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

FAQPage Schema
How do I set up a complete testing and debugging workflow for TypeScript projects?

A complete testing and debugging workflow for TypeScript projects involves stopping running servers, running type checks with npx tsc --noEmit, building production bundles, starting development servers, and performing health checks. This standardized routine minimizes manual setup and common build errors.

How do I diagnose TypeScript build and runtime errors during local development?

To diagnose TypeScript build and runtime errors, use structured troubleshooting steps: verify types without emitting files, build production assets, start the server, and query the API health endpoint. This deterministic process isolates build, type, and runtime issues quickly.

What's the best way to validate production builds before deployment in a CI-like workflow?

The best way to validate production builds before deployment is to run npm run build to create assets, start the development server, and verify server health via an API endpoint. This rapid validation routine ensures features work correctly before merges or deployments.

Do I need external libraries to manage development servers and run health checks?

No external libraries are needed to manage development servers and run health checks. The workflow relies entirely on standard tooling including bash, npm, and node-based utilities to kill processes, build bundles, and verify server status.

Why should I kill processes on development ports before starting a TypeScript build workflow?

You should kill processes on development ports like 57341 and 49019 before starting a TypeScript build workflow to prevent port conflicts. Stopping running servers ensures the production bundle builds correctly and the new development server starts without errors.

How do I verify my development server is connected and running correctly?

To verify your development server is running correctly, query the http://localhost:57341/api/health endpoint. This health check confirms the server status is ok and Octane is connected, ensuring your local environment is fully operational.