The scripter says two hundred issues are fixed. Somebody still has to look again, page by page, language by language. SurveyTester re-checks every fixed issue for you and tells you what looks fixed and what is still broken. You just confirm.
QA does not end when an issue is reported. Every fix needs a second look, and that second look is a large part of the testing work.
Every fixed issue means opening the survey, reaching the right page with the right answers and comparing it with what was reported. Fifty issues in three languages are a day of clicking.
Many issues sit deep in the survey, behind screeners, quotas and routing. Getting back to the exact page often means repeating the whole interview.
A status change says the fix was made, not that it works. Without a re-test, fixed issues reach the client unchecked.
The scripter sets the re-check status after the fix, one by one or in bulk. SurveyTester waits for the next capture of the issue's page, from any test run in that language, or starts a SurveyBot that replays the original interview up to that page.
The issue is checked the same way it was found, for example the same automatic check or the old and new text. The result is looks fixed, still present or please check manually, with the page before and after side by side.
Confirm fixed closes the issue, still broken sends it back to the scripter. The "What's next" menu collects what is left: start the re-check bots for all waiting issues, or reopen everything that is still broken at once.
Issues that came from an automatic check (spelling, wrong language, unresolved piping, visible HTML and more), text changes with an old and a new text, and project-wide findings such as rotation. Manually reported issues get a side-by-side comparison for a person to judge.
No. Any new capture of the page in the same language counts. If nobody tests it, a SurveyBot replays the original interview up to the page, with the same answers, test case, language and market.
Yes. In the browser extension, every issue under re-check asks "Is this solved?" right on the page.
Show us a project with open fixes, and we show you how the re-check handles them.
Some teams want to click around on their own. Some want a guide at their side. Some just want to know whether their survey is fine. All three are free, and none of them commits you to the others.
One of your real projects, set up and run together with a SurveyTester QA expert. Your team learns the tool on work that matters.
Request a pilot →Email us a survey link and the questionnaire. We test it with SurveyTester and send you a written report of what we found. No account needed.
Get your survey reviewed →14 days with every premium feature. Start on a demo survey or paste your own link, invite your team and explore at your own pace.
Start the 14-day trial →
Episode 1Max tested the main route. The client found the other 36.
Episode 2500 test interviews before lunch. Max tried it by hand.
Episode 3500 interviews from São Paulo. Nobody had to fly.
Episode 4A granny, a student and a businessman. All of them Clicky.
Episode 5Two hundred printed pages, one highlighter. Or one Clicky.
Episode 7Five percent changed. Who checks the other ninety-five?
Episode 8What is your zip code? Your bots need to know the country.
