<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>rpytest Blog</title><description>Engineering notes on faster pytest: collection overhead, plugin compatibility, and CI time saved honestly.</description><link>https://rpytest.neullabs.com/</link><language>en-us</language><item><title>Measuring CI minutes saved, honestly</title><link>https://rpytest.neullabs.com/blog/measuring-ci-minutes-honestly/</link><guid isPermaLink="true">https://rpytest.neullabs.com/blog/measuring-ci-minutes-honestly/</guid><description>It is easy to publish a &apos;we are 3x faster&apos; number. It is harder to publish one that survives a skeptical reading. Here is the methodology we use for rpytest&apos;s CI benchmarks, the mistakes we used to make, and how to measure your own.</description><pubDate>Thu, 04 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Plugin compatibility: where drop-in claims usually break</title><link>https://rpytest.neullabs.com/blog/drop-in-plugin-compatibility/</link><guid isPermaLink="true">https://rpytest.neullabs.com/blog/drop-in-plugin-compatibility/</guid><description>Every faster-pytest tool says &apos;drop-in compatible.&apos; Most break somewhere. This post lays out where the breakage usually happens, how we built rpytest to host real pytest so most plugins just work, and what --verify-dropin actually checks.</description><pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate></item><item><title>What pytest&apos;s collection phase costs you</title><link>https://rpytest.neullabs.com/blog/pytest-collection-phase-cost/</link><guid isPermaLink="true">https://rpytest.neullabs.com/blog/pytest-collection-phase-cost/</guid><description>Collection is the phase between &apos;pytest started&apos; and &apos;pytest ran a test.&apos; It is also the phase most people are surprised to discover dominates their CLI wall clock. Here is what it actually does, why it is slow, and what removing it looks like.</description><pubDate>Thu, 21 May 2026 00:00:00 GMT</pubDate></item></channel></rss>