Was asking, because prior experience of model based system required upwards of 5 dedicated people to maintain the graph, leading to a bit of tension. I really liked the knowledge captured in a graph form, as it helped me know where to focus when designing an E2E test.
Most excellent blog explainer Sergio. Too often in these times of agile engineering, tools like MBT get ignored because they entail investment in new languages and tools. Anything that can create inertia gets discarded far too easily. Over time I got the impression it was really only good for regression testing. Turning the model into runnable test cases was costly because we wrote all or own frameworks and tools back then. My experience of MBT is that the detractors of it win in the end because it needs a champion who can continuously evolve the processes around the system every time a new challenge arises.
Although it’s a great place to learn about product interactions, for me it failed to draw in environment and hardware integrations/inter-op, like different browser versions or networks, that provided a much greater source of valuable defects discovered to us. Would love to see a “lite” version of this tooling to support ad-hoc or exploratory test sessions.