skills.rest
nmnmcc
nmnmccCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

testing

Design maintainable tests that verify observable behavior at runtime boundaries.

2|Updated Jul 11, 2026
Search Tags:#testing#pytest#integration tests#flaky tests#test design#behavioral testing
One-click install
npx skills add https://github.com/nmnmcc/skills --skill testing-nmnmcc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/nmnmcc/skills/tree/main/skills/testing
Command: npx skills add https://github.com/nmnmcc/skills --skill testing-nmnmcc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design and maintain tests that prove software behaves correctly at the boundaries real users, systems, and releases can observe. It reduces weak, flaky, slow, or misleading tests by focusing on meaningful risks and observable outcomes.

Core Features & Use Cases

  • Behavior-first test design: Choose cases from real promises, risks, and user-visible effects instead of code branches.
  • Right-sized test boundaries: Pick the smallest useful runtime boundary, from unit to end-to-end, that can expose the important failure.
  • Stable, maintainable suites: Improve existing tests, remove brittle checks, and keep test signals trustworthy across time and environments.
  • Use case: When a bug affects serialization, retries, or a deployed integration, this Skill helps you add the narrowest test that would fail for the same real problem.

Quick Start

Use the testing skill to design a small set of observable tests for this feature change and explain which runtime boundary each one should cover.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I design integration tests that verify observable behavior instead of code branches?▼

Design integration tests by selecting cases from real promises, risks, and user-visible effects. This behavior-first approach ensures tests prove software behaves correctly at runtime boundaries rather than mirroring internal code paths.

What's the best way to fix flaky tests in a pytest suite?▼

Fix flaky tests by improving existing suites and removing brittle checks. Focus on stable, maintainable assertions that keep test signals trustworthy across time and environments, selecting only meaningful risks and observable outcomes.

How do I choose the right test boundaries from unit to end-to-end?▼

Choose the smallest useful runtime boundary that can expose the important failure. Selecting right-sized test boundaries ensures you pick the narrowest scope—from unit to end-to-end—capable of proving user-visible outcomes or failure handling.

When do I need to use test doubles and fixtures for behavioral testing?▼

Use test doubles and fixtures when you need to verify contract compatibility or failure handling at real runtime boundaries. Behavioral testing requires selecting risks and boundaries that prove user-visible outcomes without relying on brittle internal checks.

Can I use this approach to add a narrow test for a serialization or retry bug?▼

Yes, when a bug affects serialization, retries, or a deployed integration, this approach helps you add the narrowest test that would fail for the same real problem. It targets observable behavior at meaningful runtime boundaries.

Related Skills

Explore More Software Engineering Skills→
jshsakurajshsakura
22

qa-expert

Define risk-based test scope and acceptance criteria for software releases.

Community
Advanced
zxyycomzxyycom

debugging-and-error-recovery

Diagnose and fix test, build, and runtime failures using structured root-cause debugging.

Community
Advanced
partme-aipartme-ai
610

pytest

Provides guidance for writing and configuring pytest tests in Python.

Official
Intermediate
sunholo-datasunholo-data
33

Test Coverage Guardian

Analyze test coverage to identify gaps, dead code, and brittleness.

Community
Intermediate