McroSoft Six rules standard for Userinterface testing?
Answers were Sorted based on User's Feedback
Answer / rajendra prasad reddy
1. Every System Menu should have Exit/close option.
2. OK and Cancel Buttons should exist.
3. All labels should start with capital alphabets.
4. Alignment of all controls must be same.
5. All controls must be visible.
6. All labels must not overlap
The above six are called as MicroSoft six rules standard
for userInterface testing.These are very important in GUI
tetsing.
Byeeeeeeee
Friendz
Rajendra_penumalli@yahoo.com
hyd
Is This Answer Correct ? | 15 Yes | 0 No |
Answer / k.chandra sekhar
a) The Microsoft six rules. They are
b) Controls are visible and clear
c) Controls are aligning properly.
d) Controls are should not be overlapped.
e) Initial letter should be initial cap
f) Ok cancel buttons existence
g) System menu existence
h) The above six rules are under user inter face
testing.
i) User inter face testing is the under GUI testing
j) GUI testing is one of the functional testing.
My name is k.chandra sekhar
My phone no is 09246540049
I am in hyderabad
My mail id is ndra_143@yahoo.co.in
If any body want full explain send that mail
Is This Answer Correct ? | 4 Yes | 1 No |
What is negative test case ?
There are 100 test cases. And you got a bug at 85th test case. You reported it to dev. and dev. fixed that bug. when you are doing regression testing from which test case u'll do testing?? will start from 85 th test case are u'll execute 100 test cases?
How do you test cookies?
can someone give me a brief idea about embedded testing.. i know both embedded system concepts and testing concepts.. i just want to know what we have to do for embedded testing
WHAT ARE THE DIFFERENT TECHNOOGIES OR SOFTWARE LANGUAGES THAT SOFTWARE TESTER SHOULD KNOW?
What is the difference between client server and web based testing?
what is the need of black box testing after completing white box tesing?
1. Hai, if we are not having any SRS,BRS docs., how can we prepare the test cases & how can we test the application ? 2. In this, is it possible to make 100% bug free.
I want to know the real time cycle i.e SDLC.(First of all Buisness logic is prepared,but doesn't know by whom and with the help of whom?)Similarly what are the next steps (the persons involved) and connection in between the steps.
How do you know the code has met specifications?
what should be tested when credit card is used as payment option in ecommerce project?can anyone tell me in detail what to test n how to test when credit card is involved in web application?
what is buddy testing ?