# Understanding test results

> What a Semaloop test run tells you — outcomes, history, skills, notifications, debugging failures and giving feedback.

Rendered version: https://docs.semaloop.com/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**](/test-results/reading-results/) — What each test outcome means, and the context Semaloop gives you to understand what happened.
* [**Viewing previous results**](/test-results/viewing-previous-results/) — How to look back at previous test runs and build history.
* [**Skills**](/test-results/skills/) — How Semaloop agents learn and reuse repeatable routines across runs.
* [**Test notifications**](/test-results/notifications/) — The ways Semaloop can tell you a test run finished — Slack, GitHub pull request checks, and webhooks.
* [**Debugging failures**](/test-results/debugging-failures/) — How to investigate and fix a failure, in the dashboard or via the MCP server.
* [**Feedback on test runs**](/test-results/feedback/) — How test and skill feedback help Semaloop agents improve over time.

## Related

- Index of every Semaloop docs page: https://docs.semaloop.com/llms.txt
- All Semaloop docs in one file: https://docs.semaloop.com/llms-full.txt