Effectively Test Spring's RestTemplate with @RestClientTest

[@rieckpil]

If you encounter any issue while running the test, try to remove the @Bean CommandLineRunner from the main application class. I forgot to mention this

[@msraju2326]

Thanks

[@tiyasha01]

Hi,how can i test timeout set on resttemplatebuilder,that we should have Connect Exception if timeout is exceeded?

[@AmNotLegend]

is this @RestClientTest used for testing third party API? then what we can conclude from mocked responses?

[@rieckpil]

the @RestClientTest can be used to test HTTP clients that access a third part API. Testing the third party API itself is hard to achieve and the responsibility of the third party I would say. The benefits of this approach (over extensive mocking when writing classic unit tests for such HTTP clients) are: testing error scenarios (HTTP 500), verify the serialization works as expected, test fallback scenarios, etc.

[@AmNotLegend]

@@rieckpil good explanation; thanks

[@mrowox]

What if I wasn't using getForObject but instead using exchange? How do I test that?

[@rieckpil]

that doesn't matter at all as we're mocking on the HTTP level.

[@SirWolf2018]

Cool, but if you don't static import your DSL static methods, then you just add painful verbosity. You can recognize a need for a static import when the name of the class does not add anything to the meaning of the method name.

[@rieckpil]

I'm not sure why you copied the same comment four times, but thanks for the hint :) I explicitly picked the non-static import to avoid (especially for Java newcomers) confusion to understand where this method is coming from immediately. I'm also favoring the static import for my day-to-day projects to make it as concise as possible.