QA Ultimate Stack
Schedule tracking QA that fails loudly
Turn delivery checks, form validations and page-speed tests into scheduled runs that show as failed the moment a hit is blocked, a page goes silent or a form changes.
What each QA schedule does
- Network Requests Inspector: re-inspects saved pages. Any failed request, page error or page with zero collect hits makes the scheduled run fail.
- Synthetic Form Test: always runs in Validate mode, filling every field and confirming the submit button, but never submitting. Real submissions are never available to a schedule.
- Performance Test: re-measures saved pages so speed regressions show up between releases.
A list of what each QA schedule does, with real form submissions marked never scheduled.
A nightly delivery check
The most useful single schedule is a nightly Network Requests Inspector run across each brand's key pages: home, a product or service page, the main form and the confirmation page. A tag removed by mistake, a new security policy or a broken container shows up as a failed run the next morning, not at month-end.
A week strip with a nightly 02:00 run and cards for the pages checked and the failed-run behaviour.
A failed run is one glance
Because one failing page fails the run, the morning check is a single glance at Automation history. Open a failed run to see which page and which request, with the reason: a pixel refused by CSP, a page with zero hits, a 4xx from a proxy.
A scheduled run across six pages: four pass, one fails on a CSP-refused pixel and one on zero collect requests.
Triage a failed run in five steps
- Open the failed run in Automation history.
- Read the page diagnosis for each failed page: which page, which request, and why.
- Rule out the test machine first: a replaced tag library or a blocker that was switched on means the site may be fine.
- Route it: a CSP block goes to the site's developers; zero hits on a page goes to whoever owns the container or the consent setup; a 5xx from a server-side endpoint goes to whoever runs the server-side container.
- Re-run the same check by hand once the fix is live, and confirm it passes before the next night's run.
A five-step flow for triaging a failed scheduled QA run.
Conditions for scheduled runs
Scheduled runs are a Premium feature and run on your Windows computer: up to 10 a day, while the computer is awake and connected and ODDVX is running. A missed run is skipped, not queued. Run them from a machine without HTTPS-filtering security tools, or you'll get failures that aren't real.
A week of run history with four runs and one skipped day, plus the run conditions.
ODDVX for Windows
From the page to the hit, proved.
Start free with one saved form, one page and one parity check. Premium adds batch runs, exports and scheduled QA.