When MBT fails … Call for MBT Failure Stories
although we are convinced that model-based testing is the state of the art in test automation with great opportunities for quality improvement or test effort reduction, it is often hard to convince people to invest in this technology. Even teams that are convinced that this technology works find it hard to convince other teams (in the same company). We already collected several case studies that show the positive impact of introducing and applying MBT.
However, recent surveys show that only a minority of all testers apply model-based testing or even consider it a promising approach. Are we (the MBT Community) just trapped in the confirmation bias?
Now what is the problem? Like for all tools and techniques, MBT also only works if it is applied in a correct way (see Robert Binder’s comment). Are there anti-patterns or operating errors that can lead to an MBT failure? While this is theoretically possible (and also published as scientific papers), we are not aware of any real failure story of MBT. Is it because one should/can/must never publish a failure story? Or are there no failure stories? Then what is it? Technical hurdles? Tool integration issues? Modeling languages? …?
We encourage you to provide real failure stories or experienced issues about MBT. If you have some of them: What are the reasons for failure? Did you analyze it? We would be very interested in such results – even if they are somehow incomplete or anonymized … many thanks in advance. You would do the MBT Community a big favor!
Remember – the MBT Community needs you!