CPT tutorial: #3 Motivation for CPT

Constrained Path-based Testing (CPT) tutorial – Part #3: Motivation for CPT. Why isn’t basic path-based testing always enough? In this video, we focus on the key motivations behind moving toward Constrained Path-based Testing (CPT). Although simple models are easy to create and understand, they often fail to reflect real-world testing conditions. Test paths may become unfeasible due to hidden system states, creating a semantic gap between the model and actual system behaviour. At the same time, practical constraints — such as limited resources, costly operations, system outages, or shifting test priorities — require testers to make informed decisions about where tests should go, where they should not go, and how often certain parts should be tested. We show that these challenges cannot be effectively addressed with basic models alone, yet upgrading to more complex formalisms is not always practical or desirable, mostly due to the involved costs. This creates a clear need for a middle-ground approach — one that allows testers to explicitly guide test paths without overcomplicating the model. This need is exactly what motivates the development of the CPT. If you are not familiar with state machines, get the basic idea at:  https://en.wikipedia.org/wiki/Finite-state_machine Then a detail of Extended State Machines might require more reading: https://en.wikipedia.org/wiki/Extended_finite-state_machine