Functional Test Case Library (1)
1. Input validation
Input validation mainly includes: digital input validation, illegal character input validation, input length validation, required item validation and information prompt
1. Numerical input validation: Enter numbers ( positive, negative, zero, single-precision, double-precision ), character strings, blank values, null values, and critical values respectively. Invalid input, the system will give the necessary judgment prompt information
2. Character input verification: input single-byte characters, double-byte characters, uppercase and lowercase characters, special characters, blank values, and null values respectively. Invalid input, the system will give the necessary judgment prompt information
3. Date and time input verification: input any character, any number, data in non-date format, incorrect date ( wrong leap year date ), null value, and blank value. If the input is illegal, the system will give the necessary judgment prompt information. Note: Some systems will not allow the input of dates and times after or before the current day; some systems will automatically fill in the date and time through JavaScript, at this time, you need to pay attention to whether you can manually fill in the input subjectively
4. Multi-list selection box: Test whether multiple selections can be made and whether the data in the list box can be displayed completely. When there is too much data in the list box, it is necessary to sort the data in a certain format
5. Single-column drop-down box: test whether it can be manually entered and whether the data in the drop-down box can be displayed completely. When there is a lot of data in the drop-down box, it is necessary to sort the data in a certain format. If there are too many data values in the drop-down box, the drop-down box may exceed the display range of IE, which cannot be accepted.
6. Large text input box (textArea) : Although it can meet the input of large amount of data, it is best to display the length limit of input characters, and it should be combined with "character input validation". Note that punctuation should be allowed
7. File input box input validation: This input box is mainly used for file upload operations. During testing, you should pay attention to the extension of the input file. From a testing standpoint, developers are required to place input restrictions on extensions and enter formatting hints where appropriate. When the input is invalid input such as null value, the system will give necessary judgment prompt information. In addition, there should be a limit on the size of the uploaded file, and it should not be too large
8. Input character length verification: whether the length of the input character exceeds the actual system's ability to receive the character length. When the input exceeds the length, the system will give the necessary judgment prompt information
9. Required field verification: When the input is not allowed to be empty, the system needs to have the function of prompting the user to input information
10. Format and rule input validation: When the input requires a certain format, the system needs to have the function of prompting the user to input information. For example, the ID card number can be entered with 18 or 15 digits. The last digit of some ID cards is a letter. There are certain rules for the birthday and ID number on the ID card.
11. Input validation of system error location: When there is a problem with the input, it is captured by the system, and the cursor on the page can locate the input box where the error occurred.
12. Input validation of radio buttons and multi-select boxes: radio boxes need to verify in turn whether the values of the radio boxes are valid; multi-select boxes need to verify whether the values of the multi-select boxes are valid in turn
13. Verification code verification: When doing verification code input verification, first test with " character input verification ", and then pay attention that when using IE to roll back or refresh, the displayed verification code should be consistent with the actual system verification code. If the verification code is displayed in the form of an image, but the image cannot be seen or displayed incompletely due to other reasons (such as the network), the system should allow re-fetching, and it is best not to refresh the entire page
2. Operational Verification (CZ)
The use case library is mainly for page operations
1. Page link check: whether each link has a corresponding page, and the switching between pages is correct
2. Relevance check: whether deleting/ adding one item will affect other items, and if so, whether these effects are correct
3. Check whether the function of the button is correct: whether the functions such as adding, deleting, modifying, and checking are correct
4. Repeat the submission of the form: a record that has been successfully submitted, use IE to roll back and then submit it to see if the system has processed it
5. Multiple IE rollback: Check the situation of using IE rollback multiple times. If there is a rollback, roll back, go back to the original page, roll back again, repeat several times to see if there is an error
6. Shortcut key check: Whether common shortcut keys are supported, such as Ctrl+C , Ctrl+V, Backspace, etc., whether there are restrictions on shortcuts for some fields that do not allow input of information, such as selection of people and selection of dates
7. Enter key check: press Enter directly after the input is completed, see how the system handles it and whether it can report an error
8. Upload and download file check: Whether the function of uploading and downloading files is realized, whether the uploading file can be opened, what are the regulations on the format of the uploading file, whether the system has explanatory information, and whether the system can do it
9. Other verifications: The size of the pictures on the page should not be too large. When third-party software support is required, necessary information should be given. For example, jre support is required, but jre has not been installed on the user's machine . There are prominent signs to remind users to install
3. Login module test case
This use case library is mainly aimed at the login module. Needs to be combined with the " Access Control Authentication (FWKZYZ)" use case library
1. Login name input: perform " input verification ". Need to pay attention to whether the login name is case-sensitive and space-sensitive
2. Password input: perform " input verification "
3. Submit operation: Combine with " Access Null Value Verification (FWKZYZ)". After entering the correct login name and password, the user can enter the specified correct page. When the entered login name and password are incorrect, the system restricts their login and gives appropriate prompt information. When an error is encountered, an "error page test" should be performed
4. Reset operation: When the reset operation is performed, all input items on the current page are cleared
4. Add operation test cases (ZJ)
The use case library is mainly for adding operations
1. Add input content and perform " input validation "
2. Repeated increases should be limited. Specific operations: Using network transmission and server delay, click the " Add " button multiple times, and often find repeatedly submitted data in the database.
3. When the addition succeeds or fails, there should be necessary information prompts
4. The increase of file data: some increases include the increase of database data, and the increase of some files. The data at this time will be stored in two places, so when testing, it is necessary to comprehensively verify the relevant data
5. File data validation: perform " input validation " value "file input box input validation". Note: When the uploaded file is a Chinese file name, after uploading to the server, there may be garbled characters. Now the general practice is to replace the original file name with a combination of letters and numbers to overcome the drawbacks of Chinese character file names. In addition, it can increase the security of the file
5. Delete Operation Test Case (SC)
This use case library is mainly for delete operations
1. Select the data field to be deleted. Sometimes the system will delete according to ID , and sometimes the system will delete according to name. You should pay more attention when testing. Generally, it is required to delete according to ID, because deleting according to name may cause duplicate names.
2. Deduplication should be limited. Specific operations: Using network transmission and server delay, click the " Delete " button multiple times, and often find repeatedly submitted data in the database
3. When the deleted data still has files, it is necessary to verify the data in the database and whether the files under the hard disk are deleted at the same time.
4. When the data is deleted successfully or failed, there should be a response information prompt
5. Perform " Operation Verification "
6. Modify the operation test case (XG)
The use case library is mainly for modifying operations
1. Open the data page that needs to be modified. Note that compared with adding pages, only part of the values can be modified, such as keywords, etc., which cannot be modified, and the two data should be consistent
2. Increase the input limit on the page and modify the input limit on the page should be consistent
3. After the modification succeeds or fails, there should be a corresponding message prompt
7. Query operation test case (CX)
The use case library is mainly for query operations
1. Conditional input query, first perform " input validation " in the conditional input box
2. Condition combination query, combine multiple conditions to query, and the result can be verified by the database. It should be noted that the number of data results for the entire data query and conditional query data should be consistent. In addition, if you encounter a query time period of a certain day, some databases think that a day does not include 0:00, and some databases think that it includes 0:00.
3. All query results must be arranged in a certain order, which can be arranged by ID or by name
4. When the query succeeds or fails, the system should give necessary information prompts
8. Page turning operation test case (FY)
This use case library is mainly for page turning operations
1. When the amount of data is large, it needs to be displayed in pagination. The number of lines displayed on each page should not exceed 20 lines. It is better to have a serial number on the list on each page. User-friendly search
2. The page turning buttons should include: the first page, the previous page, the next page, the last page, the current X pages, and the total X pages, these commonly used buttons and displays, and the buttons can turn pages normally
3. The data displayed on each page of the page turning button should be accurate to ensure that there is no data that cannot be found. The best way is to combine it with the database to verify
4. When there are too many pages, and the page turning data cannot be displayed in full, the system should have a perfect response mechanism, such as displaying the page numbers of the first three pages of the current page and the last three pages of the page.
5. When turning to a certain page, the system should have a clear sign indicating the page number where the page is located.
9. Error page test (CW)
The error page is a friendly interface generated when encountering system exceptions
1. When the system encounters a fatal error, the debugging information of the server cannot be displayed on the page, because doing so will bring insecurity, and an appropriate prompt should be given.
2. When the system is busy and cannot give correct information in time, the system can give a friendly error page, such as: " Please try again later " and other prompt information