<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Dmitrii Shakhov</title>
    <description>The latest articles on DEV Community by Dmitrii Shakhov (@dmitrii_s).</description>
    <link>https://dev.to/dmitrii_s</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1504995%2F27053ca4-fa00-4b79-9c13-ad5d3fa8f26f.jpeg</url>
      <title>DEV Community: Dmitrii Shakhov</title>
      <link>https://dev.to/dmitrii_s</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dmitrii_s"/>
    <language>en</language>
    <item>
      <title>I built a simple pytest plugin for test observability (need your help 😅)</title>
      <dc:creator>Dmitrii Shakhov</dc:creator>
      <pubDate>Wed, 27 May 2026 09:20:56 +0000</pubDate>
      <link>https://dev.to/dmitrii_s/i-built-a-simple-pytest-plugin-for-test-observability-need-your-help--2kgp</link>
      <guid>https://dev.to/dmitrii_s/i-built-a-simple-pytest-plugin-for-test-observability-need-your-help--2kgp</guid>
      <description>&lt;p&gt;Guys, I need your help 😅&lt;/p&gt;

&lt;p&gt;As I’ve noticed, many QA Engineers (also devs) do not measure how stable or fast their tests are. Even teams that do care about test observability often build their own internal tooling to analyze test statistics.&lt;/p&gt;

&lt;p&gt;People sometimes ask me how they can organize their own analytical system for test observability. But I never had a clear answer. Just "develop your own system". This approach might work for large teams, but it can be expensive for small and medium teams. Googling didn't help me. I could not find any tools that I would confidently recommend to others. And...&lt;/p&gt;

&lt;p&gt;I decided to create a simple solution for people who use Python and pytest. It is a pytest-plugin designed to improve test observability without requiring a TMS or other paid solutions. It exports test results into ClickHouse.&lt;/p&gt;

&lt;p&gt;Key features:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Automatic CI detection&lt;/li&gt;
&lt;li&gt;Allure report support&lt;/li&gt;
&lt;li&gt;Basic Grafana configuration provided out of the box&lt;/li&gt;
&lt;li&gt;No impact on pytest execution&lt;/li&gt;
&lt;li&gt;No additional overhead if export to ClickHouse is disabled&lt;/li&gt;
&lt;li&gt;Integrates with pytest&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I’m looking for people who can test it, provide feedback, and suggest feature requests. Let’s build a useful tool for the QA community together 🙃&lt;/p&gt;

&lt;h2&gt;
  
  
  How to test it locally
&lt;/h2&gt;

&lt;p&gt;If you want to see the dashboards, I added a docker-compose file so you don't need to configure a DB from scratch.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/shakhov-dmitrii/pytest-test-observer.git
&lt;span class="nb"&gt;cd &lt;/span&gt;pytest-test-observer
docker compose up &lt;span class="nt"&gt;-d&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then just install the plugin and run your tests:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pip &lt;span class="nb"&gt;install&lt;/span&gt; &lt;span class="s2"&gt;"pytest-test-observer[allure]"&lt;/span&gt;
pytest &lt;span class="nt"&gt;--ch-url&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;localhost:8123 &lt;span class="nt"&gt;--ch-table&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;pytest_results
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You can check the results in Grafana at &lt;a href="http://localhost:3000/d/pytest-test-observer-overview" rel="noopener noreferrer"&gt;http://localhost:3000/d/pytest-test-observer-overview&lt;/a&gt; (admin / admin).&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fsb1vivgibisyr31nu2ql.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fsb1vivgibisyr31nu2ql.png" alt=" " width="800" height="620"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Here is the repository: &lt;a href="https://github.com/shakhov-dmitrii/pytest-test-observer" rel="noopener noreferrer"&gt;https://github.com/shakhov-dmitrii/pytest-test-observer&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Having historical metrics for tests has been a massive quality of life upgrade, but I want to make it better.&lt;/p&gt;

</description>
      <category>qa</category>
      <category>python</category>
      <category>pytest</category>
      <category>ci</category>
    </item>
  </channel>
</rss>
