how to do lab manual work and which which thing can be write please tell
Answers
Answer:
"lab manual" is the term we'll use for the document that you give your test users to guide their exploration of the interface that you're testing; other sources might call it a "test guide", "user worksheet", etc. The basic idea is simple: You are going to bring your users into the testing lab and tell them nothing much about the software they'll be working with outside of it's overall purpose, e.g., "We have a cool new drawing app for your to try out today". Then you'll sit them down, wire them up as needed...and then what? Well, that's when you give them the lab manual. It is just a brief intro paragraph that sets the stage, followed by a set of domain level tasks that you want them to accomplish. They work through all the tasks using your application, and when they hit the last page that says "Wow, you're done! Awesome and thanks!", then they are done and you can shut things down. Some key pointers:
FIRST: Explicitly discuss and write down your specific goals for this usability test. Decide what exactly it is you want to test here. If it's just a general more or less isolated test of an application, you'll probably just focus are the key functionalities of the app. It's important to articulate these very clearly; ask yourself some questions to move this along: What is the main, central thing(s) that users want to accomplish quickly and easily with this app? What functionalities are those that absolutely positively must work, or else users will dump the app? On the other hand, maybe this test is part of a larger testing regime associated with a full development effort. In this case, your targeted functionalities might be very specific, e.g., those associated with a newly develop/modified module, or functionalities that had significant problems during a previous round of testing, or specific functionalities that you are told to test by the development team. Whatever the case, very clearly outline the functionalities you want to test before you start writing up the lab manual!! You'll need to have them clearly in mind to design a good lab manual...and you'll need to explicitly review these testing goals later, when you report out your results.
Ok, now that you know where you are heading, we can write the manual:
Start with a separate cover page that just has the title on it. This is key: first, they can't read ahead before you start the test; second, you can clearly see on your video record when they turn that page and start. A nice clean starting point for your analysis.
Start the main section with an intro paragraph that sets up the context. Something like "Imagine you are traveling abroad in Europe. One of the most tricky challenges you'll face when traveling is figuring out how to manage local transportation, e.g., how best to get from your hotel to a recommended restaurant elsewhere in the city. The TravelGuru app is here to help. In the following pages, you'll be asked to use the app to find out key information during your imaginary trip. In particular, let's start with the assumption that you're staying in the Hotel Jardinier on the outskirts of Marseilles; this is what we've set as your current location. Have fun!". See what I mean? Sets up the context, gives a clue what the app is and what they'll be using it for.
Next you'll have a series of exercises. Use the testing goals you articulated at the start to drive these "test tasks"...obviously the tasks should exercise exactly those functionalities that you are curious about. ) This means that you have to think about, discuss, and settle on what these key functionalities are!! Then design little tasks that test these functionalities. You yourself (as an expert) should be able to complete them all in 1/3 of the time you expect users to figure them out in. Make it all flow within the imaginary scenario you intro'd at the start; so between questions you have some connective stuff like "now that you've found a good restaurant and eaten, you decide that you want to go see a live theatre performance. Use the app to..." See what I mean? Keep the story going...
Explanation: