What details are recorded during runs?
Every session can capture screenshots, DOM snapshots, network payloads, and console streams from isolated Chromium test nodes.
Security
Security and Trust
TimetoTest is engineered for high-security environments, prioritizing isolated sandboxes, least-privilege scoping, and complete visibility.
Security Principles
- Least-privilege integration access for user source and sandboxes.
- Comprehensive evidence traces on every virtual browser run.
- Continuous control validation with documented compliance checks.
Transport & Storage Protection
- TLS-protected network communication for all app and user traffic.
- Cloud-hosted database systems with AES-256 standard encryption.
- Secure credential mapping inside scoped, isolated customer boundaries.
Access Governance
- Strict role-based project ownership parameters on evidence logs.
- Tokenized access parameters for CLI triggers and API execution.
- Immutable audit logs detailing teammate changes and runs.
Traceability & Artifacts
- Runs are fully recorded with screenshots, console, and network logs.
- Triage results are scoped strictly within the project limits.
- Prompt modifications and run logs are preserved for audits.
Disclosure & Compliance
- Identified defects and security vulnerabilities are triaged in hours.
- System controls undergo regular automated audits.
- Continuous security roadmaps guide internal package updates.
Security FAQ
How is repository access scoped?
Access is strictly scoped using secure access tokens and integrations, so the QA agent only observes what you configure.
Where do runner sandboxes execute?
All browser runs execute within isolated, zero-trust cloud nodes which are wiped immediately upon completion.