ce-test-author

Standardize CE test authoring with AAA structure and public-API focus.

78|15|Updated May 1, 2023
One-click install
npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-test-author
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-test-author
Source: https://github.com/Moffran/calibrated_explanations/tree/main/.claude/skills/ce-test-author
Command: npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-test-author

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes CE test authoring by enforcing AAA structure, public-API focus, and the CE tests rubric, reducing ambiguity and inconsistency across test suites.

Core Features & Use Cases

  • Enforces consistent test placement and naming across unit, integration, and end-to-end scopes.
  • Provides a deterministic testing approach with guidelines for fixtures, seeding, and isolation.
  • Documents coverage-gate discipline to ensure tests meet quality thresholds without introducing coverage gaps.

Quick Start

Create a unit test file following tests/unit/<package>/test_<module>.py and implement a single AAA-style test that adheres to the README rubric.

Frequently Asked Questions about ce-test-author

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

FAQPage Schema
How do I standardize pytest test structure to reduce ambiguity across test suites?▼

Standardize pytest test authoring by enforcing AAA structure, public-API focus, and deterministic testing guidelines to reduce ambiguity and inconsistency across unit, integration, and end-to-end test suites.

What is the best way to enforce naming conventions and coverage-gate validation in automated tests?▼

Enforce naming conventions and coverage-gate validation by documenting coverage-gate discipline to ensure tests meet quality thresholds without introducing coverage gaps across all testing scopes.

How do I structure deterministic unit tests with AAA rigor for public APIs?▼

Structure deterministic unit tests with AAA rigor by applying guidelines for fixtures, seeding, and isolation while focusing assertions strictly on public-API behavior to remove variability.

Can I use this approach for both integration and end-to-end testing in a software development workflow?▼

Yes, this standardized test authoring approach applies to unit, integration, and end-to-end testing across software modules within a software development workflow.

Why does my test suite lack consistency in test placement and naming across different scopes?▼

Test suites lack consistency when standardization is absent; enforcing consistent test placement and naming across unit, integration, and end-to-end scopes resolves this variability.

Do I need external dependencies to apply AAA-driven test authoring for calibrated explanations modules?▼

No external dependencies are required; the Skill operates independently to standardize test authoring for calibrated_explanations modules using deterministic testing and AAA structure.