<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Test-Strategy on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/test-strategy/</link>
		<description>Recent content in Test-Strategy on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 10 Feb 2025 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/test-strategy/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Spring Boot Testing: What Should Actually Be Tested and How</title>
				<link>https://dplabs.tech/blog/spring-boot-testing-strategy/</link>
				<pubDate>Mon, 10 Feb 2025 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/spring-boot-testing-strategy/</guid>
				<description>&lt;p&gt;Spring Boot&amp;rsquo;s testing support is extensive and well-designed. It&amp;rsquo;s also easy to misuse in ways that produce slow, fragile test suites with poor diagnostic value.&lt;/p&gt;&#xA;&lt;p&gt;The core question is not &amp;ldquo;how do I test with Spring Boot?&amp;rdquo; but &amp;ldquo;what needs to be tested, and at what level?&amp;rdquo;&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-testing-pyramid-applied-to-spring-boot&#34;&gt;The Testing Pyramid Applied to Spring Boot&lt;/h2&gt;&#xA;&lt;p&gt;The testing pyramid principle: favor many fast, isolated unit tests over fewer slow integration tests. Each level of the pyramid is slower and more expensive to run but tests more of the system.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
