Posts tagged
#regression-testing
Checking that what worked yesterday still works after today's change.
4 posts
Running suites from CI and on a schedule, and keeping flaky tests honest
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.
Why we run a fix three times before we call it fixed
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.
From a failing run to a Jira ticket, and back
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.
What automation testing is, and why end-to-end suites decay
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.
