# Testing Strategies

> Turn test-policy ambiguity into one packet-first validation brief.

Turn test-policy ambiguity into one packet-first validation brief. Use when the main job is deciding which gate is actually being shaped (merge, release, or scheduled), what evidence a change needs, how flaky or expensive suites should be handled, and whether the next owner is `backend-testing`, `debugging`, `code-review`, `deployment-automation`, `steam-store-launch-ops`, `game-ci-cd-pipeline`, `web-accessibility`, or `performance-optimization` instead of absorbing all test work here. Triggers on: test strategy, merge gate, required status checks, release gate, flaky-suite policy, regression policy, validation brief, release confidence, and what should we test.

- Page: https://ss33.ai/skills/akillness/testing-strategies-59738474408
- Publisher: akillness
- Category: [Software Development](https://ss33.ai/skills/category/software-development-t44z8z) › [Testing & QA](https://ss33.ai/skills/category/software-development-t44z8z/testing-and-qa-g56s6z)
- Source: https://github.com/akillness/jeo-skills/blob/d9af9e3de37b0fd940d5cab1897c9b9a00fd8a35/.agent-skills/testing-strategies/SKILL.md

## Skill

This skill's licence does not allow redistribution, so the store does not serve its text. Get it from the author: https://github.com/akillness/jeo-skills/blob/d9af9e3de37b0fd940d5cab1897c9b9a00fd8a35/.agent-skills/testing-strategies/SKILL.md