GUI testing is a form of functional testing. Not only to consider the GUI itself test, but also to consider the GUI performance of the system function test.
features that the GUI should have
1. Compliance with standards and specifications
2. Intuitive(1) The user interface is clean, not abrupt, not crowded? The GUI should not create barriers for users. The desired function or expected response should be obvious and where expected to occur. (2) is the GUI organization and layout reasonable? Do you want to allow users to easily move from one feature to another? Is it clear what to do next? Can you decide to give up or return or withdraw at any time? Does the input be recognized? is the menu or window hidden? (3) Is there any extra function? is the software whole or part of the system doing too much? Are there too many features that complicate the job? Do you feel the information is too complicated? (4) If all other efforts fail, can the help system really help?
3. Consistency(1) Shortcut keys Hot-key and menu options. For example: In Windows, pressing the F1 key always gets help information, CTRL + C, CTRL + V. (2) Terminology and commands. Does the whole software use the same terminology? Does the attribute name match? For example, is find always called find, not sometimes called search? (3) users. Does the software always target the same user level? For example, the content of the error message should be for the user hierarchy. (4) button position. When the Windows dialog box has the OK button and the Cancel button, the OK button is always above or to the left, and the Cancel button is always the equivalent of the button below or to the right (5). The equivalent key of the Cancel button is usually ESC, while the equivalent button of the selected button is usually enter. Remain consistent.
4. Flexibility(1) State termination and skip. When the software has super User mode that users are very familiar with, it is obvious that they can skip a lot of hints or window directly to where they want to go (2) data input and output. Users want to have multiple ways to enter data and view results. To insert text in a WordPad document, you can enter, paste, read from multiple file formats, insert as an object, or drag from other programs with the mouse. (3) Use Tab key to move focus on GUI
5. Comfort(1) appropriate. The look and feel of the software should match the work done and the user. Financial business applications should not use brilliant colors and sound effects to express wild style. (2) Error handling. The program should warn the user before performing a critical error and allow the user to recover data that was lost due to an error operation. (3) performance. Fast is not necessarily a good thing. Many of the program's error message flashed through, unable to see. If the operation is slow (such as a progress bar), at least the user should be fed feedback on the duration of the operation, and it shows that it is working without stagnation (panic).
6. Correctness(1) Market positioning deviation. Do you have unnecessary or missing features, or do you have some features that do not match the marketing collateral? (2) language and spelling. Programmers know how to use only computer language keywords to spell out sentences, often to create unexpected user information. (3) Bad media. Media is all the support icons, images, sounds, and videos contained in the software UI. The icons should be the same size and have the same palette. Sounds should all have the same format and sample rate. The correct media should be displayed when selecting from the UI. (4) What you see is the income-wysiwyg. Make sure that the UI is what you actually get. When you click the Save button, does the document on the screen exactly match the disk? Is it the same as the original document when it is read from disk?
7. Practicality(1) does not mean that the software itself is practical, but only that the specific features are practical. (2) When reviewing the product specification, preparing the test or the actual test, think about the characteristics of the software to see if the actual value. Do they help users perform the functions of software design? If you think they are not necessary, look for the reasons why they exist in the software.
GUI Test Cases
window1, whether the window is based on the relevant input and menu commands to open 2, the window can change the size, move and scroll 3, the data content of the window can be accessed with the mouse, function keys, arrow keys and keyboard access 4, when overwritten and recalled, the window can correctly display 5, the need to use all window-related functions 6, Whether all windows related functions are operable 7, whether there are related drop-down menus, toolbars, scroll bars, dialogs, buttons, icons and other controls can be used for the window, and display 8, display more than one window, the name of the window is displayed appropriately 9, the active window is properly highlighted 10, if using multi-tasking Whether all windows are updated in real time 11, multiple or incorrect mouse presses will cause unexpected side effects 12, the window's sound and color hints and whether the window's action order meets the requirements 13, whether the window is properly closed
Drop -down menu and mouse1, whether the menu item is displayed in the appropriate context (context) 2, whether the application's menus display system-related features (such as clock display) 3, whether the drop-down operation is correct 4, the menu, the color palette and the toolbar is running correctly 5, whether the menu function is properly listed and the drop-down function 6, Is it possible to access all menu functions through the mouse 7, text font, size and format is correct 8, whether you can activate each menu function with other text commands 9, whether the menu function is highlighted or grayed out according to the current window operation 10, whether the menu function is executed correctly 11, the name of the menu function is self-explanatory, Whether the menu item is helpful 12, the equivalent function of the menu function and the function of the toolbar is consistent 13, in the entire interactive context, whether the mouse operation can be recognized 14, if the need to click the mouse repeatedly, whether the context can be correctly identified 15, the cursor, processing indicators and the identification of the pointer is appropriate to change the operation
Data Item1, the alphanumeric data item can be correctly echoed, and entered into the System 2, graphics mode data items (such as scroll bar) is working 3, whether it can identify illegal data 4, data input message can understand "source address" http://www.cnblogs.com/ccvamy/p/4474546.html
Tescase-gui (graphical user interface) test
