test-audit

Audits and rewrites project test suites for coverage and redundancy.

Updated Jan 21, 2019

Search Tags:#testing #test coverage #code audit #property-based testing #test rewrite #snapshot testing

Ready to run

npx skills add https://github.com/jtdowney/dotfiles --skill test-audit-jtdowney

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-audit
Source: https://github.com/jtdowney/dotfiles/tree/main/dot_codex/skills/test-audit
Command: npx skills add https://github.com/jtdowney/dotfiles --skill test-audit-jtdowney

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of auditing and rewriting project test suites, ensuring comprehensive coverage, eliminating redundancy, and improving test quality.

Core Features & Use Cases

Test Suite Auditing: Analyzes existing tests to identify gaps, redundancies, and areas for improvement.
Test Rewriting: Facilitates the process of rewriting tests from scratch or refactoring existing ones.
Coverage Improvement: Helps in enhancing test coverage by identifying and addressing untested code paths.
Use Case: A team needs to refactor a legacy module and wants to ensure the test suite is robust and efficient before and after the changes.

Quick Start

Initiate an interactive workflow to audit and rewrite tests for the current project.

Frequently Asked Questions about test-audit

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

FAQPage Schema

How do I audit and rewrite project tests to improve coverage?▼

Test suite auditing analyzes existing tests to identify gaps and redundancies, while rewriting facilitates refactoring or creating tests from scratch to improve coverage and eliminate unnecessary test code.

What is the best way to refactor a legacy module test suite?▼

Refactoring a legacy module test suite requires an interactive workflow that reviews tests module-by-module to ensure robustness, eliminate redundancy, and validate tests before and after implementing code changes.

Does test auditing support property-based testing and snapshot testing patterns?▼

Test auditing supports property-based testing and snapshot testing patterns, providing specific guidance for these approaches in Gleam and Rust projects to ensure appropriate test type usage.

Can I audit tests module-by-module instead of scanning the full project?▼

You can audit tests module-by-module instead of running a full project audit, allowing targeted reviews and post-implementation validation for specific code sections.

When should I prefer property-based testing over snapshot testing?▼

You should prefer specific test types for certain patterns by adhering to testing principles that ensure you only test essential code, choosing property-based or snapshot testing based on the specific logic being validated.

How do I eliminate redundant tests during a code audit?▼

A code audit eliminates redundant tests by analyzing the existing test suite to identify overlapping coverage and rewriting tests to ensure comprehensive coverage without unnecessary duplication.