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 — What each test outcome means, and the context Semaloop gives you to understand what happened.
  • 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.