# What Testmode records and who sees it

URL: https://testmode.ai/docs/what-testmode-records/

> What Testmode stores from your tests: screenshots, typed values, reasoning, console and network logs, and who in your organization can see them.

For each test, Testmode records a screenshot after every browser action, the agent's reasoning, a summary of the result, and the browser's console and network logs. Every member of your organization can see these records, Viewers included. Schedule email reports can also go to people outside your organization.

## What each test records

| Record | Where you see it | What it contains |
| --- | --- | --- |
| Screenshots | **Test Steps** and the screenshot viewer | The page after each action the agent took |
| Actions | **Test Steps** | What the agent did, for example `Clicked` or `Typed '…'` |
| Reasoning | An expanded row in **Test Steps**, and the screenshot viewer | Why the agent took that action |
| Summary | Under the verdict, or under **Failure reason** when a test fails | The agent's explanation of the result, or a system reason such as a failed login |
| Console logs | **Console** tab | Messages the page wrote to the browser console |
| Network logs | **Network** tab | Requests the page made |

If the agent reaches its verdict without taking any action, Testmode records a single `Observed the page` entry with a screenshot and the agent's reasoning.

The **Live Browser View** shows the browser only while a test is running. It isn't saved as a video, and there is no replay.

## Typed values and variables

**Test Steps** show what the agent typed. For example, "Login rejects an unknown email" records typing `nobody.demo@example.com`, the value of `{{Unknown Email}}`. The agent's reasoning and summary can also repeat values it saw on the page or entered.

Variable values are plain text. Every member of the organization can read them under **Settings** > **Variables**, and they show up in recorded steps when a test types them.

**Tip**

Keep passwords out of variables and steps. Store them in credentials instead.

## Logs include login traffic

Console and network logs cover the requests and console messages the browser reported during a test, including any login pages it went through.

The **Network** tab shows each request's **Status**, **Method**, **URL** and **Type**. It doesn't show request or response headers or bodies.

## Passwords and credentials

Credential passwords are stored encrypted and aren't shown again after you save them. To change a password, you enter a new one.

Login actions aren't recorded under **Test Steps**. If a login fails, the "Login failed:" message has the username and password removed.

After a credential signs in, Testmode saves the browser's cookies and the site's local and session storage for that credential, so later tests and explorations can start signed in. The saved login is stored encrypted, and no member can view it in the app. Changing the credential's username or password clears it, and deleting the credential deletes it.

## Who can see results

Every member of the organization can open the runs, screenshots and logs of all its projects, whatever their role. Viewers see the same results as Owners.

Screenshots are served only to members of that organization. A link to a run opens only for someone who is a member.

## Email reports can leave your organization

A schedule can email a run report to any address you add, not only to members. A report includes:

- the test names and their statuses
- failure summaries for tests that didn't pass
- a link to the run, which opens only for members of the organization

Failure summaries can describe what the agent saw in your app. Check who is on a schedule's recipient list before you add outside addresses.

## What the Assistant and explorations read

**The Assistant.** When you attach a CSV or Excel file, the Assistant receives the column headers, the first 5 rows and the total number of rows. It doesn't receive every row. Its **Fetch Webpage** action can only read public web pages.

**Explorations.** An exploration records a screenshot and a description of each page it visits, plus the browser's console and network logs. Every member of the organization can see them.

## Keep sensitive data out of tests

- Use test accounts, not real customer or employee accounts.
- Put passwords in credentials, never in variables or steps.
- Avoid tests that show personal or payment data, because screenshots capture whatever is on screen.
- Check schedule recipients before you add addresses outside your organization.
- Run tests that create real data, such as orders or messages, only against environments meant for testing.

## Related

- [Read run results](https://testmode.ai/docs/read-run-results/): Find screenshots, reasoning and the failure reason.
- [Credentials and automatic login](https://testmode.ai/docs/credentials-and-automatic-login/): Store logins so passwords stay out of your tests.
- [Roles and permissions](https://testmode.ai/docs/roles-and-permissions/): What each role can see and change.
- [FAQ](https://testmode.ai/docs/faq/): Answers to common questions about Testmode.