However, the following article is intended primarily as a guide to common concerns regarding model-based testing, discussing the ways in which we’ve responded to them in Test Modeller. All the features discussed draw on Curiosity’s decades of collective experience in building model-based solutions. Each has been designed to remedy common challenges when implementing model-based test design, shortening it’s time to value while amplifying its benefits.
The features discussed in this article, I hope, will therefore give you some food for thought around the role of modelling in software delivery, while also highlighting some technologies that we think are pretty new and exciting.
The article then concludes by asking a big question: Is it time to leave the word ‘model’ behind, embracing language more befitting of today’s technologies? We’d love to hear from you on this question – please take a minute to vote in our poll, letting us know what you think!