Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.qa.tech/llms.txt

Use this file to discover all available pages before exploring further.

The AI agent can navigate to URLs dynamically during test execution, without requiring static start URLs. This enables testing workflows where URLs are generated at runtime or vary based on test conditions.

​
When to Use

Dynamic navigation is useful for testing:
  • User-specific URLs (e.g., /users/{dynamicId}/profile)
  • URLs displayed on the page that need to be visited
  • URLs copied to the clipboard during the test
  • Relative navigation within the same domain (e.g., ../settings, /dashboard)

​
Supported Navigation Modes

ModeDescriptionExample
Full URLNavigate to complete web addresseshttps://example.com/page
Relative URLNavigate relative to current page/dashboard, ../settings, ?tab=profile
Clipboard URLNavigate to URL currently in clipboardCopy URL with keyboard shortcut, then navigate

​
How It Works

The agent automatically handles navigation when:
  1. Your test instructions mention navigating to a URL or visiting a link
  2. The agent encounters a URL it needs to visit during test execution
  3. URLs are dynamic - the agent adapts to whatever URL is present at runtime
No configuration required - the agent automatically determines which navigation mode to use based on the URL format and current page context.

​
Example Use Cases

Testing User Profiles

Goal: “Navigate to the newly created user’s profile page”The agent will:
  • Extract the dynamic user ID from the page
  • Construct and navigate to the profile URL
  • Verify the profile loads correctly

Testing Email Links

Goal: “Copy the verification link and visit it in the browser”The agent will:
  • Copy the link to the clipboard
  • Navigate to the clipboard URL
  • Verify the verification page loads

Testing Relative Navigation

Goal: “From the product page, navigate to the shopping cart”The agent will:
  • Navigate relatively from current page (e.g., ../cart)
  • Handle relative paths without needing full URLs

​
Technical Details

Navigation Requirements:
  • Full URLs: Must use http://, https://, or file:// protocol
  • Relative URLs: Requires an active page (cannot navigate relatively from about:blank)
  • Clipboard URLs: Clipboard must contain a valid web address
Error Handling: The agent provides clear error messages when:
  • Clipboard is empty when attempting clipboard navigation
  • Relative URL is used without a current page loaded
  • URL format is invalid or uses unsupported protocols
Related: See Email Inbox for navigating to links in test emails.