skills.rest
infraspecdev
infraspecdevOFFICIAL
Explore all skills by this author →
Website𝕏@infraspecdevGitHub

backend-testing-strategy-review

Review backend test code for strategy flaws across unit, integration, and end-to-end tests.

3|Updated Mar 10, 2026
Search Tags:#testing#backend#coverage#mocking#test review#assertions#flakiness
One-click install
npx skills add https://github.com/infraspecdev/tesseract --skill backend-testing-strategy-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-testing-strategy-review
Source: https://github.com/infraspecdev/tesseract/tree/main/shield/skills/backend/testing-strategy-review
Command: npx skills add https://github.com/infraspecdev/tesseract --skill backend-testing-strategy-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify weak or misleading backend tests before they create false confidence, missed regressions, or flaky CI results.

Core Features & Use Cases

  • Test Scope Review: Distinguishes unit, integration, and end-to-end tests so each one matches its intent.
  • Mock and Assertion Audit: Flags incorrect mocking boundaries, missing assertions, and tests that verify implementation details instead of behavior.
  • Stability and Coverage Checks: Surfaces shared-state leaks, timing-based flakiness, poor setup clarity, weak naming, and missing edge-case coverage.
  • Use Case: Review a pull request that adds tests for a backend service and quickly spot whether the new tests are actually trustworthy.

Quick Start

Ask for a backend test review of the attached diff and have it evaluate scope, mocking, assertions, isolation, flakiness, and coverage.

Frequently Asked Questions about backend-testing-strategy-review

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

FAQPage Schema
How do I review backend tests for flakiness and weak assertions in a pull request?▼

You can review backend tests by checking test scope, mock boundaries, assertions, isolation, flakiness, setup clarity, and edge-case coverage to catch weak tests before they ship and create false confidence.

What is the best way to audit mocking boundaries in backend integration tests?▼

Auditing mocking boundaries involves flagging incorrect mock setups and tests that verify implementation details instead of behavior, ensuring your backend integration tests remain isolated and maintainable.

How do I check if my unit, integration, and end-to-end tests have proper pyramid balance?▼

Checking pyramid balance requires distinguishing unit, integration, and end-to-end tests so each matches its intent, surfacing weak naming and missing edge-case coverage that could cause missed regressions.

Does this backend test review work for pre-implementation planning and onboarding audits?▼

Yes, backend test review applies to pre-implementation planning and onboarding audits, evaluating test scope, assertions, isolation, and flakiness to ensure test strategy is sound before code ships.

Why do my backend tests pass locally but fail in CI due to shared-state leaks?▼

Shared-state leaks cause timing-based flakiness and false confidence in CI; reviewing test isolation and setup clarity helps surface these leaks and stabilize backend test results across environments.

Related Skills

Explore More Software Engineering Skills→
Obsidian-OwlObsidian-Owl
9

gate-tests

Audit automated test quality for assertion strength, boundary coverage, mock discipline, and error paths.

Official
Advanced
sayedihashimisayedihashimi
2

test-anti-patterns

Detect and report anti-patterns in .NET test suites.

Community
Advanced
ValyntValynt

ci-pipeline-checks

Automates end-to-end CI pipeline validation including builds, tests, and security scans for GitHub Actions and other CI runtimes.

Official
Advanced
sunholo-datasunholo-data
33

Test Coverage Guardian

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

Community
Intermediate