Bureaucrats, emailconfirmed
1,221
edits
No edit summary |
No edit summary |
||
Line 228: | Line 228: | ||
* You need to think about a suitable context for your tasks. So don't just write: "import the pictures from the SD card into the Program" but something like "You are a Photographer and just finished shooting. Please import the pictures into the program for doing further work with them" | * You need to think about a suitable context for your tasks. So don't just write: "import the pictures from the SD card into the Program" but something like "You are a Photographer and just finished shooting. Please import the pictures into the program for doing further work with them" | ||
* It needs to be clear when a task is finished. So don't write any open ended tasks but one that have a clear goal and condition one needs to reach. | * It needs to be clear when a task is finished. So don't write any open ended tasks but one that have a clear goal and condition one needs to reach. | ||
E.g. the example above could be improved by changing the end to "Please import the pictures into the program, so that you can see the images thumbnails in the | E.g. the example above could be improved by changing the end to "Please import the pictures into the program, so that you can see the images thumbnails in the program" | ||
* Use language that is easy to understand. If the task's description is not comprehensible nobody can test. | * Use language that is easy to understand. If the task's description is not comprehensible nobody can test. | ||
==Build a Prototype== | ==Build a Prototype== | ||
Now as you know what you are going to test you can build your prototype. | |||
==Do the test== | ==Do the test== | ||
==Formulate your findings== | ==Formulate your findings== |