<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Blog | VibeQA</title>
<link>https://vibeqa.mintera.world/en/blog/</link>
<description>Notes from the VibeQA team on test design, re-verifying fixes and running tests you can trust.</description>
<language>en</language>
<atom:link href="https://vibeqa.mintera.world/en/blog/rss.xml" rel="self" type="application/rss+xml"/>
<lastBuildDate>Wed, 07 Oct 2026 00:00:00 GMT</lastBuildDate>
<item><title>Running suites from CI and on a schedule, and keeping flaky tests honest</title><link>https://vibeqa.mintera.world/en/blog/ci-schedules-and-flaky-tests/</link><guid isPermaLink="true">https://vibeqa.mintera.world/en/blog/ci-schedules-and-flaky-tests/</guid><pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate><description>Gate pull requests on VibeQA, run every suite nightly, hear about new failures, and handle flaky tests in CI with history and quarantine, not by hiding bugs.</description><category>CI/CD</category><category>Flaky tests</category><category>Regression testing</category></item>
<item><title>Why we run a fix three times before we call it fixed</title><link>https://vibeqa.mintera.world/en/blog/reverify-three-runs/</link><guid isPermaLink="true">https://vibeqa.mintera.world/en/blog/reverify-three-runs/</guid><pubDate>Sun, 04 Oct 2026 00:00:00 GMT</pubDate><description>One green run can be luck. VibeQA runs the repro test three times to verify bug fixes, then turns the outcomes into one verdict. Here is what each one means.</description><category>Jira</category><category>Flaky tests</category><category>Regression testing</category></item>
<item><title>From a failing run to a Jira ticket, and back</title><link>https://vibeqa.mintera.world/en/blog/defects-and-jira/</link><guid isPermaLink="true">https://vibeqa.mintera.world/en/blog/defects-and-jira/</guid><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><description>Jira defect tracking with a repro test: how a failing run becomes a Jira Bug, what VibeQA writes on the ticket, and where the Jira connection stops today.</description><category>Jira</category><category>QA process</category><category>Regression testing</category></item>
<item><title>A red run should mean your app is broken</title><link>https://vibeqa.mintera.world/en/blog/infra-failure-is-not-a-test-failure/</link><guid isPermaLink="true">https://vibeqa.mintera.world/en/blog/infra-failure-is-not-a-test-failure/</guid><pubDate>Mon, 28 Sep 2026 00:00:00 GMT</pubDate><description>Test failure vs infrastructure failure: why VibeQA gives a run six outcomes instead of pass and fail, shows its own errors in violet, and retries only those.</description><category>Flaky tests</category><category>End-to-end testing</category><category>Automation testing</category></item>
<item><title>What happens when you press run</title><link>https://vibeqa.mintera.world/en/blog/running-your-tests/</link><guid isPermaLink="true">https://vibeqa.mintera.world/en/blog/running-your-tests/</guid><pubDate>Fri, 25 Sep 2026 00:00:00 GMT</pubDate><description>How VibeQA runs end-to-end tests: the queue, a fresh sandbox per run, test accounts whose passwords Tokay never sees, and where to look when a test fails.</description><category>End-to-end testing</category><category>Playwright</category><category>Automation testing</category></item>
<item><title>Reviewing a test design with Tokay</title><link>https://vibeqa.mintera.world/en/blog/reviewing-with-tokay/</link><guid isPermaLink="true">https://vibeqa.mintera.world/en/blog/reviewing-with-tokay/</guid><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate><description>What test case review looks like in VibeQA: hand edits, @Tokay comments that come back as suggestions, &quot;Looks right&quot; per case, and the checks before approval.</description><category>Test design</category><category>QA process</category><category>AI in testing</category></item>
<item><title>Design the tests first, write the code second</title><link>https://vibeqa.mintera.world/en/blog/design-tests-before-code/</link><guid isPermaLink="true">https://vibeqa.mintera.world/en/blog/design-tests-before-code/</guid><pubDate>Sat, 19 Sep 2026 00:00:00 GMT</pubDate><description>Test case design before code: how Tokay turns a requirement into a table of cases you can review, and how VibeQA measures coverage by a fixed rule.</description><category>Test design</category><category>AI in testing</category><category>QA process</category></item>
<item><title>From sign-up to the first run</title><link>https://vibeqa.mintera.world/en/blog/from-sign-up-to-first-run/</link><guid isPermaLink="true">https://vibeqa.mintera.world/en/blog/from-sign-up-to-first-run/</guid><pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate><description>How to set up automated testing for a web app in VibeQA: sign in with a link, create a project, let Tokay draft suites, review them and start a first run.</description><category>VibeQA</category><category>QA process</category><category>End-to-end testing</category></item>
<item><title>What is different about VibeQA</title><link>https://vibeqa.mintera.world/en/blog/what-is-different-about-vibeqa/</link><guid isPermaLink="true">https://vibeqa.mintera.world/en/blog/what-is-different-about-vibeqa/</guid><pubDate>Sun, 13 Sep 2026 00:00:00 GMT</pubDate><description>What sets VibeQA apart from other AI testing tools: you review a test design, a person approves every version, and a red run means your app broke.</description><category>VibeQA</category><category>AI in testing</category><category>Test design</category></item>
<item><title>Meet VibeQA and Tokay</title><link>https://vibeqa.mintera.world/en/blog/meet-vibeqa/</link><guid isPermaLink="true">https://vibeqa.mintera.world/en/blog/meet-vibeqa/</guid><pubDate>Thu, 10 Sep 2026 00:00:00 GMT</pubDate><description>VibeQA is AI test automation for web apps: Tokay drafts the test design and the code, people approve both. The whole loop, from Jira ticket to verified fix.</description><category>VibeQA</category><category>AI in testing</category><category>Automation testing</category></item>
<item><title>What automation testing is, and why end-to-end suites decay</title><link>https://vibeqa.mintera.world/en/blog/what-is-automation-testing/</link><guid isPermaLink="true">https://vibeqa.mintera.world/en/blog/what-is-automation-testing/</guid><pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate><description>Automation testing explained: what unit, API and end-to-end tests each check, what they buy you, and why browser suites so often stop being trusted.</description><category>Automation testing</category><category>End-to-end testing</category><category>Regression testing</category><category>Flaky tests</category></item>
</channel>
</rss>
