Skip to content
Test framework

Running tests

Run tests, folders and suites, headless or inside the app, and read the results.

Find the Runner in the dock under Framework → Runner.

First-time setup

  • Node.js missing: the Runner shows Download Node.js and Re-check (see Requirements).
  • Node.js present: the first time, the app installs the test runner automatically (“Setting up test runner… (first run, one time)”). If it doesn’t complete, click Retry setup after checking the output.

The test list

  • All tests shows every test of the active project in folders: recordings and generated flow tests.
    • Hover a test and click ▶ to run it.
    • Hover a folder and click ▶ to run every test inside it (always headless).
    • Refresh re-reads the list.
  • Suites — named groups of tests:
    • New suite (+) creates one and lets you name it.
    • Add tests with the + next to each test → Add to suite (a test can be in several suites).
    • ▶ runs the suite; the pencil (or a double-click) renames it; × removes a test from it; the trash deletes the suite (the tests stay on disk).

Run options

On the right side of the Runner status bar:

OptionChoices
Playback speed⏩ Full speed, ▶ Slow (250 ms between actions), ▷ Slower (500 ms), 🐢 Slowest (1 s). Slower speeds make runs easy to follow.
Run modeHeadless — in a separate, invisible browser. In-App — visibly, in a dedicated tab of the app’s browser. Suites run in either mode.
Close tabsWhen on, test tabs opened by In-App runs close when the run ends; when off, they stay open for inspection.

Results

  • While running: Running, the test or suite name, and a Stop button.
  • The output streams line by line, with passed lines in green and failures in red.
  • At the end: Passed or Failed (exit N).
  • After a single test run, Report opens its HTML report in your default browser.
Running tests — Actify Studio Docs