as-test-dev

Write, review, and restructure Python tests with behavior-driven naming conventions.

Updated Mar 15, 2026

Search Tags:#testing #pytest #python #code-quality #test #behavior-driven #test-coverage

Ready to run

npx skills add https://github.com/aaronsilinskas/ai-skills --skill as-test-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: as-test-dev
Source: https://github.com/aaronsilinskas/ai-skills/tree/main/as-test-dev
Command: npx skills add https://github.com/aaronsilinskas/ai-skills --skill as-test-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write, review, or restructure Python tests with a product-focused, behavior-driven philosophy. Use this skill whenever writing new tests, auditing existing ones, naming test functions, or planning coverage — even if the user just says 'add tests' or 'check my tests.' Also use when the user asks whether a test is good, what to test next, or whether their test suite is missing something. Covers naming conventions, test structure, and distinguishing behavior-driven tests from code-path-mirroring tests.

Core Features & Use Cases

Guides test naming to reflect guaranteed behavior and scenarios
Helps audit and restructure test suites for coverage and clarity
Assists in planning test strategy across modules and features in a product-focused way

Quick Start

Describe the code behavior you want verified and request test stubs or an audit.

Frequently Asked Questions about as-test-dev

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

FAQPage Schema

How do I write behavior-driven Python tests instead of mirroring code paths?▼

Use this skill to audit existing pytest suites, identify missing test-coverage areas, and generate behavior-focused test stubs. Describe the module behavior you want verified, and it provides naming conventions and structural guidance to plan test strategy across product features.

What makes a good pytest function name for behavior-driven testing?▼

A good pytest function name reflects guaranteed product behavior and scenarios rather than mirroring internal code paths. Use naming conventions that document what the feature guarantees, making tests readable and resistant to breaking during implementation refactoring.

How do I audit my Python test suite for missing test coverage?▼

Audit Python test-coverage by evaluating whether existing tests verify product guarantees or merely mirror code paths. Restructure test suites by planning coverage across modules, applying behavior-driven principles to identify gaps, and renaming functions to reflect guaranteed behavior.

When should I distinguish between behavior-driven tests and code-path-mirroring tests?▼

Distinguish between behavior-driven and code-path-mirroring tests whenever writing new tests or auditing existing ones. Behavior-driven tests codify product guarantees and survive refactoring, while code-path-mirroring tests break when internal implementation changes without altering product behavior.

Can I use this approach to plan test strategy across multiple Python modules?▼

Yes, you can plan test strategy across multiple Python modules by applying behavior-driven testing principles. Audit modules to establish naming conventions and plan test-coverage in a product-focused way that clarifies what each feature guarantees, ensuring comprehensive suite validation.