How does TestWeaver compare to model-based test generation tools, such as Embedded Tester, Conformiq Qtronic, Rhapsody Automated TestGenerator and others?
Like formal verification, model-based test generation (MBTG) is based on a model of the system formulated in a restricted specification language, usually restricted to discrete models. TestWeaver does not need a complete model, since it relies on a simulation of the system. Moreover, TestWeaver is not restricted to Simulink, or to any particular specification language, nor is it restricted to the analysis of discrete phenomena. MBTG is useful for analyzing the properties of discrete models (and of software in isolation), but it is less useful for analyzing the properties of systems that include physical components and processes characterized by differential equations. Read more…
Related Questions
- How does TestWeaver compare to model-based test generation tools, such as Embedded Tester, Conformiq Qtronic, Rhapsody Automated TestGenerator and others?
- How does TestWeaver compare to tools doing static code analysis, such as PolySpace, Coverity and others?
- How does TestWeaver compare to test pattern / test vector generation tools?
