<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>QaCockpit blog</title><description>Practical notes on TestOps, regression, and operating software quality.</description><link>https://qacockpit.app/</link><item><title>Introducing QaCockpit: a control plane for software quality</title><link>https://qacockpit.app/blog/introducing-qacockpit/</link><guid isPermaLink="true">https://qacockpit.app/blog/introducing-qacockpit/</guid><description>Why we are building a TestOps layer that connects existing test automation instead of asking teams to replace repositories, frameworks, or CI.</description><pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate><category>TestOps</category><category>Product</category></item><item><title>A green pipeline is not enough</title><link>https://qacockpit.app/blog/green-pipeline-is-not-enough/</link><guid isPermaLink="true">https://qacockpit.app/blog/green-pipeline-is-not-enough/</guid><description>A passed workflow can still hide missing tests, skipped scope, and weak evidence. Here is what a dependable regression signal needs to preserve.</description><pubDate>Fri, 24 Jul 2026 00:00:00 GMT</pubDate><category>Regression</category><category>Quality signal</category></item><item><title>Regression campaigns without replacing your CI</title><link>https://qacockpit.app/blog/regression-campaigns-without-replacing-ci/</link><guid isPermaLink="true">https://qacockpit.app/blog/regression-campaigns-without-replacing-ci/</guid><description>How a lightweight campaign model can coordinate existing GitHub Actions workflows while keeping execution, secrets, and test code in your repositories.</description><pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate><category>Campaigns</category><category>GitHub Actions</category></item></channel></rss>