eng-testing

Guide unit, integration, and E2E test selection for boundary and critical-flow scenarios.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/CasaPerks/casaflow --skill eng-testing-casaperks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eng-testing
Source: https://github.com/CasaPerks/casaflow/tree/main/packs/engineering/skills/eng-testing
Command: npx skills add https://github.com/CasaPerks/casaflow --skill eng-testing-casaperks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

eng-testing helps you create deterministic, independent, and meaningful tests so your suite stays trustworthy instead of flaky or meaningless.

Core Features & Use Cases

  • Test pyramid guidance: Choose unit, integration, or E2E tests based on boundaries and critical user flows.
  • Test quality standards: Enforce determinism, independence, speed, descriptive naming, and behavior-focused assertions.
  • Practical structure and coverage priorities: Use Arrange-Act-Assert, cover happy paths/error/edge cases, and focus coverage on business logic and error handling.

Quick Start

When reviewing a failing test or adding coverage for a new feature, follow the test pyramid and rewrite the test to be deterministic and behavior-based, using one clear action per test.

Frequently Asked Questions about eng-testing

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

FAQPage Schema
How do I choose between unit, integration, and e2e testing for my application?

Choose tests based on boundaries and critical user flows. Unit tests isolate business logic, integration tests verify interactions across boundaries, and e2e testing validates critical user paths end-to-end.

What is the best way to fix flaky tests in my test suite?

Fix flaky tests by enforcing determinism and independence. Isolate tests from external state, mock boundaries consistently, and ensure each test runs fast without side effects to maintain suite trustworthiness.

How should I structure test cases to focus on behavior instead of configuration?

Structure test cases using Arrange-Act-Assert with one act per test. Cover happy paths, errors, and edge cases while prioritizing meaningful coverage over framework boilerplate using descriptive, behavior-focused naming.

When should I use mocking in my integration tests?

Use mocking in integration tests to enforce test independence and determinism. Apply mocking to external boundaries to isolate the system under test, ensuring fast execution and eliminating flaky dependencies.

What does the test pyramid mean for organizing my test strategy?

The test pyramid organizes your test strategy by prioritizing a large base of fast, isolated unit tests, fewer integration tests for boundaries, and minimal e2e tests for critical flows to optimize speed and coverage.