<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pytest on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/pytest/</link>
    <description>Recent content in Pytest on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 02 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/pytest/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Python Benchmarking: pytest-benchmark vs CodSpeed vs pyperf vs airspeed-velocity</title>
      <link>https://www.pistack.xyz/posts/2026-07-02-python-benchmarking-pytest-benchmark-codspeed-pyperf-asv/</link>
      <pubDate>Thu, 02 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-02-python-benchmarking-pytest-benchmark-codspeed-pyperf-asv/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Performance regressions are among the most painful bugs to diagnose. A function that was fast yesterday becomes slow today, and nobody knows why. Without systematic benchmarking integrated into your development workflow, performance degradation creeps in silently — one pull request at a time — until your application feels sluggish and your users notice before you do.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
