testing

Automate Go test workflows from running tests to publishing results.

1|Updated Dec 2, 2023
One-click install
npx skills add https://github.com/tinywasm/devflow --skill testing-tinywasm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/tinywasm/devflow/tree/main/skills/testing
Command: npx skills add https://github.com/tinywasm/devflow --skill testing-tinywasm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow unifies Go testing by coordinating gotest, mocking patterns, WASM/stdlib dual testing, and automated publishing to ensure fast feedback and consistent test quality across local, CI, and agent workflows.

Core Features & Use Cases

  • gotest Runner: Handles vet, race, cover, and WASM tests with single-line outputs for dashboards.
  • Publishing (gopush): Automates testing, tagging, pushing, and dependency updates after successful runs.
  • Mocks & Dual Testing: Encourages mock-based tests and builds with build tags to support both WASM and stdlib environments.
  • Diagram-Driven Testing: Aligns tests with docs/diagrams and ensures coverage across branches.
  • CI Readiness: Integrates with CI pipelines and produces concise, readable results.

Quick Start

Run gotest to execute the full suite, or run gotest -run TestName to target specific tests, then publish with gopush after verifying docs and badges.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I automate Go test workflows from running tests to publishing?

Automating Go test workflows involves coordinating gotest, mocking patterns, and gopush to execute tests, validate coverage, and push updates. This ensures fast feedback and consistent quality across local, CI, and agent environments.

What is WASM and stdlib dual testing in Go?

WASM and stdlib dual testing uses build tags to execute Go tests in both WebAssembly and standard library environments. This approach encourages mock-based tests to verify deterministic behavior across different runtime targets.

How do I run targeted Go tests and publish results with gopush?

Run gotest -run TestName to target specific tests, then publish with gopush after verifying docs and badges. Gopush automates tagging, pushing, and dependency updates following successful test runs.

Does this Go testing workflow integrate with CI pipelines and dashboards?

Yes, the Go testing workflow integrates with CI pipelines and produces concise, single-line outputs designed for dashboards. It handles vet, race, cover, and WASM tests to ensure continuous integration readiness.

How does diagram-driven testing align Go tests with documentation?

Diagram-driven testing aligns Go test execution with diagrams stored in the docs/diagrams directory. This ensures test coverage validates branches and stays synchronized with documented system architecture.

What are the limitations of using gopush for automated dependency updates?

Gopush automates dependency updates and publishing only after successful gotest runs complete. You must verify documentation and badges before publishing, as it assumes prior test validation and diagram alignment.