FaultPilot home
FaultPilot documentation
Browser Tests
Install the recorder, capture a real journey, configure safe test data, and schedule reliable replay.
Open in FaultPilot1
Before you begin
- Use a current Chromium-based browser.
- Install FaultPilot Interactive Recorder from the Chrome Web Store.
- Keep the FaultPilot recording page and target application tab open until recording stops.
- Use a dedicated non-production or synthetic account whenever possible.
2
Record a journey
- Open Browser Tests and choose Interactive Recorder.
- Enter the complete HTTP or HTTPS starting URL.
- Enable third-party frames and popups only when the journey requires them; Chrome will request broader temporary access.
- Acknowledge the privacy notice, start recording, complete the journey, and return to FaultPilot to stop.
3
Review and secure steps
- Remove accidental layout clicks and duplicate navigation steps.
- Reorder, disable, duplicate, or edit actions before saving.
- Mark credentials as private; FaultPilot replaces plaintext with an encrypted secret reference.
- File fixtures are encrypted and limited to three files and 2 MB total per recorded upload action.
4
Validate and schedule
- Run the recorded flow before saving or enabling a schedule.
- Confirm the runner is online and compatible.
- Review screenshot, video, step timing, selector healing, console, and network diagnostics.
- Choose a responsible schedule; queued tests may start late when the single browser worker is busy.
5
Supported boundaries
- Same-origin and opted-in cross-origin iframes, open Shadow DOM, popups, tabs, content-editable controls, and file inputs are supported.
- Closed Shadow DOM, browser-internal pages, operating-system dialogs, and canvas-only controls cannot be inspected reliably.
- Sites with bot challenges, mandatory device attestation, or restricted geographic access may require a different testing environment.