Our goal is to help you get the most out of TesterH. The tips and suggestions below are designed to help you extract as much value as possible from your test suites and prompts.

​
General guidelines

  • Keep the language simple. Write clear and unambiguous instructions.
  • Provide examples to help Tester H add context to your test suites.
  • Keep it short, the more concise your prompt, the easier it is to optimize TesterH.
  • Be specific, the more thorough your prompt, the better Tester H will perform.
DoDon’t
Break down tasks into small, explicit stepsAvoid high-level tasks like “Add iPhone 16 to cart”
Use quotation marks around text to inputDon’t write inputs without quotes
Use clear UI vocabulary: “button”, “navbar”, “input field”, etc.Don’t refer to elements vaguely
Be specific with location when multiple elements share a labelDon’t assume the agent will click the right one
Add scroll instructions when necessaryDon’t assume the agent will scroll automatically
Clearly separate “Given”, “When”, and “Then” logicDon’t write assertions based on unstable or temporary UI states
Only test public pages, or pass access tokens explicitly.Don’t rely on login state unless properly configured