Writing on QA & automation
Deep dives into test automation, AI-powered QA, and how VigilQA works under the hood.
Why We Built VigilQA
Test suites that nobody trusts. Maintenance backlogs that grow faster than features. The real cost of brittle automation — and what a knowledge-base-first approach changes.
Read post →Bootstrapping Your Knowledge Base from Existing Documentation
How to use Extract from Document to turn Word specs, PDFs, and Markdown into a ready-to-use KB in under an hour — and what to review before you trust the output.
Reading a Test Failure: Five Artifacts That Accelerate Debugging
Traceback, screenshot, browser console log, API request/response log, Playwright trace — what each one tells you and how to use them without re-running the suite.
Change-Driven Coverage: Testing What Actually Changed
How the Service Registry connects backend code changes to coverage gaps — and why prioritising by what changed beats a flat list of 80 untested scenarios.
Structuring Your Knowledge Base for Maximum Accuracy
The three files that drive AI test generation — and what to put in each one so the agents produce tests that actually reflect your application.
How Locator Healing Works
A look inside the three-tier fallback system — from stored alternatives to AI-generated selectors — and why human approval is still the right call.
Setting Up VigilQA in GitHub Actions
The complete CI workflow — from storing your API key as a GitHub secret to getting pass/fail status on every pull request in under 15 minutes.
Flaky Tests vs Real Bugs: How to Tell Them Apart
The four failure categories VigilQA classifies — and the signals that distinguish an infrastructure flake from a genuine product regression.
What the OWASP VAPT Module Tests — and What It Doesn't
All ten OWASP Top 10 categories mapped to what automated scanning catches, what needs manual review, and how to use the compliance output.
Why We Kept Humans in the Loop
Fully autonomous AI testing sounds appealing. Here's why we deliberately chose not to build it — and why that makes VigilQA more trustworthy, not less.
API Contract Testing: Your OpenAPI Spec as a Living Test Suite
Functional API tests verify behaviour. Contract tests verify shape. You need both — and they're not the same thing.
Performance Testing Without the Complexity
What p50/p95/p99 actually mean, when load testing differs from stress testing, and how to set meaningful thresholds without a dedicated performance engineer.
What WCAG 2.1 AA Compliance Actually Requires
A practical breakdown of Level A and AA requirements — what they mean for your web app and how automated testing fits alongside manual review.
Visual Regression Testing: Catching UI Bugs Before Users Do
Pixel-diff screenshot testing catches the layout and rendering bugs that functional tests are blind to. Here's how to use it without drowning in false positives.