skills.rest
cacack
cacackCOMMUNITY
Explore all skills by this author →
GitHub

check-tests

Inspect Go test files for edge cases, assertions, and database patterns.

4|1|Updated Dec 7, 2025
Search Tags:#qa#go#code-quality#coverage#table-driven#test-analysis#gedcom
One-click install
npx skills add https://github.com/cacack/my-family --skill check-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check-tests
Source: https://github.com/cacack/my-family/tree/main/.claude/skills/check-tests
Command: npx skills add https://github.com/cacack/my-family --skill check-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies gaps in Go test suites that coverage numbers alone do not reveal, focusing on edge cases, assertion quality, test patterns, database matrix coverage, and important missing tests such as GEDCOM round-trip validation.

Core Features & Use Cases

  • Edge case detection: Scans domain/*_test.go files for tests covering invalid inputs, empty values, nils, and error paths.
  • Assertion quality review: Samples test files to check whether assertions validate specific values, error types, or only basic nil checks.
  • Pattern and coverage checks: Detects use of table-driven tests, dual-database (sqlite/postgres) test patterns, presence of _test.go counterparts for core packages, and GEDCOM import/export round-trip tests.
  • Use Case: A QA lead or maintainer runs this skill on a Go monorepo to produce a prioritized PASS/WARN/FAIL report highlighting test gaps that require developer attention.

Quick Start

Run the check-tests skill on the repository to analyze Go test files and produce a PASS/WARN/FAIL report for each check.

Frequently Asked Questions about check-tests

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

FAQPage Schema
How do I check Go test quality beyond basic coverage numbers?▼

Analyzing test health beyond coverage involves scanning Go test files for edge cases, assertion quality, and table-driven patterns. This skill targets domain, command, and query packages to produce a structured PASS/WARN/FAIL report detailing weak assertions and missing tests.

What is a table-driven test pattern and how do I verify it in my Go repository?▼

Table-driven tests structure Go test cases into arrays for iterative validation. This skill detects table-driven pattern usage in test files and warns when core packages are missing this structured approach to input validation.

Can I detect missing GEDCOM round-trip tests in a Go monorepo?▼

You can detect missing GEDCOM round-trip tests in a Go monorepo. The analysis scans for GEDCOM import and export validation tests, flagging their absence as a test suite gap in the generated PASS/WARN/FAIL report.

Does this work with Go projects using both sqlite and postgres databases?▼

This works with Go projects using sqlite and postgres databases. It checks for dual-database test patterns to ensure your tests validate both happy and error paths across different database implementations.

How do I find weak assertions in my Go test files?▼

Finding weak assertions in Go test files involves sampling test files to check whether assertions validate specific values and error types, or only perform basic nil checks. The skill highlights these weak assertions in a structured report.

Related Skills

Explore More Software Engineering Skills→
Arx-GameArx-Game
4

running-tests

Guide SQLite and Postgres test workflows with just wrappers and tag decisions.

Official
Advanced
xorzaxorza
1

Improve tests

Improve Rust submodule test suites by adding missing tests and refining weak assertions.

Community
Intermediate
chtughachtugha

qa-review

Reviews code changes for test coverage, edge cases, and potential regressions using Python analysis and test generation.

Community
Intermediate
MatthieuszMatthieusz

coding-standards

Validate TypeScript code against predefined coding standards using static analysis tools.

Community
Advanced