skills.rest
ravnhq
ravnhqOFFICIAL
Explore all skills by this author →
WebsiteGitHub

platform-testing

Apply framework-agnostic testing principles to write, review, and debug tests.

16|15|Updated Jan 16, 2026
Search Tags:#testing#mocking#framework-agnostic#integration-testing#AAA#test-isolation
One-click install
npx skills add https://github.com/ravnhq/ai-toolkit --skill platform-testing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: platform-testing
Source: https://github.com/ravnhq/ai-toolkit/tree/main/skills/platform-testing
Command: npx skills add https://github.com/ravnhq/ai-toolkit --skill platform-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tests across teams often diverge in style and approach, causing flaky results and high maintenance costs. This Skill standardizes testing practices to improve reliability and readability.

Core Features & Use Cases

  • Test behavior, not implementation details
  • Prefer integration tests over unit tests
  • Arrange-Act-Assert (AAA) pattern in every test
  • Tests must be independent — no shared mutable state
  • Keep tests small and focused — one behavior per test
  • Name tests to describe the behavior being verified
  • Optimize for confidence, not coverage percentage
  • Don't chase 100% coverage — test what matters

Quick Start

Provide a concise testing plan for a new feature following AAA, with guidance on isolation and clear test naming.

Frequently Asked Questions about platform-testing

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

FAQPage Schema
What is the AAA pattern in integration testing and when should I use it?▼

The AAA pattern structures integration testing into Arrange, Act, and Assert phases to verify behavior. Use it in every test to improve readability and reliability across frontend, backend, or database contexts.

How do I structure unit tests to avoid shared mutable state and flaky results?▼

Structure unit tests to ensure complete test isolation by eliminating shared mutable state. Keep tests small and focused on one behavior per test, using meaningful names to describe the behavior being verified.

Does framework-agnostic testing work for both frontend and backend environments?▼

Framework-agnostic testing applies across frontend, backend, and database contexts. It standardizes testing practices without relying on specific frameworks, ensuring consistent test behavior and reducing maintenance costs.

What is the best way to decide between using mocks or real dependencies in tests?▼

The best way to decide on mocking is to test behavior, not implementation details. Evaluate whether real dependencies provide higher confidence, prioritizing integration tests over unit tests while optimizing for confidence over coverage percentage.

Why does chasing 100% test coverage lead to high maintenance costs?▼

Chasing 100% test coverage leads to high maintenance costs because it encourages testing implementation details rather than behavior. Optimize for confidence by testing what matters, avoiding brittle tests that diverge in style and cause flaky results.

Related Skills

Explore More Software Engineering Skills→
onzhangonzhang
2

java-backend-workflow

Define a framework-agnostic Java backend workflow for MySQL-backed applications.

Community
Advanced
LudwigAJLudwigAJ

test-writing

Write Rust unit, integration, async tokio, and mocking tests.

Community
Intermediate
jiroamatojiroamato

pr

Create pull requests from current branches using GitHub templates and validation checks.

Community
Intermediate
rsmdtrsmdt
381

testing-strategies

Design test suites and assess coverage using test pyramid principles across Jest and Pytest.

Community
Advanced