table of Contents
Seven command button control test
Eight radio button control test
Twelve test of the scroll bar control
One login
Enter a certain system, enter the login page, let's talk about the test points of the login function.
- User name and password meet the requirements (requirements on the format)
- The username and password do not meet the requirements (requirements on the format)
- The username meets the requirements, the password does not meet the requirements (requirements on the format)
- The password meets the requirements, the user name does not meet the requirements (requirements on the format)
- username or password is empty
- User name that does not exist in the database, password that does not exist
- User name existing in the database, wrong password
- User name that does not exist in the database, password that exists
- There is a space before the entered data
- Log in as a user who has been deleted or disabled
- After entering the correct user name and password, press [enter] to log in
When writing user name and password formats, boundary value and equivalence methods are often used. For example, a system login user name requires a length of 1~10. We can divide:
- Invalid equivalence class: Invalid equivalence class with length less than 1, and length greater than 10.
- Effective equivalence class: greater than or equal to 1 and less than or equal to 10.
Equivalence class: Equivalence class can be divided into two different situations: valid equivalence class and invalid equivalence class.
- Effective equivalence class
Refers to the set of input data that is reasonable and meaningful for the specification of the program. The effective equivalence class can be used to check whether the program achieves the functions and performance specified in the specification.
- Invalid equivalence class
Contrary to the definition of a valid equivalence class. Invalid equivalence class refers to the set of input data that is unreasonable or meaningless to the specification of the program. For specific issues, there should be at least one invalid equivalence class, and there may be more than one.
When designing test cases, these two equivalence classes should be considered at the same time. Because the software must not only be able to receive reasonable data, but also be able to withstand unexpected tests, such a test can ensure that the software has higher reliability.
Boundary value:
- Definition: The boundary value analysis method is a black box test method for testing the boundary value of input or output. Usually the boundary value analysis method is used as a supplement to the equivalence class division method. In this case, the test cases come from the equivalence class boundary.
- Difference from equivalence division
- Boundary value analysis is not to randomly pick one from a certain equivalence class as a representative, but to make every boundary of this equivalence class as a test condition.
- The boundary value analysis considers not only the input conditions, but also the test conditions generated by the output space.
- Consideration of boundary value analysis method:
Long-term testing experience tells us that a large number of errors occur on the boundary of the input or output range, rather than inside the input and output range. Therefore, by designing test cases for various boundary conditions, more errors can be detected. To design test cases using boundary value analysis methods, first determine the boundary conditions. Usually the boundary of the input and output equivalence classes is the boundary condition that should be tested. The value that is exactly equal to, just greater than or just less than the boundary should be selected as the test data, rather than the typical value or any value in the equivalence class as the test data. In the above example, the boundary value method is used to obtain values: 0, 1, 8, 10, 11
Two new
Test points of common added functions in the system:
- The data items to be added are reasonable, check whether the corresponding data is added in the database
- Leave a required data blank
- Design test cases for other input items according to the principle of boundary value equivalence class design test cases (the text box test will be explained in detail later)
- There should be error prompts where the requirements are not met
- Whether to support table key
- Can press enter to save
- If it is prompted that it cannot be saved, check whether there is one more data in the database
Three delete
Common delete function test notes:
- Delete the existing data in a database, and then check whether the database is deleted
- Delete data that does not exist in a database, whether there is an error message when reading the book, and no data in the database has been deleted
- Whether to support enter key
- Are there any tips for deleting by mistake
Four change password
Common points for changing password testing:
- Do not enter the old password, directly change the password
- Input wrong old password
- Do not enter a new password to confirm
- Do not enter new password
- The new password and the confirmed new password are inconsistent
- There are spaces in the new password
- New password is empty
- The new password format is correct (as required)
- The new password format is wrong (as required)
- The new password is non-allowed characters (if some passwords must be composed of English and numbers, then try Chinese characters and symbols, etc.)
- See whether it supports tap and enter keys, etc.; whether the password can be copied and pasted; whether the password is encrypted with a symbol such as *
- See if the password is case sensitive, the new password is lowercase in both Chinese and English, and the confirmed password is uppercase in both Chinese and English
- Can the new password be modified successfully as the old password
Five query
Common query function test notes:
- The input query condition is the data existing in the database, to see if the corresponding data can be found correctly;
- Add a space before entering the correct query conditions to see if the corresponding data can be found correctly;
- Enter data whose format or range does not meet the requirements, and see if there is an error message;
- Enter data that does not exist in the database;
- Do not enter any data;
- Whether to support the table key;
- Whether to support the enter key;
- Whether to support fuzzy query;
- Single query and combined query;
- Enter special characters to query (single quote, double quote, etc.);
Query result check:
- How to sort the query results smoothly;
- Whether the query result displays the sorting function according to the field;
- Whether the query result has pagination, if so, how many records each page contains;
- Whether the query result matches;
- Whether the result is consistent with the database;
- Whether the query result is an exact query or a fuzzy query;
UI verification:
1. Whether the text display is correct;
2. Whether there are typos on the page;
3. Whether the input box size and text size are appropriate;
4. Whether the page is beautiful;
5. The query result field shows whether it is consistent with the demand;
Performance aspects:
- Check whether the processing time is acceptable;
- When there is a large amount of data in the database, whether the query time is acceptable;
3. When multiple users query at the same time, enter the same or different query conditions and whether the system responds in a timely manner;
Six text box test
How to test the text box
- Enter the correct format data;
- Input the wrong format data;
- Enter very long characters. For example, in the "Name" box, enter more than the allowable number of characters, assuming a maximum of 255 characters, try to enter 256 characters, and check whether the program can handle it correctly (boundary value);
- Enter the default value, blank, space;
- If only letters are allowed, try to enter numbers; otherwise, try to enter letters;
- Use copy, paste and other operations to force input data that is not allowed by the program;
- Enter a special character set, such as NULL and \n;
- Enter characters or text that exceeds the length of the text box, and check whether the entered content is displayed normally;
Seven command button control test
- Click the button to correctly respond to the operation. For example, click OK to perform the operation correctly; click Cancel to exit the window;
- Give adequate prompts for illegal input or operations, for example, when entering the number of working days per month as 32, click "OK" and the system should prompt: the number of days cannot be greater than 31;
- For operations that may cause the data to be unrecoverable, a confirmation message must be given to give the user the opportunity to give up the choice;
Eight radio button control test
- A group of radio buttons cannot be selected at the same time, only one can be selected;
- Perform the function of each radio button one by one. After selecting "male" and "female" respectively, the data saved in the database should be correspondingly "male" and "female";
- A group of radio buttons that perform the same function must be selected by default in the initial state, and cannot be empty at the same time;
Nine Combo list box test
- The content of the entry is correct, and the detailed entry content can be determined according to the requirements description;
- Execute the function of each item in the list box one by one;
- Check whether you can enter data into the combo list box;
Ten check box test
- Multiple check boxes can be selected at the same time;
- Multiple check boxes can be partially selected;
- Multiple check boxes may not be selected;
- Execute the function of each check box one by one;
XI List box control test
- The content of the entry is correct; similar to the combo list box, according to the requirements manual, make sure that the content of the list is correct, and there is no loss or error;
- Use the scroll bar when the content of the list box is large;
- When multiple selections are allowed in the list box, check the items selected by shift, press ctrl to select items and directly select multiple items with the mouse;
Twelve test of the scroll bar control
Pay attention to the following points:
- The length of the scroll bar is changed in time according to the length or width of the displayed information, which is helpful for users to understand the position and percentage of the displayed information. For example, when browsing a 100-page document in Word, when browsing to 50 pages, the scroll bar position should be in the middle; 2. Drag the scroll bar, check the screen refresh, and check whether there are garbled characters;
3. Click the scroll bar;
4. Use the scroll wheel to control the scroll bar;
5. The up and down buttons of the scroll bar;
Thirteen interface test
The interface is the most direct layer between the software and the user. The quality of the interface determines the user's first impression of the software. And a well-designed interface can guide users to complete the corresponding operations themselves and play a role as a guide. At the same time, the interface is like a human face, which has the direct advantage of attracting users. A well-designed interface can bring users a sense of ease and joy and a sense of success. On the contrary, due to the failure of the interface design, the user feels frustrated. No matter how useful and powerful functions are, the user's fear and abandonment may be in vain. The current interface design is far from enough to attract the attention of software designers. It was not until the recent rise of web page production that it was favored by experts. And a well-designed interface is rejected due to the need for artistic beauty.
Let’s talk about some common meet test points:
13.1 Form
Method of testing the form:
- The size of the form should be suitable, and the control layout should be reasonable;
- Moving the window, moving the window fast or slowly, the background and the window refresh must be determined;
- Zoom the form, the controls on the form should change with the size of the form
- Display resolution, you must test whether the display of the program is normal under different resolutions;
When testing, also pay attention to whether the status bar is displayed correctly; whether the tool's icon execution operation is effective and whether it is consistent with the icon display in the menu; whether the error message content is correct, without typos, and clear, etc.
13.2 Controls
testing method:
- The font size of the form or control should be consistent
- Pay attention to the full angle, half angle blend
- Is there a mixture of Chinese and English
13.3 Menu
Pay attention when testing:
- Choose whether the menu can work normally and is consistent with the actual execution content
- Are there any typos
- Is the shortcut key repeated
- Whether the hotkey is repeated
- Whether shortcut keys and hot key operations are valid;
- Is there a mixture of Chinese and English
- The menu should be context-related, such as: users with different permissions log in to an application, users of different levels can see different levels of menus and use different levels of functions
- The shortcut menu of the right mouse button, such as: right click to display copy, etc.
13.4 Special attributes
1. The installation interface should have company introduction or product introduction, and company icon
2. The main interface and most interfaces should have a company icon
3. Choose "Help" -> "About" for naming, you should look at the relevant copyright product information first
13.5 Page Beautification
The interface should be sized to fit the aesthetic point of view, feel coordinated and comfortable, and be able to attract users' attention within an effective range.
Suggestions and requirements:
1. The length and width are close to the golden ratio, remember that the ratio of length and width is out of balance, or the width exceeds the length
2. The layout should be reasonable, not too dense, and not too open, and use the space reasonably
3. The size of the buttons on the same page should be the same, and the size of buttons on different pages should be as close as possible. Do not use too long names on the buttons
4. The size of the button should be coordinated with the size and space of the interface
5. Avoid placing large and irregular buttons on the empty interface
6. After placing the controls, the interface should not have a large vacancy
7. The font size should be coordinated with the size ratio of the interface, the font usually used is 12px
8. The foreground and background colors are reasonably coordinated, the contrast should not be too large, the main color should be soft, it is best to use dark colors, such as big red, big green, etc., you can borrow the Windows interface color
9. The main colors commonly used in large systems are "#E1E1E1", "#EFEFEF""#COCOCO", etc.
10. The interface style should be consistent, the size, color, and font of the words should be the same. It is recommended to use pictures for artistic treatment or special requirements.
11. If the form supports maximization or enlargement, the controls on the form should also scale with the form: remember to only enlarge the form and ignore the scaling of the controls
12. The system dialog page should not support zooming, that is, only the close function in the upper right corner
13. Usually when the parent form supports zooming, the child form does not need to be zoomed
14. If you can provide the user with a custom interface style, the user can choose the color..
13.6 Form
For the table, the settings of its properties agree to be defined in CSS
The most frequently used table is to display the installed data. Since there are many table items that need to be displayed on the page, in principle, the width of each cell of the table should be set in a percentage method, so that the table can not only speak the data completely. Display, but also can adapt to different resolutions. However, due to the variable length content in the table, in order to ensure that the width of the table is not squeezed, the display width can be fixed for the variable length content. When the display width exceeds the display width, it will be displayed as .., after the cursor stays, the details Floating layer display.
other requirements:
- The data in the header should be centered horizontally/vertically.
- If the content in the form is fixed-length, it will be displayed in the center; if it is not fixed in Chinese or English, it will be displayed on the left; if it is a numeric value, it will be displayed on the right
- The text in the table header should be bold or different from the table content
- Adjacent rows in the table need to use two light colors with a certain contrast difference as the background color
- The table border style of each page needs to be unified, it is recommended to set a thin border
- The link text in the table needs to be displayed in a different color or font from other content
- Try to control the nesting of tables within three levels, and prohibit the use of tables for page layout
13.7 Other page elements
1. Button, the text displayed on the button is required to accurately express the meaning of the function
2. Single selection box, the default selection and the distance between the associated text should be 3px
3. The multi-select box is not selected by default. The associated text should be able to accurately express the meaning of the selection and the spacing of the controls should be 3px
4. The drop-down box gives a default selection, and the default selection displays text prompts such as "default all" or "please select"
5. Picture, the default is to display the icon representing the picture file, or the thumbnail
6. Multimedia, the default is to display icons representing multimedia files
Fourteen paging test
Pay attention to the main points of paging test:
Condition combination (first page, second page, third page)
For the test of 1 page turning link or button, the main test points to be checked are:
- The display of the control when there is no data
- On the homepage, whether the homepage and the previous page can be clicked
- In the last page, whether the next page and last page can be clicked
- Whether the functions of the four buttons are correct when the first and last pages are not
- After turning the page, whether the records in the list are sorted according to the specified order, for 2 total pages
The current page, the main inspection points are:
- Is the total number of pages equal to the total number of records/specify the number of records per page
- Is the current page number correct
For 3 designated jump pages, the main inspection points are:
- Whether it can jump to the specified number of pages normally
- Handling when the number of input jump pages is illegal
For 4 to specify the number of bars displayed on each page, the main inspection points are:
- Is there a default specified number of items displayed per page
- After specifying the number of records per page, the number of records displayed in the list and whether the number of pages is correct
- Handling when the number of entries per page is illegal (English, special characters, etc.), enter 0 or a number that exceeds the total number of pages, whether there is a friendly prompt message
15 system ease of use
Ease of use means that the functions on the page follow conventions, such as: the button name is easy to understand, the wording is accurate, and it is easy to distinguish from other buttons on the same interface, and the text can be understood. This allows users to know the functions on the page and perform related correct operations without consulting the help
Claim:
- Open a new interface, the cursor stays in the first text box to be entered by default
- Place the buttons with the same or similar functions together to reduce the distance of mouse movement. Commonly used buttons should support shortcut keys
- Divide the interface into area blocks according to function, enclosed in Frame, and have function description or title
- The page should support the keyboard automatic browsing function, that is, press the Tab key to switch automatically
- The controls that should be entered first and important information on the page should be higher in the tab order, and the position should be more prominent on the window
- The number of controls on the same page is best not to be 10, if more than 10, you can consider using the page interface display
- Use option boxes instead of drop-down list boxes when the number of options is the same
- Checkboxes and option boxes are arranged in order of the highest probability of selection
- Use the option box when the number of options is small, instead use the drop-down list box;
- The order of the buttons should be the same as the order of the controls. At present, the general trend is from top to bottom, and the rows are from left to bottom.
- The order of the buttons should be the same as the order of the controls. At present, the general trend is from top to bottom, and the way between rows from left to right
Sixteen permissions test
1) After giving a person the corresponding authority, check whether the person has this authority on the interface, and log in as this person to verify whether the authority is set correctly (whether it exceeds the given authority);
2) Delete or modify the permissions of the personnel who have logged in to the system and are operating, and whether the program can be processed correctly;
3) Re-register the system and log in after changing the login identity to see if the program can be executed correctly and the authority is correct;
4) In the case of workgroup or role management, delete the workgroup or role containing users, whether the program can handle it correctly;
5) Whether users with different permissions log in to the same system, and whether the scope of permissions is correct;
6) Overwrite all permission settings of the system;
7) Can you add users with empty information (including empty usernames and empty passwords, empty usernames and non-empty passwords, non-empty usernames and empty passwords);
8) Can a long user name and long password be added, and if allowed, can the new user log in correctly;
9) Whether the system allows deleting the special user of the system administrator or modifying the password of the system administrator, and the actual situation of the system after deletion or modification;
10) Whether the logged-in user can modify his own authority;
11) Add user (with identification or number): same identification, different user name; same identification, same user name; different identification, same user name; different identification, different user name;
12) Can the logged-in user modify the information of himself (or other persons) and delete himself (or other persons);
13) Modify user information (including permissions, passwords, basic information, etc.), the impact on other modules;
14) Modify user information: the modified user information is the same as the existing user information; the modified user information is different from the existing user information;
15) Do not authorize users, whether to allow login;
15) When changing some settings, will it affect the settings of the personnel with superior authority and the same authority;
16) The system administrator has modified some data, whether the data has changed when logging in as another person;
17) Can a user belong to multiple groups at the same time, whether the permissions of each group can be crossed; whether the user who is added after deletion has the previous permissions; whether the user attributes (including permissions) are changed to see whether it affects the permissions.