Everything Testmode records belongs to a project, and every member of that project’s organization can read it, Viewers included. The exceptions are credential passwords, which nobody can read back, the live browser, which only editors see, and your own conversations with the assistant.
What is recorded
Section titled “What is recorded”| Record | What it holds | Kept |
|---|---|---|
| Test cases | Name, steps, Expected Outcome, settings, and the browser operations each step was compiled to | Until deleted |
| Runs and tests | Who or what started the run, the environment, each test’s status, duration and summary | Until the project or environment is deleted |
| Step timeline | Each operation a test ran: what it did, its outcome, the page URL, and the step’s wording at the time | With the run |
| Failure screenshots | One screenshot of the page when an operation fails | 90 days, or until the test’s run is deleted |
| Session replay | The recording of each test’s and exploration’s browser | 31 days |
| Console and network logs | Up to 500 console messages and 1,000 requests per test; secrets removed from URLs | With the run |
| Findings | Each failure of your app: the test, the step, the page, its triage and state | Until deleted with the project |
| Explorations | Each page visited: its URL without secrets, purpose, forms, actions and states; what it measured and tried; and the suggestions | Until deleted |
| The map | Every screen an exploration read, with its latest screenshot (replaced each time it is read again), the links between screens, the journeys and the product summary | Until removed from the map |
| Notes | What your team taught Self-driving, and the answers to its questions | Until deleted |
| Self-driving’s work | Its reviews, investigations and every tool it used, its Inbox items, and every change it made to the suite with what was there before | With the project |
| Assistant conversations | Your messages and its replies, with the tools it used | With the project |
| Credentials | Name, username, login URL; the password encrypted | Until deleted |
| Variables | Name, value, description | Until deleted |
| Billing history | Every credit added or used | With the organization |
What is kept out
Section titled “What is kept out”- Passwords are encrypted, never shown and never sent to AI models. The login step types them; the step timeline and logs never contain them.
- Secrets in URLs, such as tokens, codes and keys in query strings, are removed before logs and exploration pages are stored.
- Variable values are left out of test summaries, which also go to report emails, CI logs and AI agents.
Who sees what
Section titled “Who sees what”| Who | Sees |
|---|---|
| Members of the organization (all roles) | Everything in its projects, except passwords, the live view and other people’s own assistant conversations |
| Editors and above | Also the live browser of running tests and explorations |
| Everyone in the project | The conversation about an Inbox item, started with Ask about this |
| Report recipients | The report email; opening the run needs a membership |
| A connected Slack channel | Self-driving’s questions and verdicts, posted as threads |
| API keys and AI agents | Projects, environments, plans, test cases and runs; not credentials or variable values |
Related
Section titled “Related”Read run resultsWhere each record appears.
Roles and permissionsWhat each role can see and do.
Limits and defaultsHow long things are kept.