Microsoft Interview Question
Software Engineer in TestsTeam: Server and tools in microsoft erp
Country: United States
Interview Type: In-Person
Adding ..
Check how many letter/characters you can write
Check if it is too glossy so that your shadow appears on it ?Thats not you want the whiteboard to be.
If you leave the writings on it for days and how easy it is to wipe it off.
check if marker pen is the only thing used to write on it. What happens with pencil/pen ?
How much stress you need to erase?
How can I erase it? What happens with a tissue/paper ?
How heavy it is to be hung on the wall?
I agree this is a very vague question, you need to ask the following questions before you can answer this question:
1. Who is using this whiteboard? and why?
2. What are some scenarios in which the user will be using this whiteboard?
3. is there any failure or boundary condition which is considered for this board? etc....
I agree this is a very vague question, you need to ask the following questions before you can answer this question:
1. Who is using this whiteboard? and why?
2. What are some scenarios in which the user will be using this whiteboard?
3. is there any failure or boundary condition which is considered for this board? etc....
One can build large number of test cases if we take the following approach.
1. Build test case around input like, Check if it is not too glossy so that your shadow appears or the marker ink doesn't hold up to the board and so on.
2. Build tests around the output - like board being with too glossy surface, showing up higher level of reflection for which stuff written on the board is not visible and so on..
3. Build tests around user acceptance tests - What is the board intended to (kind of user, drawing, writing - the width-lenght of the bard), How heavy is the board, is it portable or not and so on.
One can build large number of test cases if we take the following approach.
1. Build test case around input like, Check if it is not too glossy so that your shadow appears or the marker ink doesn't hold up to the board and so on.
2. Build tests around the output - like board being with too glossy surface, showing up higher level of reflection for which stuff written on the board is not visible and so on..
3. Build tests around user acceptance tests - What is the board intended to (kind of user, drawing, writing - the width-lenght of the bard), How heavy is the board, is it portable or not and so on.
This is a generic question. You need to ask questions up-front first in order to test out the whiteboard effectively. Some questions that come to mine are..
- pete May 06, 2012- what are the use cases of the white board?
- who is the white board are going to use by?
- what type of markets are designed for the white board?
...