The most complete test case (UI)

First, the text box is a character type

Required non-null check:
1, the required fields are not entered-the program should prompt error;
2, must fill in only a few spaces, no other characters entered-the program should prompt error;

Field Uniqueness Check: (Not all fields are checked for this, depending on the actual project situation)
1. Enter duplicate field values when adding--Must prompt friendly information;
2. Enter duplicate field values when modifying--must prompt friendly information;

Field length check:
Enter [minimum number of characters -1]--program should prompt error;
Enter [minimum number of characters]--ok;
3, input [minimum number of characters +1]--program should prompt error;
4, input [maximum number of characters -1]--ok;
5, input [maximum number of characters]--ok;
Enter [maximum number of characters +1]--program should prompt error;

? field is a special character check:
1, input domain, such as the prohibition of the input of certain characters, whether the restriction is successful, the information is friendly;
2, Chinese, English, space, numbers, characters, underscores, single quotes, and all the special characters of the combination;
3. All special characters must be tested

? field is a special code check:
Enter the HTM code: such as "<font> Hello </font>";--You must display the code in text form.
2, input JavaScript code: for example <param name= "Moviewindowwidth" value= "" "" >;--must be in the form of text to display the code.
Multi-line text box input:
1, whether to allow carriage return to line;
2, save after the display can keep the input format;
3, only enter the carriage return line, check whether it can be saved correctly, if possible, view the saved results. If not, see if you have the correct prompt;
4, only enter the space, check whether it can be saved correctly, if possible, view the saved results. If not, see if you have the correct prompts.

Second, the text box is a numeric type
Boundary Value:

1, input [minimum value -1]--program should prompt error;
2, input [minimum value]--ok;
3, input [maximum value]--ok;
4, input [maximum value +1]--program should prompt error;

Number of digits:
1, input [limit number]--ok;
2, enter the [limit number +1]--according to the actual project, whether automatically rounded up to limit the number of digits, or prompt information;
3, input [limit number -1]--ok;

? outliers, special values:
1, input non-numeric data: Chinese characters, letters, characters--The program should prompt error;
2, input negative number--according to the actual project, if not allowed to enter negative numbers, must prompt friendly information;
3, the field is forbidden to enter non-numeric data directly, the use of "paste", "copy" function to try to enter, and test whether the normal commit save-only use "paste", "copy" method input special characters should not be saved, and should give the corresponding prompt;
4, full-width digital and half-width of the situation-the full-width of the number can not be saved, prompting friendly information, half-width digital normal preservation;
5, the first zero value: such as 01=1--depending on the actual project situation;

Third, the text box is the date type
Legality check:
1, day input [0 days]--program should prompt error;
2, day input [1st]--ok;
3, day input [32 days]--program should prompt error;
4, month input [1, 3, 5, 7, 8, 10, December], day input [31st]--ok;
5, month input [4, 6, 9, November], day input [30th]--ok;
6, month input [4, 6, 9, November], day input [31st]--program should prompt error;
7, input non-leap year, month input [February], day input [28th], such as 2009.2.28--ok;
8, input non-leap year, month input [February], day input [29th], such as 2009.2.29--program should prompt error
9, (Leap year) month input [February], day input [29th], such as 2008.2.29--ok;
10, (Leap year) month input [February], day input [30th], such as 2008.2.30--program should prompt error;
11, month input [0月]--program should prompt error;
12, month input [January]--ok;
13, month input [December]--ok;
14, month input [1 March]--The procedure should prompt error;

Format check:
1, illegal format: 2009-09, 2009-09-, 200-2-2;
2, depending on the specific project will be legal: 2009/09/01, 2009.09.01, 20090901, 2009-09-01;
Exception value, special value:
1, input Chinese characters, letters, characters--The program should prompt error;

Four, the text box is the time type
Legality check:
1, when input [24 o'clock]--The program should prompt error;
2, when input [00 o'clock]--OK;
3, sub-input [60 points]--The program should prompt error;
4, sub-input [59 points]--ok;
5, sub-input [00 points]--ok;
6, seconds input [60 seconds]--The program should prompt error;
7, seconds input [59 seconds]--OK;
8, seconds input [00 seconds]--OK;

? format check:
Illegal format: 12:30:, 123000;
2, depending on the specific project and whether it is legal: 12:30, 1:3:0;

Exception value, special value:
1, input Chinese characters, letters, characters--The program should prompt error;
2, whether the time involved in the system to take the server time;

Page features we often encounter the following features:
1, home, previous page, next page, end.
2, the total number of pages, the current page
3. Specify jump Page
4. Specify the number of bars to display per page
Of course, some are less than how many pages, all displayed in numbers, more than a few pages before the next page of control appears. This paper uses the above four points as a general use case to design it.

For "Home, Prev, Next, Last". The test points to check for page links or buttons are:
1, there are countless data when the display of the control
2, on the home page, the first and last whether you can click
3, at the end of the next and last page can be clicked
4, in the non-home and non-final, four button function is correct
5. If the records in the list are still sorted by the specified sort sequence after the page turn

For the "Total pages, current page total pages, current page", the main test points to check are:
1, the total number of pages is equal to the total record/Specify the number of pages per page
2, the current page is correct

For the above test cases, the following:

Step 1: List no records
Expect:1, four page turn controls grayed out and not clickable
2, the list has the corresponding no data information hint
3. Number of pages cannot be specified
4. Cannot specify jump page
5, the total number of pages displayed as 0
6, the current page display is 0
Step 2: Number of records in the list <= the number of bars per page specified
Expect:1, four page turn controls grayed out and not clickable
2, the total number of pages displayed as 1
3, the current page display is 1
Step 3: Number of records in the list > number of bars per page specified
Expect:1, default on the first page, the current page is 1
2. The data of the list is sorted correctly according to the specified sort column
3, record number and database match
4, Total pages = number of records/number of bars per page specified
Step 4: Number of records in the list > the number of bars per page specified, on the homepage
Expect:1, home turn gray not click
2, the previous page to become gray can not click
3, the next page can be clicked, from (Specify the number of bars per page +1) record start display, current page +1
4, end can click, display the last page of records
Step 5: The number of records in the list > the number of bars per page specified, in the middle of a page
Expect:1, the first page can be clicked, displaying 1 to the record of the specified number of bars per sheet
2, the previous page can be clicked, display the previous page of records
3, next page can be clicked, from the next page of records
4, end can click, display the last page of records
5. The data of the list is sorted correctly according to the specified sort column
6, the current page is the pages
Step 6: Number of records in the list > the number of bars per page specified, at the end
Expect:1, the first page can be clicked, displaying 1 to the record of the specified number of bars per sheet
2, the previous page can be clicked, display the previous page of records
3, the next page to become gray is not clickable
4, the last turn gray can not click
5. The data of the list is sorted correctly according to the specified sort column
6. The number of pages currently in the last page
For the Specify jump page, the main test points to check are:
1, whether can jump to the specified number of pages normally
2, the input of the number of jump page illegal when the processing
For specify the number of bars per page, the main test points to check are:
1, whether there is a default to specify the number of bars per page
2, specify the number of bars per page, the list displays the number of records, the page is correct
3, the number of entries per page of illegal processing

Step 7: Enter a positive integer that shows the number of bars per page to be less than the total record
Expect:1, the number of bars per page updated to the specified number of bars
  &NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;2, records that exceed the specified number of bars page display
         3. Total pages updated to list of records/pages per page
Step 8: Enter the number of bars per page for 0, negative, decimal
Expect:1, Tip "the number of bars per page must be an integer greater than 1"
         2, prompt after each page shows the number of bars returned to the last entry in effect
Step 9: Enter a positive integer that shows the number of bars per page greater than or equal to the total number of records
Expect:1, four flip buttons grayed out, no clicks
        2, total pages displayed as 1
        3 , the current number of pages is displayed as 1
Step 10: Enter the number of bars per page longer than the specified length of the database <<<maxlen>>>
expect:1, tips per page no more than <<< Maxlen>>> bit
        2 The number of bars per page after prompting reverts to the last effective number of bars
Step 11: Enter the number of bars per page for non-numeric, illegal values

Expect:1, Tip the number of bars per page must be an integer greater than 1
2, prompt after each page shows the number of bars restored to the last effective number of bars
Step 12: Enter the number of pages that are present for the jump
Expect:1, correctly jumps to the specified number of pages
Step 13: Enter the number of pages of the jump that do not exist or illegal values
Expect:1, jump page value is set to 1, display the first page of data

1: Ease of Use:
Button name should be easy to understand, with accurate words, screen discard the words are not ambiguous, to the same interface with the other buttons easy to distinguish, can hope the text to understand the best. Ideally, users will be able to know the functionality of the interface and perform the correct operation without consulting the help.
Ease of Use details:
1): To complete the same or similar functions of the button with frame frame up, commonly used buttons to support shortcuts.
2): The element that completes the same function or task is placed in a centralized position, reducing the distance of the mouse movement.
3): According to the function of the interface divided into local blocks, framed by frame, and to have a functional description or title.
4): The interface to support the keyboard auto-browse button function, that is, press the TAB key automatic switching function.
5): Controls on the interface should first be entered and important information should be in the tab order should be in the front, position should also be placed in the window more prominent position.
6): The number of controls on the same interface should not be more than 10, more than 10 can consider using the paging interface display.
7): Paging interface to support the quick switch between pages, commonly used combination shortcut keys Ctrl+tab
8): Default button to support enter and select operation, that is, press ENTER to automatically perform the default button corresponding action.
9): The writable control detects an illegal input and should give a description and be able to get the focus automatically.
): The Order of the TAB key and the order of the control are always, the current popularity of the overall from top to bottom, while the row from left to right way.
11): Check boxes and Options boxes are ranked by the high base of the selection odds.
12): Check boxes and Options boxes have default options and Support tab selection.
13): When the number of options is the same, use the option box instead of the drop-down list box.
14): Use the drop-down box instead of the option box when the interface space is small.
15): The number of options is called when you use the options box instead of the drop-down list box.
16): Professional-strong software to use the relevant terminology, universal interface advocates the use of universal word eye.
2: Normative:
Usually the interface design is designed according to the specifications of the Windows interface, that is, "menu bar, toolbar, tool compartment, status bar, scroll bar, right-click shortcut menu," the standard format, it can be said: the interface to follow the degree of normalization, the better the use of the corresponding. Small software generally does not provide a tool compartment.
Normative rules:
1): The common menu should have a command shortcut.
2): The menu with the same or similar function is separated by a horizontal line and placed in the same position.
3): The icon in front of the menu can visually represent the action to be done.
4): The menu depth is generally required to control up to three levels.
5): Toolbar requirements can be customized according to the requirements of the user's own choice.
6): Toolbars with the same or similar functions are put together.
7): Every button in the toolbar should be prompted with prompt information.
8): The maximum length of a toolbar cannot exceed the screen width.
9): The icon of the toolbar can visually represent the action to be done.
10): The System common toolbar sets the default placement location.
11): The tool compartment can be considered when the toolbar is too long.
12): The tool compartment to be able to increase or decrease, by the user's own according to the requirements of customization.
13): The default total width of the tool compartment should not exceed 1/5 of the screen width.
14): The status bar to be able to display the user's actual needs of information, commonly used are:
The current operation, system status, user location, user information, prompt information, error messages, and so on, if an operation takes a long time, you should also display the progress bar and process tips.
15): The length of the scroll bar should be based on the length or width of the displayed information can be changed in time to facilitate the user to understand the location and percentage of information displayed.
16): The height of the status bar to place five good words, the width of the scroll bar is slightly narrower than the state bar.
17): The menu and the tool bar should have a clear boundary, the menu needs to be highlighted, so that when the toolbar is removed, there is still three-dimensional.
18): The 5th font is usually used in the menu and status bar. The tool bar is generally wider than the menu, but not too wide, otherwise it looks very uncoordinated.
19): The right-click shortcut menu uses the same guidelines as the menu.
3: Help Facilities:
The system should provide detailed and reliable help documentation that can be used to find solutions when users are confused.
Help facility Details:
1): The performance description and instructions in the help documentation are consistent with system performance. (Our system Help documentation is a description of the system's ancestral period, confusing).
2): When the new system is packaged, the changes are made in the help document to make the appropriate changes.
3): To provide timely call system help function. Commonly used F1.
4): When you invoke Help on the interface, you should be able to locate the help location relative to the operation in a timely manner. That is to say, help should be targeted immediately.
5): It is best to provide the current popular online Help format or HTML Help format.
6): Users can search for help in the Help index with keywords, and of course should provide help with the main inscription.
7): If you do not provide a written help document, it is best to have the function of printing help.
8): In the help should provide our technical support methods, once the user is difficult to solve their own can easily find new ways to help.
4: Rationality:
The diagonal intersection of the screen is where the user looks directly at the top One-fourth places where the user's attention is easily drawn, and the two locations should be taken care of when placing the form.
Reasonableness rule:
1): The center position of the parent form or main form should be near the diagonal focus.
2): The subform position should be in the upper-left or middle of the main form.
3): When multiple subforms pop up, they should be shifted to the right and downward to show the form's title.
4): Important command buttons and the use of more frequent buttons to be placed on the interface to the attention of the position.
5): Incorrect use of buttons that easily cause the interface to exit or close should not be placed in the easy spot. The horizontal start or the last with the vertical row is the easy point position.
6): Buttons that are not related to the in-progress operation should be masked (grayed out in Windows and cannot be used).
7): For operations that could cause data to be unrecoverable, a confirmation message must be provided to give the user the opportunity to opt out.
8): illegal input or operation should have enough prompt description.
9): For the operation of the problem occurred in the place to cause errors to be prompted, so that users understand the wrong source, to avoid the formation of indefinite waiting.
10): Hints, warnings, or error descriptions should be clear, clear and appropriate.
5: Aesthetics and Coordination:
The interface should be sized to fit an aesthetic perspective, feel coordinated and comfortable, and be able to attract users ' attention within an effective range.
Aesthetic and coordination rules:
1): Long and wide close to the golden point ratio, avoid the long-width imbalance, or width over length.
2): layout should be reasonable, not too dense, nor too empty, reasonable use of space.
3): The button size is basically similar, avoid using too long name, so as not to occupy excessive interface position.
4): The size of the button and the size of the interface and space to coordinate.
5): Avoid placing large buttons on the empty interface.
6): The interface should not have a large vacant position after the control is placed.
7): The size of the font to match the size of the interface, usually the font used in Arial 9-12 is more beautiful, rarely use more than 12th font.
8): The foreground and background color collocation reasonable coordination, the contrast should not be too big, preferably less dark, such as red, Big green and so on. Common colors Consider using the Windows interface tones.
9): If the use of other colors, the main color to be soft, with affinity and magnetism, resolutely eliminate the purpose of the Thorn color.
10): The main colors commonly used in large-scale systems are "#E1E1E1", "#EFEFEF", "#C0C0C0" and so on.
11): The interface style to be consistent, the size of the word, color, font to be the same, unless it is necessary for artistic processing or have special requirements of the place.
12): If the form supports minimizing and maximizing or zooming in, the controls on the form will also be scaled with the form, instead of zooming in only the form and ignoring the controls.
13): For the interface containing the button should not generally support the zoom, that is, the upper right corner only the shutdown function.
14): The subform does not need to be scaled when the parent form supports zooming.
15): If you can provide users with custom interface style is better, by the user to choose their own color, font and so on.
6: Menu Location:
The menu is the most important element on the interface, and the menu location is organized according to function.
Menu Set Test Details:
1): Menus are usually arranged in a "common--primary--minor--tool-Help" location, in line with the popular Windows style.
2): Commonly used are "file", "edit", "View" and so on, almost every system has these options, of course, according to different systems have a choice.
3): Drop-down menu to be grouped according to the meaning of the menu options, and cut in accordance with certain rules of the arrangement, separated by a horizontal line.
4): The use of a set of menus have a succession of requirements or a guide, should be ranked in order.
5): Menu items that are not ordered are ordered by frequency and importance, often placed at the beginning, not commonly used on the back, and important in the beginning, secondary in the rear.
6): If the menu options are large, the length of the extended menu should be used to reduce the depth of the principle arrangement.
7): The menu depth is generally required to control up to three levels.
8): The common menu to have a quick command, the combination of principles see 8.
9): Menus that are not related to the operation are handled in a shielded manner, if the dynamic loading mode-that is, only the menu that is needed-is best.
10): The icon in front of the menu should not be too large, and the word height to keep the best.
11): The main menu width to close, the number of words should not be more than four, each menu can be the same number of words the best.
12): The number of main menus should not be too much, preferably a single row layout.
。 7: Uniqueness:
If you blindly follow the industry's interface standards, you will lose their individuality. It is particularly important to design an interface that has its own unique style when the framework conforms to the above specifications. Especially in the commercial software circulation has the very good migration the implicit advertisement utility.
1): The installation interface should be an introduction or product introduction, and has its own icon.
2): The main interface, it is best to have a company icon on most interfaces.
3): The sign-in screen should have the logo of the product, including the company icon.
4): The "about" in the Help menu should have copyright and product information.
5): The company's series of products to maintain the interface style, such as background color, font, menu arrangement, icons, installation process, button language should be broadly consistent.
8: Combination of shortcuts
Use shortcut keys in menus and buttons to make it faster for users who prefer to use the keyboard. The use of shortcut keys in western Windows and its applications is mostly consistent.
In the menu:
1): Transaction-oriented combinations are:
ctrl-d Delete; Ctrl-f search; ctrl–h replace; ctrl-i insert; ctrl-n new record; Ctrl-s save Ctrl-o Open.
2): List:
Ctrl-r, ctrl-g positioning; ctrl-tab the next page window or the reverse-order navigation of the same control;.
3): Edit:
Ctrl-a Select all, ctrl-c copy, ctrl-v paste, Ctrl-x cut; ctrl-z undo operation; Ctrl-y restore operation.
4) file operation:
Ctrl-p print; Ctrl-w off.
5): System Menu
alt-a files; alt-e edit; alt-t tools; alt-w window; alt-h Help.
6): MS Windows reserved key:
Ctrl-esc Task List, ctrl-f4 close window, Alt-f4 end app, Alt-tab next app, Enter default button/confirm action; ESC Cancel button/cancel operation; shift-f1 context-sensitive help.
In the button:
Can be adjusted according to the needs of the system, the following is a common combination.
Alt-y determine (yes), alt-c Cancel, alt-n No, alt-d Delete, alt-q exit, alt-a Add, alt-e Edit, alt-b browse; alt-r read; Alt-w write.
These shortcuts can also be used as a standard for developing Chinese applications, but they may be preceded by the initials of Hanyu Pinyin.
9: Security Considerations:
The error rate is controlled by the following methods on the interface, which greatly reduces the damage caused by the user's human error. Developers should take into account all possible problems and minimize the likelihood of errors. If the application has a protective error and exits the system, this error is most likely to cause the user to lose confidence in the software. Because this means that the user wants to break the train of thought, and time and effort to re-login, and the operation has been done because there is no disk and all lost.
Security Details:
1): The most important thing is to exclude errors that may cause the application to abort abnormally.
2): Should be careful to avoid the user inadvertently input invalid data.
3): Use related controls to restrict the types of user input values.
4): When the user makes a choice of only two possibilities, you can use a single box.
5): When the selection may be more, you can use a check box, each choice is valid, the user cannot enter any invalid choice.
6): A list box, drop-down list box can be used when a particular term is selected.
7): In an application, the developer should avoid unauthorized or meaningless actions by the user.
8): limit or block input characters or actions that may cause fatal errors or system errors.
9): Remedial action should be taken for operations that may have serious consequences. By remediation The user can return to the original correct state.
10): Judge the input of some special symbols, the characters that conflict with the symbols used by the system, and prevent the user from entering the character.
11): For error operation it is best to support reversible processing, such as canceling series operation.
12): You should prevent the user from doing an operation that is only entered after the validation character is entered.
13): The cancellation function should be provided for operations that may cause long wait times.
14): special character Fuchang; >&lt, ":" ["{,/|}]+=)-(_*&&^%$#@!~,.。?/There are spaces.)
15): To limit the conflicts with the reserved characters used by the system.
16): When reading the information entered by the user, choose whether to remove the front and back space as needed.
17): Some fields that are read into the database do not support spaces in the middle, but the user really needs to enter the middle space, which should be processed in the program.
10: Multi-window application and system resources:
Well-designed software should not only have a complete function, but also to occupy the most limited resources as far as possible.
1): In a multi-window system, some interface requirements must be kept at the top level, to prevent users from opening multiple windows, non-stop switching or even minimize other windows to display the window.
2): Automatically unload the memory when the main interface is loaded, and let out the occupied Windows system resources.
3): Close all forms, and release all system resources that are accounted for when the system exits, unless it is a system that needs to run in the background.
4): Try to prevent the exclusive use of the system.

1. Input verification input verification mainly includes: digital input verification, illegal character input verification, input length verification, required verification and information tip 1. Digital Input Validation: Enter numbers (positive, negative, 0, single, double), string, blank, NULL, critical value. Illegal input, the system gives the necessary information of the judgment prompt

2. Character Input Validation: Enter single-byte characters, double-byte characters, uppercase and lowercase, special characters, blank values, and null values, respectively. Illegal input, the system gives the necessary information of the judgment prompt

3. Date and time input verification: Enter any character, any number, non-date format data, incorrect date (wrong leap year date), null value, blank value, respectively. Illegal input, the system gives the necessary information of the judgment prompt. Note: Some systems will not let you enter the date or time after the day, or some systems will be using JavaScript to fill the date time, you need to pay attention to whether or not to manually fill in the input

4. Multi-List selection box: whether the test can be multi-selected, if the data in the list box can be displayed completely. When the list box has too much data, you need to sort the data in a certain format

5. Single-column list drop-down box: whether the test can be manually entered, whether the data in the drop-down box can be displayed intact. When you have a lot of data in the dropdown box, you need to sort the data in a certain format. If the dropdown box data value is too large, the drop-down box may exceed IE display range, this kind of situation can not be received

6. Large text input box (TextArea): Although it can meet the input of large data volume, it is best to display the length limit of the input characters, and should be combined with "character input verification". It should be noted that the presence of punctuation should be allowed

7. File input Box input verification: This input box is mainly used for file upload operation. During the testing process, you should be aware of the extension of the input file. From a test point of view, the developer must enter restrictions on the extension and enter the formatting hints where appropriate. When input is an illegal input, such as null value, the system gives the necessary information of the judgment. In addition, for the uploaded file size should be limited, not too big

8. Enter the character length verification: the length of the input character exceeds the ability of the actual system to receive the character length. When the input exceeds the length, the system gives the necessary information of the judgment

9. Required fields Validation: When the input is not allowed to be empty, the system needs to prompt the user to enter the information function

10. Format, rule Input validation: When the input needs a certain format, the system needs to be prompted to enter the information function. For example, the identity card number can be entered 18 or 15, some of the last identity card for the letter, ID card on the birthday and ID number has a certain rule

11. System error Location input verification: When the input has a problem, is captured by the system, the cursor on the page can navigate to the input box where the error occurred

12. Single box, multi box input validation: The Radio box needs to verify that the value of the radio box is valid, and the multi box needs to verify that the value of the marquee is valid 13. Verification Code verification: To do verification code input verification, the first combination of "character input verification" to test, and then note that the place is, When using IE fallback or refresh, the verification code displayed should be consistent with the actual system verification code. If the verification code is displayed as a picture, but the picture cannot be seen or displayed for other reasons (such as a network), the system should allow re-acquisition, preferably not the entire page Refresh 2. Operation Verification (CZ) The use case library is primarily for page operations

1. Page link check: Each link has a corresponding page, and the page switch between the correct

2. Correlation check: the deletion/addition of an item will have an impact on other items, and if so, whether the effects are correct

3. Check the function of the button is correct: such as increase, delete, change, check and other functions are correct

4. Repeat the form: A record has been successfully submitted, use IE back up and then submit to see if the system has been processed

5. Multiple IE fallback: Check multiple use of IE fallback situation, in the back of the place, back, back to the original page, and then back, repeated several times, to see if the error

6. Shortcut key check: whether to support common shortcut keys, such as CTRL + C, CTRL + V, BACKSPACE, etc., for some fields that do not allow input information, such as the selection of people, select the date to the shortcut is also limited

7. Enter check: The input after the end of the direct enter, see how the System processing, can error

8. Upload the download file check: Upload the download file is the ability to implement, upload the file can open, to upload the format of the file, whether the system has the explanation information, and check whether the system can do

9. Other verification: the size of the page should not be too large, need third-party software support, should give the necessary information, such as the need to support the JRE, but the user machine has not installed the JRE, then on the page should have a significant flag to remind users to install

3. Login module Test Cases the use case library is primarily for login modules. Need to combine access control validation (FWKZYZ) use case library 1. Login Name Input: Enter validation. Note that login names are case sensitive and spaces

2. Password input: "Input Verification"

3. Commit operation: Combined with "access null value verification (FWKZYZ)". When the correct login name and password are entered, the user is able to enter the specified correct page. When the login name and password entered are incorrect, the system restricts its login and gives the appropriate prompt information. "error page test" should be performed when an error is encountered

4. Reset operation: When the reset operation, all entries on the current page are emptied

4. Add Operation test Case (ZJ) The use case library is primarily for increased operations

1. Add input to "input validation" 2. You should limit the number of repetitions: Use network transport and server latency, click the "Add" button multiple times, and often find duplicate submissions in the database 3. When the increase succeeds or fails, you should have the necessary information prompt 4. Increase in file data: Some additions include the increase in database data, and the increase in the number of files, the data will be stored in two places, so when testing, the relevant data need to be fully validated 5. File Data validation: Enter validation for the input validation value file input box. Note: When uploading files to a Chinese file name, a garbled behavior may occur after uploading to the server. Now the general practice is to replace the original file name with a combination of letters and numbers, in order to overcome the drawbacks of Chinese character file names, in addition, can increase the security of the file 5. Delete operation test Case (SC) The use case library is primarily for delete operations

1. Select the data field you want to delete. Sometimes the system will be deleted according to the ID, sometimes the system will be deleted according to the name, the test should pay more attention, the general requirements by the ID to delete, because the name can be deleted, the name may have duplicate problem 2. You should limit duplicate deletions. What to do: take advantage of network transmission and server latency, multiple clicks on the "delete" button, often found in the database duplicate submitted data 3. When the deleted data also has files, Western medicine to verify the existence of data in the database, and the files under the hard disk are deleted at the same time 4. After the data has been deleted successfully or failed, To have a response to the information tip 5. Perform "Operation Verification" 6. Modify the Action test case (XG) The use case library is primarily for modification operations

1. Open the data page that needs to be modified, note that compared with the increase of the page, can only modify some of the values, such as keywords, etc. can not be modified, and the data should be consistent 2. Increase the input limit on the page and modify the input limit of the page should be consistent 3. After the modification succeeds or fails, there should be a corresponding Query operation Test Case (CX) The use case library is primarily for query operations

1. Conditional input query, first the condition input box "input Validation" 2. Conditional combination query, combine multiple criteria query, the results can be verified by the database. It is important to note that the entire data query and condition query data results in the same number of bars, in addition, if you encounter a day of query time period, some databases think that a day does not include:00, some database is considered to include 3. All query results must be arranged in a certain order, by ID or by name to arrange 4. When the query succeeds or fails, the system should give the necessary information hints

8. Page Turn operation test Case (FY) The use case library is primarily for page flipping operations

1. When the amount of data is very large, you need to display the page, the number of rows per page is best not more than 20 lines, each page of the list is preferably a serial number identification, row and row color to have a certain distinction, so as to facilitate the user's search

2. Page Turn button should include: Home, previous page, next page, last, current X page, a total of x pages, these common buttons and display, and buttons can be page-normal

3. The page-turn button displays the data on each screen accurately, ensuring that there is no data that cannot be found, and that the best practice is to validate with the database

4. Too many pages, paging data can not be fully displayed, the system should have a sound response mechanism, such as the value of the current page of the first three pages and three pages of the page of the page Digital 5. When you turn to a page, the system should have a clear logo that indicates the page number

9. Error page Test (CW) error page is a friendly interface that occurs when a system exception is encountered

1. When the system encounters a fatal error, the debug information of the server cannot be present on the page, because doing so will lead to unsafe and should give a suitable prompt message

2. Because the system is busy, unable to give the correct information in time, the system can give a friendly error page, such as: "Please user try again later" and other information

The most complete test case (UI)