Reading brand_tracker_Q3.docx
40 questions · 11 logic rules · 6 validations
Catch breaks before respondents do.
01 Go deeper
The most expensive bug in research is the one found after fieldwork starts. Aayvu's test mode lets you walk the survey exactly as a respondent would — taking every branch, triggering every validation.
Meanwhile the logic checker scans your rules for conflicts automatically, so broken routing never reaches the field.
02 Why it matters
Run the published experience with real controls, validations, messages, and branching.
Catch missing references, unreachable targets, invalid quotas, and logic cycles before launch.
Move from an issue to the exact question, rule, or validation that caused it.
03 In practice
A good QA pass combines automatic checks with a human run-through of the respondent experience.
Analyze the questionnaire for broken references, conflicting actions, and invalid configuration.
Answer as a respondent and deliberately trigger screeners, branches, quotas, and validations.
Return to the flagged rule, make the change, and repeat the path before publishing.
04 What’s included
Fill the survey with the same question controls used in the live form.
Check question, row, column, and answer-action dependencies.
Flag missing questions, variables, options, pipes, and quotas.
Surface circular visibility and hybrid column gating.
Exercise required fields, ranges, selection limits, patterns, and sum rules.
Keep editing without changing the live snapshot until you republish.
Start with the document you already have.