Pular para o conteúdo
PHP Ecosystem
Explore

Testing

Este conteúdo não está disponível em sua língua ainda.

This package provides a consistent set of Composer scripts for local validation. Use a source checkout with PHP 8.3 or later and development dependencies installed. Record the PHP version, resolved dependency revisions, and any symlinked package path before interpreting results.

Tool references:

Terminal window
composer install
composer validate --strict
composer audit

Do not bypass security advisories to obtain a successful install. A consuming application should commit its lock file; this library’s local lock file is ignored.

Run Rector to apply automated code refactoring. This command modifies files.

Terminal window
composer rector

Preview the refactoring without modifying files.

Terminal window
composer rector-check

Check coding standards without modifying files.

Terminal window
composer ecs-check

Apply coding standard fixes. Review the changes before keeping them.

Terminal window
composer ecs

Verify that runtime dependencies are correctly declared in composer.json.

Terminal window
composer check-dependencies

Run mutation testing.

Terminal window
composer mutation

Run mutation testing with PHPStan static analysis enabled.

Terminal window
composer mutation-static

Both scripts disable Composer’s process timeout, set PHP’s memory limit to unlimited, use four workers, ignore the MSI when there are no generated mutations, and require 100% MSI and covered MSI. composer mutation-static additionally enables PHPStan with an unlimited memory limit. infection.json5 defines the source directory, per-test timeout, and reporting; it does not contain the command-line thresholds. The shared CI workflow receives the same worker and MSI options. Infection requires an available coverage driver, and a failed or skipped initial suite is not a passing run.

Make the CLI tools used by the shared quality workflow available on PATH: actionlint with its ShellCheck helper, codespell, EditorConfig Checker, markdownlint-cli2, Prettier, and yamllint. Run all checks:

Terminal window
composer quality

Each tool also has its own script:

Terminal window
composer actionlint
composer codespell
composer editorconfig-checker
composer markdownlint
composer prettier
composer yamllint

The linter configuration lives in .github/linters, and the Prettier configuration lives in .prettierrc.json and .prettierignore. The shared quality workflow uses those exact files.

Run static analysis.

Terminal window
composer static

Run the full test suite.

Terminal window
composer tests

Documentation and application verification

Section titled “Documentation and application verification”

In an application, also verify that every intended runner consumes the required groups, every intended middleware pipeline contains both debugger middleware IDs in package order, an allowed HTML request receives the toolbar and is retained in History, a known log entry appears in Logs with sensitive keys redacted, an unlisted client is denied, and a production process has no debugger integration. Trigger the real application behavior for optional Mail, User, RBAC, Inertia, or Vite panels; panel registration alone does not prove that an event reached its collector.

Validate skills/yii3-debug-integration/SKILL.md with a compatible Agent Skills validator. Build a Composer archive and inspect its file list: the skill must be included, while .agents/, .claude/, AGENTS.md, docs/, and any future examples/ directory must be absent. Test composer skills:show and synchronization in a disposable application with llm/skills configured. Native client discovery and activation are separate checks from installation and synchronization.

Make zizmor and Gitleaks available on PATH. Audit the current workflow files with the same pedantic persona used by the shared security workflow:

Terminal window
composer zizmor

Scan Git history for secrets with the repository’s Gitleaks configuration:

Terminal window
composer gitleaks

Run both checks. Findings make the command fail; inspect them rather than disabling the checks.

Terminal window
composer security

Zizmor needs GitHub API access for its online audits. If the tool runs offline, report that limit separately. To request an offline audit explicitly:

Terminal window
composer zizmor -- --offline

Report hosted CI execution and its PHP/OS matrix separately from these local commands. Keep generated reports in ignored internal/.

Composer scripts support forwarding additional arguments using --.

Run PHPUnit with code coverage report generation.

Terminal window
composer tests -- --coverage-html internal/coverage

Run PHPStan with a different memory limit.

Terminal window
composer static -- --memory-limit=512M

Back to documentation