Every survey project runs the same loop: QA reports issues, the scriptwriter fixes them, and QA has to look again before the issues can be closed. This sandbox walks you through that loop with two versions of a demo survey for a museum association - one with errors, one corrected - and shows how SurveyTester takes the "look again" off your hands: fixed issues are re-checked automatically, the What's next button tells you what is left, and you only confirm the result.
It takes about 15 minutes. The background on how each kind of issue is re-checked is in Automatic re-check of fixed issues.
The two demo surveys
| Version | Link |
|---|---|
| With errors | https://www.feedback-experts.com/mrIWeb/mrIWeb.dll?I.Project=SANDBOX_MUSEUMSWITHERRORS |
| Corrected | https://www.feedback-experts.com/mrIWeb/mrIWeb.dll?I.Project=SANDBOX_MUSEUMSOFNEWYORKFINAL |
The first version contains typical mistakes - spelling errors, a broken image and more - that SurveyTester's automatic checks find on their own. The second version is the same survey with the mistakes fixed.
Before you start: the setup
The re-check builds on a few settings. An administrator makes them once; after that they apply to every project of the project type. In the sandbox you can play both parts, QA and scriptwriter, as long as your own role has the permissions of the QA role.
| Where | What to set | Why |
|---|---|---|
| Administration › Project Types › Classification Field Definitions | A Status field with the value Fixed, and Needs Re-check ticked for that value. The field also needs a value that closes the issue (Close Issue ticked) | Setting Fixed marks an issue for a re-check; Confirm fixed later sets the closing value |
| Administration › Project Types › Automatic Issue Detection Settings | For each automatic check, the classification values a finding gets when it is converted into an issue - an open status, never Fixed or a closing value | Converted findings must start as open issues, otherwise they are marked for a re-check or closed right away |
| Administration › Roles, role of your QA testers, area Issues | Can Use "What's next" and Can Answer Re-checks During Testing | The first shows the What's next button, the second the question Is this solved? in the browser extension |
| Administration › Roles, role of your scriptwriters | Can Use "What's next" switched off | Scriptwriters fix issues; deciding whether a fix works is QA's job |
| Issues page of each QA user | The column Re-check, added with the column selector | Shows the progress and the result of each re-check |
See Classification Fields and Roles and permissions for these screens.
Step 1: Create the project with the faulty survey
Open the project menu (☰) and choose Create New Project. Pick a folder and the project type you prepared, give the project a name such as "Sandbox re-check", and paste the first link as Survey Link:
https://www.feedback-experts.com/mrIWeb/mrIWeb.dll?I.Project=SANDBOX_MUSEUMSWITHERRORS
Choose English as default language and click Create Project.
Step 2: Test the survey and collect findings
Run one or more test runs: a manual test (Test Survey › Manual Testing) or a few SurveyBots (Test Survey › SurveyBot Testing). Choose English on the survey's language page - a re-check is always answered by a test in the same language as the issue. After each test run, SurveyTester's automatic checks look at every page and report what they find as findings.
Step 3: Add one or two issues by hand
Start another manual test and report one or two problems that no automatic check can judge, for example an image that does not fit the question, or a question text that is hard to understand. Report them from the browser extension as usual: it takes the screenshot and lets you mark the spot. See Creating A New Issue.
Step 4: Convert the findings into issues
Open Issues and click the button for the Auto-Detected Findings. Review the list and convert the relevant findings into issues - in the sandbox, simply all of them. The converted issues get the classification values from the Automatic Issue Detection Settings, so they start as open issues.
Step 5: Hand the issues to the scriptwriter
Set the project phase to Script Update Needed with the Project Phase drop-down on the Issues page. In a real project this tells the scriptwriter that a batch of issues is ready to be fixed. See Project Phase & Milestone.
Step 6: The scriptwriter fixes the survey
Now play the scriptwriter. The fixed script is published as a new survey: open Project Details › General and replace the Survey Link with the corrected version, then save:
https://www.feedback-experts.com/mrIWeb/mrIWeb.dll?I.Project=SANDBOX_MUSEUMSOFNEWYORKFINAL
Back on Issues, select all issues and set Status to Fixed with Bulk Edit. Then set the project phase to Ready for QC: the fixes are ready to be checked.
Step 7: See the issues wait for a re-check
Switch back to the QA role. The Re-check column now shows waiting for every issue: SurveyTester has opened a re-check request for each one and waits for a fresh capture of the issue's page in the corrected survey.
You can now re-check in two ways. Use the first for the converted findings and the second for the issues you reported by hand - or try both.
Option 1: Use "What's next"
Click What's next at the top of the issue list. The menu lists what is left to do:
- ... fixed issues wait for a re-check with the button Run SurveyBot re-check now. Click it and confirm: SurveyBots repeat the original interviews up to each issue's page on the corrected survey, and SurveyTester runs the same automatic check again on the new capture.
- ... manually reported issues wait for a re-check by a person, with the issue numbers. A bot cannot judge a problem described in your own words: click an issue and use Repeat test run to this page to look at the page yourself, or use option 2.
When the bots are finished, reload the issue list. The Re-check column and the issue details show Looks fixed for every issue whose problem is gone. Click Looks fixed to open the comparison: the page When reported next to the Re-check capture. Check it and click Confirm fixed to close the issue, or Still broken to send it back to the scriptwriter.
Option 2: Answer while testing
Start a new manual test in English on the corrected survey. When you reach a page with an issue under re-check, the browser extension's Issues window shows the question Is this solved? below the issue's description. Look at the page and answer:
- Yes closes the issue.
- No sets it back to an open status for the scriptwriter.
This is the natural way for the issues you reported by hand: you look at the page anyway.
What you have practised
- One status value, Fixed, starts the re-check - no extra step for the scriptwriter.
- Findings are re-checked by the same automatic check that found them, with one click in What's next.
- Issues reported by hand are re-checked by a person, either from the issue or directly while testing.
- SurveyTester never closes an issue on its own: the decision stays with QA.
Use the same loop in your next project: convert findings, hand them over with Script Update Needed, let the scriptwriter set Fixed and Ready for QC, and let What's next guide you through the re-check.