Testing a script

Start from the exact version you want to review. A ticket attached to an older version should be reproduced on that version before comparing a proposed fix.

Run the questionnaire

Open the project, select Versions, then open the script in the debugger. Answer questions and follow the routes relevant to the change. Check the question text, option labels, validation and routing—not just whether the script starts successfully.

The source and inspection tools help a scripter understand the current state. Other reviewers can concentrate on the interview itself.

An invented visitor survey running in the real questionnaire renderer. Check the question wording and options, select an answer, then use Continue to check the next step of the route.

Record a useful problem

Create a ticket while the problem is visible. Give it a specific title and describe the expected result, the actual result and any conditions that matter. The captured version and interview path provide reproducible context.

Do not include real respondent details, passwords or unrelated confidential material in descriptions or screenshots. Use invented test answers.

Check a proposed fix

Open the ticket and use its reproduction or candidate-testing controls. Compare the source changes, replay the captured journey, and test nearby routes that could also be affected. A successful replay is evidence for that route; it is not proof that every possible interview works.

If the fix is correct, resolve the ticket. If it is not, explain the remaining problem and reopen it. See Tickets and proposed fixes.

Keep the original evidence

Uploading a new version does not erase the earlier version or its tickets. Keep the original report intact so reviewers can understand both the defect and the reason for the correction.