<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Integration Tests for WebClient with WireMock	</title>
	<atom:link href="https://blog.codersee.com/integration-tests-webclient-wiremock/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.codersee.com/integration-tests-webclient-wiremock/</link>
	<description>Kotlin &#38; Backend Tutorials - Learn Through Practice.</description>
	<lastBuildDate>Wed, 16 Apr 2025 04:49:36 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Frank Neblung		</title>
		<link>https://blog.codersee.com/integration-tests-webclient-wiremock/#comment-105</link>

		<dc:creator><![CDATA[Frank Neblung]]></dc:creator>
		<pubDate>Wed, 06 Mar 2024 13:11:24 +0000</pubDate>
		<guid isPermaLink="false">https://codersee.com/?p=9508747#comment-105</guid>

					<description><![CDATA[Hi Piotr,

thanks a lot for this article. As always, it&#039;s a pleasure to read. I gained many insights on how to access the GitHub-API and how to configure and integration-test SpringBoot applications.

The Wiremock-Part, however, didn&#039;t convince me. In my opinion wiremock&#039;s fluent API leads to verbose testcode and a low signal/noise ratio.
Also I&#039;m ambivalent about the usage of json files found in `src/test/resources`. On the one hand, one can easily record actual output from github.com and paste it into a resource file. On the other hand, to validate the test&#039;s behavior, one has  to switch editors and must ignore almost all lines in `list_github_repositories_200_OK_page_1.json`.

In the case, you are interested in alternative approaches to testing, feel free to check out [my repository](https://github.com/neblung/webclientinttest)

Best regards
Frank]]></description>
			<content:encoded><![CDATA[<p>Hi Piotr,</p>
<p>thanks a lot for this article. As always, it&#8217;s a pleasure to read. I gained many insights on how to access the GitHub-API and how to configure and integration-test SpringBoot applications.</p>
<p>The Wiremock-Part, however, didn&#8217;t convince me. In my opinion wiremock&#8217;s fluent API leads to verbose testcode and a low signal/noise ratio.<br />
Also I&#8217;m ambivalent about the usage of json files found in `src/test/resources`. On the one hand, one can easily record actual output from github.com and paste it into a resource file. On the other hand, to validate the test&#8217;s behavior, one has  to switch editors and must ignore almost all lines in `list_github_repositories_200_OK_page_1.json`.</p>
<p>In the case, you are interested in alternative approaches to testing, feel free to check out [my repository](<a href="https://github.com/neblung/webclientinttest" rel="nofollow ugc">https://github.com/neblung/webclientinttest</a>)</p>
<p>Best regards<br />
Frank</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Page Caching using Disk: Enhanced 

Served from: blog.codersee.com @ 2026-02-25 18:52:02 by W3 Total Cache
-->