PHP From ZeroModern PHP course

testing php applications

Pest Advanced Features Orientation

Match The Tool To The Problem

Architecture tests can protect namespace rules. Parallel execution can shorten independent suites. Profiling finds slow tests. Snapshots detect output changes but require careful review. Browser testing covers a real UI where that boundary matters.

Isolation Comes First

Parallel tests must not share mutable state or assume execution order. Snapshots need stable data. Browser tests need deterministic setup. Each speed or convenience feature reveals weak isolation if the suite was relying on hidden coupling.

./vendor/bin/pest --parallel
./vendor/bin/pest --profile
./vendor/bin/pest --update-snapshots

Common Mistakes

  • Turning snapshots into an approve-without-reading workflow.
  • Running parallel tests against shared mutable resources.
  • Adding architecture rules nobody maintains.
  • Using browser checks for every unit-level rule.

What To Practise

  • Choose an advanced feature for a concrete need.
  • Prepare tests for parallel isolation.
  • Review snapshot changes deliberately.

Practice

Practice: Choose Pest Features For A Suite

Recommend Pest features for a slow suite with architecture drift and one critical login journey.

Requirements

  • Use profiling before optimising blindly.
  • Consider parallel execution and isolation.
  • Add one architecture rule.
  • Keep the login browser journey narrow.
Show solution

The plan applies each feature to a specific problem.

  • Profile the suite before optimizing it, remove shared mutable state, and then trial parallel execution.
  • Add one maintained architecture rule for the namespace dependency that is drifting.
  • Keep one narrow login browser journey alongside lower-level authentication tests.
  • Use snapshots only for stable output whose changes will be reviewed.

The official Pest documentation shows the current command flags and plugin requirements.