There was a problem sending you an sms. Check your phone number or try again later.
To get Scribd mobile enter your number and we'll send you a link to the Scribd app for iPhone & Android.
We've sent a link to the Scribd app. If you didn't receive it, try again.
- It is essential to have GUI consistency within the Application.
- Should be alike in look and feel as per any other standard Window software.
- Should have standard set of keys implemented for the software.
- Should have clean and neat exit.
While testing any Windows based application the testing can be broadly categorized
into following compartments. They are:
- Standardization Testing.
- GUI Testing.
- Validation Testing.
- Functionality Testing.
This compartment mainly emphasizes on the standardization part of the application.
Standardization means that the application being developed should have standard
look and feel like any other window application. The general guidelines are as follows:
1. The application should have first "About Application" screen displayed.
2. Most of the screens/ dialog box (as on context) should have Minimize, Restore and
3. Proper icon should be attributed to the application
4. All screens/ dialog box should have a proper caption as per the context used.
5. The application should be seen in the Windows Task Bar as well as status bar.
This compartment mainly emphasizes on the GUI - Graphics User Interface aspect of
the Application. It is not concrete that once GUI guidelines are set that can be
followed blindly. GUI standards may vary from company to company and also from
application to application. But still one can set general guidelines to have an overall
idea on how to start GUI testing. These guidelines apply for every screen/ dialog box
of the application. General guidelines are:
1. All the dialog box should have a consistent look through out the Application
system. For e.g.- If the heading within a dialog box is blue then for each dialog box
the heading should be of this color.
2. Every field on the screen should have an associated Label.
3. Every screen should have an equivalent OK and cancel button.
4. The color combination used should be appealing.
5. Every field in the dialog box should have a Short Cut Key support. For e.g.- User
6. Tab order should be normally set horizontally for the fields. In some case as per
the case the Tab Order can be set vertically.
7. Mandatory fields should have * (RED ASTERIK) marked to indicate that they are
8. Default key <Enter> should be set as OK for the dialog box.
9. Default key <Esc> should be set as Cancel for the dialog box.
Validation testing mainly depends on the fields set in the dialog box and the
functions it has to perform. But still there are certain common rules that can be
applied. General guidelines are:
1. For text box fields where value entered has to be numeric check following:
\u00a8 It should accept numbers only and not alphabets.
\u00a8 If field usage is such that for e.g., To accept
Total number of days
Zip code etc.
then it should not accept 0 and negative values.
2. For text box fields where value entered has to be alpha-numeric check following:
\u00a8 It should accept alphabets and numbers only.
\u00a8 If field usage is such that for e.g., accepting
then field value should start with an alphabet only.
\u00a8 Depending on the condition this fields may accept special characters like -, _, . etc.
3. If the field is a combo box then it has to be checked for following points:
\u00a8 Check the combo box has drop down values in it, it is not empty.
\u00a8 Drop down values should be alphabetically sorted. This might change as per
requirement but as standard practices it should be alphabetically sorted. For e.g. to
select data type from the list it will be as follows:
\u00a8 Selection of any drop down value is displayed on closing and opening the same
\u00a8 By default some value like "Select Value" or "_______" string is displayed. This is
because User comes to know that value is to be selected for this field. Avoid
displaying the first default value in the list.
4. If the field is a list box then it has to be checked for following points:
\u00a8 Check the list box has values in it, it is not empty.
\u00a8 List box values should be alphabetically sorted and displayed. This might change as
per requirement but as standard practices it should be alphabetically sorted.
\u00a8 Selection of any list box value should put a check before the value and should
display the correct value(s) selected on closing and opening of the same dialog box.
\u00a8 If the list box supports multiple selection then check whether multiple values can be
5. If the field is a list of radio button then it has to be checked for following points:
\u00a8 Check whether as per requirements all the values are listed. For e.g. to select date
format. Possible values displayed will be as follows:
\u00a8 Same selected value should be displayed on closing and opening of the same dialog
6. Data Controls are to be tested as part of functionality testing.
Now bringing you back...
Does that email address look wrong? Try again with a different email.