Scribd
Upload
41 views

Function Tesing Checklist: Yes No N/A Note

The document contains two checklists for testing the functions and GUI of a software. The function testing checklist contains questions about testing searching users by role, gender, status and creating a new user. The GUI testing checklist contains questions about consistency, layout, formatting, error handling and usability of the graphical interface. Both checklists include columns to mark if an item was tested and the results.

Uploaded by

hùng cường
Copyright
© © All Rights Reserved
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
41 views

Function Tesing Checklist: Yes No N/A Note

The document contains two checklists for testing the functions and GUI of a software. The function testing checklist contains questions about testing searching users by role, gender, status and creating a new user. The GUI testing checklist contains questions about consistency, layout, formatting, error handling and usability of the graphical interface. Both checklists include columns to mark if an item was tested and the results.

Uploaded by

hùng cường
Copyright
© © All Rights Reserved
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
You are on page 1/ 2

Function Tesing Checklist

Question Yes No N/A Note


Is the GUI following functions tested?
Search users by role x
Search users by gender x
Search users by status x
Create a new user

Is the business logic of the following


functions tested?
Search user by role x
Search users by gender x
Search users by status x
Create a new user

* Comment

* Suggestion

[ ] - Pass
[ ] - Test again
[ ] - Other
GUI Tesing Checklist

Question Yes No N/A Note

Is graphical design of GUI is consistent with other screen? x


Is one button set to be default? x
Are the controls ordered according to normal behavior
(Microsoft Style)? x
Are all labels aligned uniformly? x
Are text areas aligned uniformly? x
Are there any spelling mistakes? x
Are all non-enterable text areas of the same color (gray)? x
Is the tab sequence correct? x
Is cursor becomes hourglass when doing background
processing? x
Does cursor return to pointer after the task? x
Do all fields match data length? x
Do enterable fields accept entry only for the given lengths of
String e.g. char (30)? x
Are abbreviations used? If yes x
Are they understandable for end users? x
Are they consistently used across all screens? x
Are both mouse and key strokes handled? x
Are the color combinations used on screens consistent? x
Is the usage of the screens intuitive? x
If hotkeys or accelerator keys used, is it consistent? x
If yes to the above, has this been tested? x
Are error messages displayed in non-technical terms and are
understandable to the user? x
Are the error messages informative and not blaming the
x
user?
Before an action that affects the system (such as a delete) is
x
performed, is the user asked for confirmation?
Are date and time formats across the system consistent? x
Are number formats consistent? x
If Tooltips are used, are they helpful or meaningful? x
Are screens and menu mapped correctly? x

* Comment

* Suggestion

[ ] - Pass
[ ] - Test again
[ ] - Other

07e-CL/PM/HDCV/FSOFT 1/1

You might also like