There are many benefits to the model-based testing approach. Some of them were mentioned above but we summarized the main ones in this section.
Once the scope of the coverage has been defined and agreed, it is very easy to follow the project execution, see what is left to be performed and size the efforts.
It is necessary in some businesses to have a range of test tools available to test the same specifications. This innovative solution makes this simple to achieve.
Initial states required to launch each test is fully integrated and known by the model! This way the model prevents ending a test with a System Under Test which is not reverted to the same initial state. It makes running tests in any order very simple to achieve and little place for errors.
Moreover, the choice of reverting the SUT to the initial state is not let to the test tool vendor.
Test scenarios that you can see in the readable test plan (html, pdf, …) is exactly the same as the test scripts because they have the same source, the model. So when you read a test to analyse a log, you have the exact same content in both formats.
You never have to wonder if your test plan expectations are actually correctly implemented!
In case a specification update is light, it is possible to perform the change in the model and simply ‘reproduce’ the tests before they can be rerun. Additionally you do not have to worry whether the update was reflected everywhere or not, the model takes care of this.
Cherry on the pie, it also tells you precisely all that has changed between any 2 deliveries so you can control your expectations.
Thanx to model-based testing, Mellonne’s tooling and experience, project maintenance is very cost-effective. A side effect is that time frames can be short when necessary.