testing

Prioritize integration tests and observable outcomes over implementation details.

9|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/susomejias/rembric --skill testing-susomejias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/susomejias/rembric/tree/main/.agents/skills/testing
Command: npx skills add https://github.com/susomejias/rembric --skill testing-susomejias

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the common pain point of writing brittle, low-confidence tests that break during unrelated code refactors, waste time verifying implementation details instead of user-facing behavior, and fail to align test effort with actual business risk.

Core Features & Use Cases

  • Testing Trophy Bias Guidance: Defaults to prioritizing static checks and integration tests over excessive unit or end-to-end tests, balancing confidence and maintenance cost.
  • Risk-Aligned Prioritization: Provides a checklist to prioritize testing for high-impact functionality like payments, auth, and critical user flows instead of chasing arbitrary coverage goals.
  • Mocking and Interaction Testing Best Practices: Guides users to mock only real external boundaries (network, time, third-party APIs) and assert on observable user-facing outcomes instead of internal method calls.
  • Use Case: For a team building a new checkout feature, use this Skill to design integration tests that validate the full payment flow end-to-end, rather than mocking every internal service, reducing test flakiness and catching real user-facing bugs.

Quick Start

Use the testing skill to design a test plan for your new user permission system that prioritizes integration tests for role assignment and access control flows.

Frequently Asked Questions about testing

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

FAQPage Schema
Why do my unit tests break during refactoring even when the application behavior stays the same?

Tests break during refactoring because they verify implementation details instead of observable behavior. Prioritizing behavior verification and asserting user-facing outcomes over internal method calls prevents this brittleness.

What is the best way to align test coverage with actual business risk?

Align test coverage with business risk by prioritizing high-impact functionality like payments and authentication. Use a risk-aligned checklist to focus test effort on critical user flows instead of chasing arbitrary coverage metrics.

How do I stop over-mocking internal services in my integration tests?

Stop over-mocking by only mocking real external boundaries such as network requests, third-party APIs, and time. Assert on observable user-facing outcomes rather than internal application method calls to reduce test flakiness.

When should I prioritize integration tests over unit tests?

Prioritize integration tests when you need higher confidence in critical user flows. An integration-first testing bias balances maintenance cost and confidence by validating full feature paths rather than isolated, over-mocked units.

Can I use this testing strategy for end-to-end test levels?

Yes, the testing strategy supports unit, integration, and end-to-end test levels. It guides observable outcome assertions across all levels while maintaining an integration-first bias to optimize overall test suite confidence.

Does this approach require any specific testing frameworks or dependencies?

No, this approach requires no specific testing frameworks or dependencies. It provides a framework-agnostic strategy for designing test plans, writing assertions, and reducing unnecessary mocking across your software engineering workflow.