Skip to Content
Raydo

Test a browser form workflow

Run a read-only browser path first, then configure a test submission with approval and read-back.

Use a staging page with a test account and a disposable form record. In connection settings, check that the browser route is ready in the project and supports the actions you plan to use. For an authenticated path, use the intended test session.

Open the page and inspect it

  1. Create a test workflow and remove any default read or delivery steps. Remove the default topic input if unused. Add a Capability step. Under Connected apps and channels, select the granted Browser Automation operation for browser.navigate. Declare the run input portalUrl as a required string and map the node’s url to $.run.input.portalUrl.
  2. Connect the granted browser.observe operation. For a public test page, map its url to the same run input. For a logged-in test, use the same provider and connected tab or session. If you are choosing the provider explicitly, add a string providerId and map it to both steps. For example, use raydo-headless for a stateless public page when this provider is ready.
  3. Activate the flow and start it in the test project with your staging URL. In the run trace, compare the actual URL, title, session, and observed fields. If the provider cannot reach the requested page or session, resolve the browser binding before testing writes.

Extend the test to filling and submission

  1. Add a browser.type step per field or a supported form-fill operation. Configure target descriptors from the test page. Use dummy text and verify which fields autosave. Before enabling an upload, confirm the route supports browser.upload_file and stage a disposable file as an accessible artifact.
  2. Add a Review gate before the first action that can write externally. Show the pending text, file, destination, and account in the approval context. Add a separate gate before submit if preparing the form and committing it are different decisions.
  3. Configure browser.submit_form with the actual test target and a review summary. For the Chrome extension route, set postActionVerification with expectedText or expectedUrlIncludes that uniquely identifies the success state. Verify the returned receipt and record before capturing a screenshot.
  4. If preparation requests a native file chooser handoff or submission has an uncertain result, stop and inspect the browser and target system. Continue only after you can tell what actually happened.

The browser node guide explains route requirements. For a longer walkthrough, see demo playbooks.

On this page

Test a browser form workflow