When a vaping app usability report says “task completed,” what did the tester do?
Read the task hierarchy and scoring rule before comparing completion across scenarios.
No Vape · Updated

Find the task beneath the scenario name
Bracken and colleagues report a preliminary usability study of a research virtual reality application related to vaping. Its Table 1 shows one scenario as a hierarchy of tasks and lower-level interactions. Two raters recorded task completion, and a third reviewed the recording if they disagreed. This description concerns a research prototype distinct from the mobile app offered on this site.
A scenario label tells you the setting or objective. The task list tells you what the tester needed to do in the interface. Record the smallest item the paper treats as scored, then check whether it summarizes a major task, several clicks or completion of the whole scenario.
Sketch a fictional task tree
Imagine an invented software test with one scenario called “review an entry.” It has two major tasks, open an old entry and reach the details view. The first task involves selecting an item and confirming the selection. One person reaches the details view after pressing the wrong item and correcting it. A test could count the endpoint as achieved while still recording a navigation error.
A second person opens the entry but never reaches details. Write the endpoint and observed difficulty in separate columns. If the study offered optional routes, copy the stated rule about which route counts. Otherwise leave the scoring of unchosen branches unresolved instead of turning every unused option into a failed step.
Check the denominator in the summary
The VR report presents error percentages by scenario using calculations for each participant and then averaging across participants. Its table notes that scenarios have different numbers of major tasks. When you compare two reported percentages, check the task counts and averaging rule. An average of participant percentages answers a different question from a pooled count across all tasks.
Find the tutorial or practice arrangement as well. In the cited study the tutorial preceded the scenario tasks. Observed completion after instruction describes what people did under that setup. The paper needs separate evidence if a claim concerns someone navigating a different version without the same introduction.
Describe the interaction that was observed
Finish with the test version, scenario, scored unit and definition of completion. Then describe any documented errors or unresolved scoring detail. Satisfaction comments can complement those observations, but they describe a different part of the session. Keep any claim about regular app use or cessation separate from the observed interface activity.
Questions about this step
Can finishing a scenario coexist with a navigation error?
Yes, if the scoring rule records endpoint completion and errors separately. Confirm what the report actually counts at each level.
Sources and scope
Sources inform the guidance. The worksheets and examples are No Vape editorial suggestions, not tested treatments.
Written with AI assistance and checked against the cited sources. No clinical review is claimed. This guide covers practical planning, not individual medical treatment. How we research and write