Please refer to our FAQs for any troubleshooting help you may need.
These questions and answers are based on general topics related to the Tester H.
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:
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.
These questions and answers are based on product-specific topics related to Tester H.
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.
You can create multiple branches, or actions, using the following button:
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.
No. Tester H enables you to create and save as many test suites as you want.
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**.**
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.
Not at the moment. However, we plan to make test suites reusable across tests in the future.
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 action/assertion (hard should stop and fail if not meet, soft should raise a warning and keep executing the test)
Not at the moment. However, we’re currently working on implementing this capability.