メニュー
Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ai-regression-testing |
| description | Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots. |
| origin | ECC |
Testing patterns for AI-assisted development, where the same model writes code and reviews it -- creating systematic blind spots that only automated tests can catch.
When an AI writes code and then reviews its own work, it carries the same assumptions into both steps:
AI writes fix -> AI reviews fix -> AI says "looks correct" -> Bug still exists
AI adds field to production path but forgets sandbox path, or vice versa.
Test to catch it: Assert same response shape in both paths.
New column added to response but not to the SELECT query.
Error state set but old data not cleared.
Optimistic update without rollback on API failure.
Do not aim for 100% coverage. Instead, write tests for code that had bugs:
This works because AI tends to make the same category of mistake repeatedly.
| AI Regression Pattern | Test Strategy | Priority |
|---|---|---|
| Sandbox/production mismatch | Assert same response shape | High |
| SELECT clause omission | Assert all required fields | High |
| Error state leakage | Assert state cleanup on error | Medium |
| Missing rollback | Assert state restored on failure | Medium |
Clean Architecture patterns for Android and Kotlin Multiplatform projects -- module structure, dependency rules, UseCases, Repositories, and data layer patterns.
Performance baseline and regression detection -- page performance, API latency, build times, and before/after comparison.
Turn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold.
Automated visual testing and interaction verification -- smoke tests, interaction tests, visual regression, and accessibility audits using browser automation.
Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.
Post-deploy monitoring -- watches deployed URLs for regressions in HTTP status, console errors, performance, content, and API health.