KO

Tests

The Tests window (bottom) shows the project's tests as a tree, found by reading the files, without running anything: PHPUnit (suites, files, classes, methods, data sets), Pest, JumPHP game tests, and JavaScript tests (*.test.mjs with node --test, Vitest, Jest).

The Tests window

Run

  • Run All, a suite, a file, a class, a method, a data set, Rerun the Failed Tests.
  • The test at the cursor: Ctrl+Shift+F10, or the ▶ in the editor's gutter (coloured by the last result).
  • Results come live: the tree turns green or red as tests end.
  • A failure shows expected / actual side by side, the stack's links and what the test printed.
  • A game test shows its filmed frames (a picture every 4 frames) and its last frame.
  • The clock button reruns the last tests whenever a file is saved.
  • Filters: failed only, slow (≥ 500 ms). The summary bar: passed / failed / skipped, time, coverage, the last 10 runs.

How they run

Project Command
JumPHP game / app, engine, ide bin/jumphp test <id> --phpunit (Docker)
web site / any PHP project PHPUnit in the site's PHP container, or the computer's PHP (runner Local)
JavaScript node --test, npx vitest run, npx jest (the computer's node, else Docker)

Coverage

The ✓ button (Run All Tests with Coverage): Xdebug in coverage mode; green / red bars in the editor's gutter and a percentage per file in the tree.

Limits

Pest's names are guessed from the code; JavaScript has no coverage; PHPUnit 12+ ignores @test.