Skip to main content

Local Dashboard

StackTest includes a local-first dashboard for inspecting run history, deployment status, event timelines, and raw artifacts.

npx stacktest dashboard

The server binds to 127.0.0.1 by default and reads local files under .stacktest/runs. No test data is uploaded by the dashboard.

StackTest local dashboard showing run history with status filters

View Previous Runs​

After a run completes, open the dashboard and visit /runs. The run list supports status filters and text search across run ID, project name, provider, and regions.

Inspect A Run​

Open a run to see summary metrics, deployment metadata, failure details, and the execution event stream.

StackTest local dashboard showing a passed AWS CloudFormation run with event timeline

Failed runs highlight the failing deployment and provider event reason.

StackTest local dashboard showing a failed AWS CloudFormation deployment event

Watch An Active Run​

Use the dashboard integration when running tests:

npx stacktest run ./stacktest.yaml --dashboard

New normalized runs write events.jsonl, and the dashboard streams appended events with Server-Sent Events.

StackTest local dashboard showing a running multi-region test

Open Raw Artifacts​

The artifacts page lists files under the selected run folder and previews JSON, logs, and text files.

StackTest local dashboard showing the artifacts file browser

Mock Mode​

Use deterministic mock data for demos and documentation:

npx stacktest dashboard --mock --port 3456 --no-open

Options​

npx stacktest dashboard \
  --dir .stacktest \
  --runs-dir .stacktest/runs \
  --port 3456 \
  --host 127.0.0.1 \
  --no-open

Launch Tests From The Dashboard (opt-in)​

Browser-based launches are disabled by default. Enable them only on loopback:

npx stacktest dashboard --enable-actions --host 127.0.0.1

Then open Launch Test (/launch):

  1. Enter a config path under the current workspace (.yaml, .yml, or .json).
  2. Optionally set a provider override (for example fake for a local dry exercise).
  3. Click Preview plan, review the confirmation summary, then Deploy and Run Test.

Safety rules:

  • Requires explicit --enable-actions and a loopback bind host.
  • Disabled in --mock mode.
  • Config paths cannot escape the workspace root.
  • The API rejects launches without "confirm": true.
  • Prefer the CLI for routine work: stacktest run ./stacktest.yaml.

Troubleshooting​

If the port is already in use, choose another port:

npx stacktest dashboard --port 4567

If no runs appear, run a test first:

npx stacktest run ./stacktest.yaml

Older run folders may show partial details if they only contain legacy report files.