Timeline for When testing a prototype, do you inform your users that everything is not functional?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 31, 2017 at 8:23 | comment | added | Roux Martin | @Usbman, If you are testing a specific task then your questions and the task description shouldn't allow for anything that might unduly influence the test - You need to pick your wording and direction very carefully. This is true for any task-based testing. If your prototype is built correctly, your design is correct and your test is correctly designed then the user should be fully able to complete the task without hitting any non-functional areas. You can consider any non-functional hits as a failure of either the design or the test. | |
| Jan 30, 2017 at 23:26 | comment | added | Usbman | I agree with you, however for now we do the bulk of our testing on Usertesting.com which means we have no control over the script once the user starts the test. It gets super frustrating for both parties watching them click a button over and over again. I love your description though which I might try to communicate with the UX lead here. Thank you. | |
| Jan 30, 2017 at 18:46 | comment | added | Devin | +1, Exactly the same for me, nothing to add | |
| Jan 30, 2017 at 15:54 | history | answered | Roux Martin | CC BY-SA 3.0 |