• The goal of the test: what do you want to achieve?
The goal of the test is to check the functionality and usability of the site(Tuubi). We intend to gather enough information or facts in other to improve the short comings encountered on the site. MB: to test which functionslity and what usability aspects?Basic functionalities e.g successful login,appearance of workspaces,inter navigation functionality,to check the updates from course contents.Some usability aspects e.g this talks about the interaction of the users with the tools present on tuubi such as the when creating workspaces etc.
• Where and when will the test take place?
The test would be carried out in one of the computer rooms in school later next week.
• How long is each test session expected to take?
The test session would take approximately 10 20 mins for each participant. They will be given some questioners and Interviews also.
• What computer support will be needed for the test?
The support needed would be a computer connected to the internet because we would ask them(students) to log on to their Tuubi.
• What software needs to be ready for the test?
The basic software needed for the test are Windows OS and the latest versions of a web browser e.g. Mozilla, Internet Explorer etc.
• What should the state of the system be at the start of the test?
We will set the browsers default url to Tuubi, so that they can see Tuubi's login page when they start the browser and from that point on they will start by typing their user name and password.
• What should the system/network load and What should the system/network load and response times be? (not too fast or too slow);
The system network load would be adequate enough to support our test wich is at least a 2 Mbps or more.
• Who will serve as experimenters for the test?
Kashi will take the note.
Ademola handles the questioners.
Bekafa will do the introduction and
Biruk will make the interview.
• Who are the users going to be and how are we going to get hold of them?
The users are going to be co-students and we going to inform them beforehand so they would all be present during the test period.
• How many users are needed?
We are going to use at least 3 users for the testing.
• What test tasks will the users be asked to perform?
They will start by loging in, checking lecture notes, downloding lecture notes, changing prefrences, checking the forums, submitting assignements, creating workspaces, managing subscriptions, and how to navigate from one page to another and the loading time involved when opening any particular part of the site. The task would have to be listed in a chronological order which has to be suitted to our testing.
• What criteria will be used to determine when the users have finished each of the test tasks correctly?
After they finished their tasks they should logout The criteria would be the success achieved in each particular stage of the given task given to the participants in our testing. Such task may be was it possible for them to log in into their accounts or was it possible to download courses contents etc.
• What user aids will be made available to the test users (manuals, online help, etc)?
Verbal and written aid We would not be given to the users e.g. questionnaires. MB: this answer I do not get at all, it does not seem to answer to the questiongiving much assisstance to the participants because we would like to see how well they can find their around the Tuubi.
• To what extend will the experimenter be allowed to help the users during the test?
We are going to adopt the testing aloud method. MB: your give a method not an answer to the question which how much are youy allowed to help the user For example when they can't find a link, we can probably show them some online use of Tuubi. We would not want to interfare or impair their way of judgement .
• What data is going to be collected and how will it be analysed?
The data that would be collected would be what ways and methods they think Tuubi can be improved for the best. MB: nooooooo, do you take notes, record the session.....or use some other manner to document what occurred in during the test We will take notes of every thing that will happen in the test.
After Pilot Testing
1. When was the test Executed?
12.03.2009
2. where was the test Executed?
Dolphin
3. To be corrected in test plan
\ analyzation of exat time??how long exactly is going to take for the test?
\ Method for collection the data or answer
\ clear task of people involving to conduct the task,for e.g tester,participants exact information etc
\ For different user ,different test should be conducted.
4.Test plan being corrected above will be highlighted with red color.
5. Actual testing
where is it happening> Schools Library
When..9th Dec. 2009