<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Testing on BurrowedInCode</title><link>https://burrowedincode.dev/tags/testing/</link><description>Recent content in Testing on BurrowedInCode</description><generator>Hugo</generator><language>en-us</language><copyright>BurrowedInCode</copyright><lastBuildDate>Tue, 10 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://burrowedincode.dev/tags/testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Integration Testing with Go and PostgreSQL</title><link>https://burrowedincode.dev/posts/integration-test/</link><pubDate>Tue, 10 Nov 2026 00:00:00 +0000</pubDate><guid>https://burrowedincode.dev/posts/integration-test/</guid><description>&lt;h1 id="integration-testing-with-go-and-postgresql"&gt;Integration Testing with Go and PostgreSQL&lt;/h1&gt;&#10;&lt;p&gt;Testing is an important part of software development; it helps verify that your code behaves as intended. Software tests come in many flavors: unit tests, integration tests, system tests and more. You may be familiar with unit testing, which tests individual components—such as functions or methods—in isolation, using assertions to check their behavior. Writing tests helps expose flaws in your logic and identify opportunities for improvement.&lt;/p&gt;</description></item></channel></rss>