skills.rest
acmeleme
acmelemeOFFICIAL
Explore all skills by this author →
GitHub

test-discipline

Update dependent test assertions and EXPECTED_* arrays after API changes.

Updated Nov 11, 2025
Search Tags:#qa#fixtures#test#assertions#ci#api-changes#test-synchronization
One-click install
npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill test-discipline-acmeleme
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-discipline
Source: https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator/tree/main/.copilot/skills/test-discipline
Command: npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill test-discipline-acmeleme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When APIs change, tests must be updated in the same commit to prevent CI failures and drift between code and tests.

Core Features & Use Cases

  • Detect API changes and identify impacted tests to ensure the test suite remains accurate.
  • Synchronize fixtures and assertions by updating expected counts and data structures.
  • Prevent CI regressions by enforcing same-commit test updates during API evolution.

Quick Start

Update your API changes in the same commit and adjust corresponding tests to reflect the new behavior.

Frequently Asked Questions about test-discipline

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

FAQPage Schema
How do I keep tests aligned with API changes to prevent CI failures?▼

To keep tests aligned with API changes, update dependent test assertions within the same commit to prevent CI regressions and drift between code and tests.

Why do my fixtures and assertions break after an API surface change?▼

Fixtures and assertions break after an API surface change because test expectations and data structures no longer match the new API behavior, requiring you to synchronize fixtures and update expected counts across the codebase.

What is the best way to synchronize test expectations during API evolution?▼

The best way to synchronize test expectations during API evolution is to detect API changes, identify impacted tests, and adjust EXPECTED_* arrays and fixtures in the same commit to enforce test synchronization.

When do I need to update EXPECTED_* arrays in my test suite?▼

You need to update EXPECTED_* arrays in your test suite whenever API surface changes impact test expectations, fixtures, or file counts across the codebase, ensuring CI remains green and preventing code-test drift.

Does enforcing same-commit test updates work for preventing CI regressions?▼

Enforcing same-commit test updates prevents CI regressions by ensuring that any API changes are immediately accompanied by corresponding fixture and assertion updates, eliminating drift between code and tests.

Related Skills

Explore More Software Engineering Skills→
nok0321nok0321

quick-test

Run only tests affected by git diff changes.

Community
Intermediate
roberttmadsen13-delroberttmadsen13-del

tdd-rust

Automate Red-Green-Refactor TDD for RTK filters in Rust with insta snapshots.

Community
Advanced
htooayelwinicthtooayelwinict

documentation-management

Update project documentation files when system behavior changes.

Community
Intermediate
DexploarerDexploarer
6

mock-generator

Generate test mocks, stubs, and fixtures for JavaScript/TypeScript and Python projects.

Community
Intermediate