Skip to content
Semaloop Docs

Understanding test results

Every test run ends in an outcome, with the context behind it: video, a trace of what the agent did, system logs and network traffic. These pages cover how to read that, where to be notified, and how to act on a failure.

  • Reading test results — Every Semaloop test run ends in success, failure or error, with a timeline, video, logs and network activity behind it. This page explains each.
  • The test run view — How the test run page is laid out around the recording, how to move through a run, and how to switch back to the classic view.
  • Build summaries — A short written summary of how each build did compared with the build before it, on the build page and in Slack.
  • Ask — Ask questions in natural language about an app's builds, tests and runs, and get a short answer that links to where it came from.
  • Viewing previous results — How to look back at previous test runs and build history.
  • Skills — How Semaloop agents learn and reuse repeatable routines across runs.
  • Test notifications — The ways Semaloop can tell you a test run finished — Slack, GitHub pull request checks, and webhooks.
  • Debugging failures — How to investigate and fix a failure, in the dashboard or via the MCP server.
  • Feedback on test runs — How test and skill feedback help Semaloop agents improve over time.