Skip to main content
What happens:Tests fail immediately or start on the wrong page.Why it matters:The Start URL is where Testavi begins your test flow—it must be complete and properly formatted.Correct example:Always include https:// and the complete URL.Screenshot2026 01 15at01 44 57Incorrect examples:
  • Missing protocol (https://) Screenshot2026 01 15at01 45 31
  • Incomplete URLs Screenshot2026 01 15at01 45 43
Always copy and paste the URL directly from the browser’s address bar.
What happens:Tests become semantically unclear or are misinterpreted.Bad example:Screenshot2025 07 05at11 01 54AMGood example:Screenshot2025 07 05at10 53 16AMSeparate verification and action into distinct steps.Rule of thumb:
  • Actions = things the test does (e.g., click, scroll)
  • Verifications = things the test checks (e.g., visible, present)
Keep them in separate steps.
What happens: Testavi can’t interpret “Go to URL” commands mid-test, causing scripts to fail.Bad example:Screenshot2025 07 05at11 54 00AMGood example:
  • Set the Start URL in your test’s settings Screenshot2025 07 05at11 54 57AM 1
  • Use actions for in-test navigation (e.g., click on navigation links) Screenshot2025 07 05at11 58 12AM
What happens:The agent only interacts with elements in view unless instructed otherwise. Tests may fail to locate off-screen elements.What to do:Explicitly include scroll steps before verifications or actions.Screenshot2025 07 05at12 09 50PMThe agent will also scroll to find out-of-viewport items, but specifying scrolls improves test stability. See Discrete Actions: Scroll.
Remember that the agent sees only what a human sees. Include scroll instructions to ensure consistent element visibility.

​
✅ Authoring Do’s & Don’ts

❌ Don’t✅ Do
Use incomplete or incorrect URLsUse full URLs including https://, copy directly
Mix actions and verificationsKeep actions and checks in separate steps
Use “Go to URL” mid-testSet the start URL in test settings
Omit scroll instructionsExplicitly include scroll steps before actions/verifications