Collection Runner

• Platform Availability: Windows App · VS Code Extension (shared shell)
• Overview: Runner executes a collection or folder plan with live pass/fail, configuration, history, and reports. Use it for regression suites and data-driven runs.

How It Works (Windows App)

1. Switch to Runner mode.
2. Select a collection and optional folder scope.
3. Review the execution plan checkboxes; filter with Ctrl+F.
4. Open Configuration for iterations, delay, timeout, stop-on-fail, retry, workers, SSL, reports, and test data.
5. Click Run (or Ctrl+Enter). Use Pause / Resume / Stop / Restart as needed.
6. Review Dashboard, Report, Inspector, and Results. Export reports (json, html, pdf, junit, csv).

Toolbar & overflow

• Collection select, FolderScopePicker
• Execution modes: Manual, Scheduled, CLI, Background
• Overflow: Monitors, Reports, History, Configuration, Favorites, Change collection, Keyboard shortcuts
• Mock toolbar control

Bottom tabs

Console · Results · Variables · Cookies · Tests · History · Reports · Load · Monitors

How It Works (VS Code Extension)

1. Open Signoff Studio and switch to Runner, or run Signoff Studio: Run Collection / Run Request from the Command Palette / explorer commands.
2. Same Runner UI as Windows.
3. Scheduled/background monitors only fire while the webview panel remains open.

Code / Configuration Examples

CLI equivalent:

npm run runner -- run \
  -c ./collections/starter.signoff.json \
  -e httpbingo \
  --reporters json,html \
  -o ./out/report \
  -i 1 \
  --bail

Edge Cases, Troubleshooting & Pro-Tips

• Select the correct environment before Run so

  {{baseUrl}}

  resolves.
• Start with one folder for a shorter first pass.
• PDF reports use the host

  htmlToPdf

  bridge.

GAP IDENTIFIED: Scheduled / always-on monitors prefer the Windows app (Microsoft Store). In VS Code, schedules acknowledge webview mode and only run while the panel is open. See Monitors & scheduler.

Next

• Load testing
• Monitors & scheduler
• Tests & scripts