Testing & Verification

Run automated PHP test suites and static analysis after code changes.

Updated Oct 18, 2025
One-click install
npx skills add https://github.com/screenfluent/aicodingforum --skill testing-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Testing & Verification
Source: https://github.com/screenfluent/aicodingforum/tree/main/.claude/skills/testing
Command: npx skills add https://github.com/screenfluent/aicodingforum --skill testing-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After code generation, bug fixes, or refactoring, this Skill ensures you run the appropriate tests and analyses to validate correctness and quality, reducing regression risk.

Core Features & Use Cases

  • Quick verification: Syntax, unit, and style checks for rapid feedback.
  • Targeted tests: Run unit, integration, and architecture checks to pinpoint issues.
  • Static analysis & coverage: PHPStan level 9 checks, test coverage enforcement, and architecture analysis with Deptrac.

Quick Start

Execute the verification steps after changes:

  • composer test:fast - syntax, unit, style (~5-10s)
  • composer test - full suite before commit (~30-60s)
  • composer test:unit - unit tests
  • composer test:integration - DB/filesystem tests
  • composer analyze:architecture - Deptrac layer analysis

Frequently Asked Questions about Testing & Verification

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

FAQPage Schema
How do I run automated tests and static analysis on PHP code?

Automated testing and static analysis validate code quality through syntax checks, unit tests, integration tests, and PHPStan level 9 analysis. Use `composer test:fast` for quick feedback (~5-10s) or `composer test` for the full suite (~30-60s) to catch regressions and style violations before commit.

What's the best way to verify code after refactoring or bug fixes?

Run targeted verification workflows: execute unit tests with `composer test:unit`, integration tests with `composer test:integration`, and architecture analysis with `composer analyze:architecture` using Deptrac to ensure changes maintain layer boundaries and don't introduce regressions.

Can I enforce test coverage and static analysis in pre-commit hooks?

Yes. This Skill provides conditional pre-commit checks that run syntax validation, style checks via PHP CS Fixer, and coverage enforcement at 95% to prevent code with unmet quality standards from being committed.

How does PHPStan level 9 improve code quality verification?

PHPStan level 9 performs deep static analysis to detect type errors, undefined variables, and logical issues before runtime. Combined with parallel-lint syntax checks and Deptrac architecture validation, it catches bugs early and enforces strict code standards.

Do I need to run all tests every time or can I run targeted checks?

You can run targeted checks for speed: `composer test:fast` runs syntax and unit tests in 5-10 seconds for rapid feedback, while `composer test` runs the full suite including integration and architecture tests before final commit or deployment.