top of page
Frequently asked questions
• High-level modeling accelerates test automation and supports in-sprint test automation
• Our new modeling technique detects more bugs
• Manual testers can use it as Harmony doesn’t require coding – all competitor tools do
Our techniques are provable better than traditional ones, read Modern Software Testing Techniques (https://www.amazon.com/Modern-Software-Testing-Techniques-Developers-ebook/dp/B0CKSDDT8K)for details.
Non-model-based testing tools apply no or ad-hoc test design, resulting in poor-quality software. Traditional models can be stated when the application is ready. Some coding is also required. The tools support either stateless or stateful solutions, but not both. Modeling the output is difficult as at a given node more values can occur. None of these problems happen for using Harmony.
A basic test design knowledge is necessary to make the abstract model. Using our user guide is usually enough. You can solve tricky exercises here (https://test-design.org/practical-exercises/)or you can learn more by reading our book.(https://www.amazon.com/Modern-Software-Testing-Techniques-Developers-ebook/dp/B0CKSDDT8K)
bottom of page