Navigate to a specific page inside your test
Users move between pages constantly while interacting with your application—from exploring content and submitting forms to completing purchases and reviewing histories. The Browser Go To step lets you control exactly where your test navigates next by directing the browser either to a relative path within the same domain or to a full, absolute URL anywhere on the web.
This is one of the most fundamental steps in any end-to-end flow because it determines the starting point for actions and assertions that follow. Whether you’re testing simple navigation or complex sequences, accurate control over URLs ensures your test runs reliably and predictably.
Navigate using relative paths
When your test needs to stay within the same site or domain, the relative path navigation keeps the context clean and consistent. Relative paths specify locations like:
/login
/dashboard
/products/12345
/checkout/confirmation
By using relative navigation, your automation can route directly to specific areas of your app without relying on previous clicks or steps. This is especially useful for:
Resuming a user journey at a particular screen
Jumping directly to a feature that needs testing
Avoiding unnecessary setup if a prior navigation has already been covered
Relative paths keep your flows concise and focused on what matters, and because they reference logical structure rather than full addresses, they adapt easily across environments like staging, QA, and production.
Navigate using absolute URLs
Sometimes you need to step outside your main application or hit a specific endpoint that isn’t part of the base domain. The absolute URL navigation lets you point the browser anywhere on the internet.
Examples include:
https://yourapp.com/login
https://partner.example.com/auth-callback
Third-party pages
Marketing content
Policy or documentation links
Absolute navigation gives you full control when your flow crosses domains or when testing redirect behaviours. Because it uses full URLs, it removes ambiguity about where the browser should land next.
Why direct navigation matters
While many tests build navigation step-by-step through clicks and interactions, direct URL navigation is often faster, more deterministic, and easier to maintain for specific flows. It reduces reliance on potentially flaky UI interactions and makes tests easier to read and reason about.
For example:
Jump directly to a user profile page to focus on profile update logic
Start a test on a specific onboarding step without repeating initial screens
Validate redirects, deep links, or marketing landing pages
Step into external services that your app depends on
Direct navigation gives you flexibility without sacrificing clarity.
Seamless integration with other steps
Once the browser lands on the target page, your test can continue with any of the available actions and assertions such as:
Touch to interact with buttons and links
Fill Input to enter text
Check Text and Check Value to validate UI state
Wait for Element to synchronise timing
Visual regression to confirm layout integrity
This means navigation becomes the reliable foundation upon which the rest of your automation is built.
Relative and absolute navigation steps make your test flows faster to write, easier to maintain, and more robust to UI changes. They allow your automation to focus on validating behaviour rather than struggling through brittle navigation sequences.