Assume that you create a site & then some stumps for it. These stumps can be hit by your test automation, which is great.
Then imagine that you add another test case, but don't remember to add a stump for it. The way things work now is that Stumps will proxy/forward that request to the real web site/service. This could lead to technical testing debt - your test automation now accidentally depends on a real, live service, when you wanted it a stump.
We should be able to force a website into a "don't proxy stuff, only serve up the stumps" mode, and return a "404, there wasn't a stump for that" message for any unmatched request.
Assume that you create a site & then some stumps for it. These stumps can be hit by your test automation, which is great.
Then imagine that you add another test case, but don't remember to add a stump for it. The way things work now is that Stumps will proxy/forward that request to the real web site/service. This could lead to technical testing debt - your test automation now accidentally depends on a real, live service, when you wanted it a stump.
We should be able to force a website into a "don't proxy stuff, only serve up the stumps" mode, and return a "404, there wasn't a stump for that" message for any unmatched request.