skills.rest
liangmiQwQ
liangmiQwQCOMMUNITY
Explore all skills by this author →
Website𝕏@liangmiQwQGitHub

adding-tests

Write integration tests validating user-visible behavior via public APIs.

Updated Apr 12, 2026
Search Tags:#testing#isolation#integration-testing#user-behavior#bug-fix#test-architecture#new-feature
One-click install
npx skills add https://github.com/liangmiQwQ/skills --skill adding-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adding-tests
Source: https://github.com/liangmiQwQ/skills/tree/main/my-skills/adding-tests
Command: npx skills add https://github.com/liangmiQwQ/skills --skill adding-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tests that validate real user-visible behavior instead of internal implementation details, ensuring bugs are caught from the user's perspective and resilient to refactors.

Core Features & Use Cases

  • Guided routing by context using dedicated guidance for bug fixes and new features.
  • Emphasis on integration tests that exercise the public API, end-to-end flows, and observable outcomes.
  • Clear rules and best practices for test isolation, public-behavior focus, and reproducible results.

Quick Start

Identify the user-facing behavior to protect and write one integration test per issue following the routing guidance.

Frequently Asked Questions about adding-tests

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

FAQPage Schema
What is the best way to write integration tests for user behavior?▼

Integration tests for user behavior should validate real user-visible outcomes by exercising the public API and end-to-end flows. This ensures tests remain isolated, repeatable, and resilient to internal refactors.

How do I write tests for a bug fix without testing implementation details?▼

To write tests for a bug fix without testing implementation details, follow dedicated routing guidance to identify the user-facing behavior to protect. Focus solely on observable outcomes rather than internal logic.

When do I need user-facing tests for new features?▼

You need user-facing tests for new features when you want to catch bugs from the user's perspective. Validating real user-visible behavior ensures your new feature works correctly across end-to-end flows.

Does test isolation affect reproducible results in integration testing?▼

Test isolation directly affects reproducible results in integration testing by preventing state leakage between tests. Maintaining isolated tests ensures consistent validation of user behavior without external interference.

How to start writing user-focused tests for my public API?▼

To start writing user-focused tests for your public API, identify the specific user-facing behavior to protect. Then write one integration test per issue following routing guidance for bug fixes or new features.

Related Skills

Explore More Software Engineering Skills→
Me1eMe1e

test-driven-development

Guide software teams through the Red-Green-Refactor cycle for feature implementation and bug fixes.

Community
Intermediate
HexSleevesHexSleeves

tdd

Implement test-first development with red-green-refactor cycles for features and bug fixes.

Community
Intermediate
arbazkhan971arbazkhan971
26

e2e

Automate end-to-end testing workflows across Playwright, Cypress, Selenium, or custom frameworks.

Community
Advanced
tykhoncodetykhoncode

tdd-quality

Audit unit and integration tests for behavior-first vertical RED-GREEN cycles.

Community
Intermediate