I built a simple pytest plugin for test observability (need your help π )
Dmitrii Shakhov has developed a pytest plugin aimed at improving test observability for QA engineers and developers. The plugin exports test results into ClickHouse and includes features like automatic CI detection and Allure report support. Shakhov is seeking feedback and suggestions from the community to enhance the tool further.
- βͺThe pytest plugin is designed to improve test observability without requiring a test management system.
- βͺIt integrates with pytest and exports results into ClickHouse.
- βͺShakhov is looking for users to test the plugin and provide feedback.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source Β· retrieval Β· rights Β· ranking β open for full record
inspect β
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/dmitrii_s/i-built-a-simple-pytest-plugin-for-test-observability-need-your-help--2kgp |
| Publication time | Wed, 27 May 2026 09:20:56 +0000 |
| Retrieval time | 2026-05-27T09:37:57.389Z |
| Last seen | 2026-05-27T09:37:57.389Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch Β· cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | KDSNTThhhW5- |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes β open original |
| Substitutes article? | No β link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 1504995) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Dmitrii Shakhov Posted on May 27 I built a simple pytest plugin for test observability (need your help π ) #qa #python #pytest #ci Guys, I need your help π 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. People sometimes ask me how they can organize their own analytical system for test observability.
β¦
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
