Your input helps us improve and shape the future of our platform.If you have feedback or want to suggest a new feature, please reach out in the following:
General feedback dialogs on the Tester H homepage
Feedback dialog shown at the end of an agent run in Tester H
Meetings with the H Company team after a few weeks of testing
Not at all. Tester H is designed for both manual QA testers and automation engineers. You can generate robust end-to-end tests directly from natural language prompts (including Gherkin-style Given/When/Then). The generated scripts follow best practices, so you can easily review, adapt, extend, or run them as-is with full confidence.
Tester H works with all modern web browsers and has no specific compatibility requirements. Simply visit https://www.testerh.ai/ using your preferred browser to get started.
Should I “Build your own” test suite or “Generate from text”?
Up to you! Tester H enables you to visually map out a journey in graph form or speed up the process by writing a short prompt defining the scope and actions that apply to the test. If you choose to write a text prompt, however, we recommend referring to our Best practices.
Can I run multiple test suites simultaneously using different URLs?
No. At the moment Tester H can only run one suite/graph per URL at one time. However, it is possible to create several suites and launch them at the same time to run simultaneous tests.
Can I reference dynamic content or changing elements?
Tester H cannot currently handle dynamic content in its test suites. Referring to dynamic content or changing elements may disrupt or fail your test. Please refer to our Testing recommendations and Prompt templates and examples for guidance on how to get the most out of Tester H.
Is there a way to see or edit the generated test script?
Yes! Simply return to the homepage to view existing test suites. Clicking on a test suite displays a detailed view of each journey you ran and the Edit test suite button enables you to modify a test suite. For more information, check out our Get started guide.
What happens if one step fails — does the test stop or continue?
Currently, a test that includes a failed step forces the test suite as a whole to stop. In the future, however, we plan to introduce hard vs. soft actions and assertions. This means that a hard action would stop and fail if not met, and a soft action would raise a warning but keep executing the test.