given that the stubserver is started with command line argument "stub1.json stub2.json"
and files "stub1.json" and "stub2.json" are both on the classpath
when I do a HTTP GET to the endpoint as configured in "stub1.json"
then the response should be as configured in "stub1.json"
given that the stubserver is started with command line argument "stub1.json stub2.json"
and files "stub1.json" and "stub2.json" are both on the classpath
when I do a HTTP GET to the endpoint as configured in "stub2.json"
then the response should be as configured in "stub2.json"
given that files "stub1.json" and "stub2.json" are both on the classpath
and both "stub1.json" and "stub2.json" define the same endpoint
when the stubserver is started with command line argument "stub1.json stub2.json"
then the stubserver should not start successfully, giving a meaningful error message
given that the stubserver is started with command line argument "stub1.json stub2.json" and files "stub1.json" and "stub2.json" are both on the classpath when I do a HTTP GET to the endpoint as configured in "stub1.json" then the response should be as configured in "stub1.json"
given that the stubserver is started with command line argument "stub1.json stub2.json" and files "stub1.json" and "stub2.json" are both on the classpath when I do a HTTP GET to the endpoint as configured in "stub2.json" then the response should be as configured in "stub2.json"
given that files "stub1.json" and "stub2.json" are both on the classpath and both "stub1.json" and "stub2.json" define the same endpoint when the stubserver is started with command line argument "stub1.json stub2.json" then the stubserver should not start successfully, giving a meaningful error message