reference appendices

Testing Tool Index

PHP projects usually combine fast automated tests with static analysis, coding checks, and a smaller number of higher-level integration checks. Choose tools based on the failure they catch.

Use This Reference When

  • Selecting a test runner.
  • Adding static analysis or mutation testing.
  • Designing a CI check sequence.

Typical Check Sequence

composer validate --strict
vendor/bin/phpunit
vendor/bin/phpstan analyse
vendor/bin/php-cs-fixer check --diff

Tool names vary by project. The important skill is knowing what each check proves and keeping the local and CI paths repeatable.

Practice

Map Tools To Risks

Choose checks for a pure function, a database repository, and a JSON endpoint. Explain why one test type is insufficient.

Show solution

Use a focused unit test for the pure function, integration coverage for the repository boundary, and an HTTP-level check for the endpoint contract. Add static analysis for type-related defects.