Scribd
Upload
7 views

Gui Testing

Uploaded by

trungbao105
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
7 views

Gui Testing

Uploaded by

trungbao105
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

• Navigation – Check all menus, menu items and toolbar for navigation.

This should be done for both


keyboard and mouse to ensure both produce the same response. Check window navigation using
keyboard and mouse.
• Formatting – Check that all formatting is proper for date entry, masks and drop-down boxes. Items
should be nicely sort in lists and with the correct formatting
• Color and fonts – Check all colors, font widths and fonts for displayed texts and field alerts. Ensure the
field prompts use correct fonts and color with background set to read-only mode.
• Scrolls – All vertical and horizontal bars used in scrolling should only appear where necessary.
Eliminate all that should not appear.
• Controls and alignments – The window should be resizable, all controls should function as required
and every display should exhibit correct alignment. All content, list items and labels must be properly
aligned.
• Spelling and grammar – For elements like texts displayed in window, captions, error messages, field
prompts, status bar options and pop-up text must be of correct spelling and grammar.
• Justification – The numerical fields should be right justified while character and alphanumeric fields
should be left justified. Check, if any, for default displays
• Look and feel – Check that all multiple windows have the correct look and feel that expresses
transition and allows closing or navigating back
• Default and shortcut keys – All shortcuts and shortcut keys must be defined and should be checked
to ensure they work correctly. Default buttons should also work correctly
• Tab – Ensure the tab order is from top left and moves bottom right. Remove disabled fields which are
often marked as read-only fields from the tab sequence. The tab should load in time and its display should
be in sequence.
• Opening input – Test whether the cursor points on the first input when a new window is opened.
• Alternatives – The menu command should have alternative hot key sequences that can work correctly
and remove any duplicate hot key from the window.
• Behavior – Test and validate the behavior of different control such as the radio and push buttons, list
box buttons among others. Ensure there is a help menu and buttons like F1 land users at help pages.
• Modality and multiple windows – Test to validate that windows are modal and no other features
outside the window can be accessed when it is still active. Ensure there is a capacity to open multiple
windows.
• Contrast – Command buttons that are not in use should be greyed out to distinguish them from active
command.
• Images – Check through the entire application for broken images and fix them.

You might also like