In the discussion of #37, @agoncal mentioned that the Azure SDK integration tests are executed against a test proxy, which will record the real http request/response in record mode and return the specific recorded response in playback mode. The benefit of this approach is obvious which can greatly save cost especially there're a lot of dependent Azure services.
The similar approach can be applied to Quarkus Azure Service extensions as they are built on top of Azure SDK. Details pls see:
In the discussion of #37, @agoncal mentioned that the Azure SDK integration tests are executed against a test proxy, which will record the real http request/response in
recordmode and return the specific recorded response inplaybackmode. The benefit of this approach is obvious which can greatly save cost especially there're a lot of dependent Azure services.The similar approach can be applied to Quarkus Azure Service extensions as they are built on top of Azure SDK. Details pls see:
37