You use stubs both in testing and development if there is no backend API ready. Simple stubs are sufficient for the development, while this is not enough for the testing.
Looking at the enterprise, you wil not often see this kind of stubs in testing, usualy there is quite functional test environment if possible. As a worst case - no test env at all.
Using simple stubs invalidates your business process tests as you might skip many variations of the flow. Developing a full functional stub is quite a task and often is not an affordable solution
HP Service Virtualization Software was designed to overcome those constrains, without development skills, with multiple protocol and data formats support, with data and performance models support, so you can learn the behaviour of a real service from data and performance perspectives.
That is what will be shown and discussed here.