<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Integration-Testing on DRM HSE</title><link>https://www.drmhse.com/tags/integration-testing/</link><description>Recent content in Integration-Testing on DRM HSE</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 15 Jul 2026 21:43:22 +0300</lastBuildDate><atom:link href="https://www.drmhse.com/tags/integration-testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Serializing SQLite Writes in a Parallel Rust Test Suite</title><link>https://www.drmhse.com/posts/battling-with-sqlite-in-a-concurrent-environment/</link><pubDate>Fri, 19 Dec 2025 10:00:00 +0000</pubDate><guid>https://www.drmhse.com/posts/battling-with-sqlite-in-a-concurrent-environment/</guid><description>&lt;p>We moved our SSO integration tests to SQLite because a local test run should not require a PostgreSQL service. The first version kept the PostgreSQL-era pool configuration: up to 100 connections, with the tests running across eight workers.&lt;/p>
&lt;p>The suite began failing with &lt;code>500 Internal Server Error&lt;/code> responses and &lt;code>Database busy&lt;/code> messages. The failures looked intermittent, but the underlying mismatch was straightforward: we had changed the database without changing our model of write concurrency.&lt;/p></description></item></channel></rss>