[Tool] test points for common functions

1. We often encounter login, add, delete, and query modules. How should we consider the test points of these modules?

1) Login

① Both the user name and password meet the requirements (in the format)

② The username and password do not comply with the requirements (format requirements)

③ The user name meets the requirements, and the password does not meet the requirements (format requirements)

④ The Password meets the requirements, and the user name does not meet the requirements (format requirements)

⑤ The user name or password is blank

⑥ Username that does not exist in the Database and password that does not exist

7. username and wrong password in the database

Username and password that do not exist in the login Database

There is a space before the data entered by the cursor

⑩ Enter the correct username and password, and then press [enter] to log on

2) add

① The data items to be added are reasonable. Check whether the corresponding data is added to the database.

② Leave a required data Blank

③ Design test cases for other input items based on the principles of the Boundary Value equivalence class design test cases

④ There should be an error message in the areas that do not meet the requirements

⑤ Whether the table key is supported

⑥ Press enter to save

7. If you are prompted that the data cannot be saved, check whether a data record exists in the database.

3) Delete

① Delete the data in a database and check whether the data is deleted in the database.

② Delete data that does not exist in a database, read a book with an error message, and no data in the database is deleted

③ Enter a incorrectly formatted data to check whether there is any error message and no data in the database is deleted.

④ Add a space before the entered correct data to see if the data can be deleted correctly

⑤ No input

⑥ Indicates the table key?

7. Whether the Enter key is supported

4) Query

Exact query:

① The input query condition is the data in the database to check whether the corresponding data can be found correctly.

② Add a space before entering the correct query conditions to check whether the corresponding data can be correctly identified.

③ If the input format or range does not meet the requirements, check whether there is an error message.

④ Input data that does not exist in the Database

⑤ No data is input

⑥ Whether the table key is supported

7. Whether the Enter key is supported

Fuzzy query:

Add the following to the exact query:

① Enter some characters to check whether all the relevant information in the database can be found.

2. text box, buttons, and other controls

1). text box test

How to test the text box

A. Enter normal letters or numbers.

B. Enter the name of an existing file;

C. Enter extra-long characters. For example, if you enter a maximum of 255 characters in the "name" box, try to enter 256 characters to check whether the program can process them correctly;

D. Enter the default value, blank, and space;

E. If only letters are allowed, enter a number; otherwise, enter a letter;

F. Use copying, pasting, and other operations to force the input data that is not allowed by the input program;

G. Enter special character sets, such as NUL and \ n;

H. Enter a character or text that exceeds the length of the text box to check whether the entered content is properly displayed;

I. Enter the data that does not conform to the format and check whether the program is properly verified. For example, the program requires that the input format be YY/MM/DD, and the actual input is yyyy/mm/DD, the program should provide an error message

The test method used in the test process:

1. enter invalid data;

2. Enter the default value;

3. Enter a special character set;

4. input the data that overflows the buffer;

5. Enter the same file name;

2) Test the command button control

A. click the button to correctly respond to the operation. For example, click OK to perform the operation correctly. Click Cancel to exit the window;

B. Provide sufficient instructions for illegal input or operations. For example, if the number of working days in a month is 32, click OK and the system prompts that the number of days cannot exceed 31;

C. A confirmation message must be provided for operations that may result in data being unable to be restored, giving the user the opportunity to give up the selection;

3) Test the single-choice button control

A. a group of single-choice buttons cannot be selected at the same time, but only one can be selected.

B. Execute each single-choice button one by one. After selecting "male" and "female", the data stored in the database should be "male" and "female" respectively ";

C. A group of radio buttons that execute the same function must be selected by default in the Initial State and cannot be empty at the same time;

4) Test the up-down control text box.

A. Enter a number directly or use an up or down arrow to control the number. For example, enter 10 in "quantity", or click the up arrow to change the number to 10;

B. Use the up and down arrows to control the automatic cycle of a number. For example, if the maximum number is 253, click the up arrow to automatically change the number to 1. Otherwise, it applies;

C. directly enter the over-boundary value. The system should prompt you to re-enter the value;

D. Enter the default value. It is blank. For example, if the number of "inserts" is the default value, click "OK"; or, delete the default value, leave the content blank, and click "OK" for testing;

E, the input character. At this time, the system should prompt that the input is incorrect.

5) Test the combined list box

A. The entries are correct. The detailed entries can be determined based on the requirements;

B. perform the functions of each entry in the list box one by one;

C. Check whether data can be input to the composite list box;

6) check box test

A. Multiple check boxes can be selected at the same time;

B. Multiple check boxes can be partially selected;

C. Multiple check boxes may not be selected;

D. Execute the check box functions one by one;

7) Test the list box Control

A. The entries are correct. Similar to the composite list box, the items in the list are determined based on the requirement specification correctly without loss or error;

B. scroll bars must be used for a large number of contents in the list box;

C. When the list box allows multiple selections, you must check the shift selected entries, press Ctrl to select the entries, and directly select multiple entries with the mouse;

8) Test the scroll bar control.

Pay attention to the following points:

A. The length of the scroll bar changes in time based on the length or width of the display information. This helps you understand the position and percentage of the display information. For example, you can browse the 100-page document in word, when browsing to 50 pages, the scroll bar should be in the middle;

B. Drag the scroll bar to check the screen refresh and check whether there are garbled characters;

C. Click the scroll bar;

D. Use a scroll wheel to control the scroll bar;

E. the up and down buttons of the scroll bar.

9) Test the mixed use of various controls in the form

A. Interaction between controls;

B. The order of the tab key, generally from top to bottom, from left to right;

C. Use of hotkeys and test them one by one;

D. Use of the Enter key and the ESC key;

In the test, the principle of simplicity and complexity should be followed, and the function test of a single control should be performed first to ensure the implementation is correct, and then the function combination of multiple controls should be tested.

PS: when testing the password input box, pay special attention to the test of uppercase letter input.

3. Search, replace, insert, and edit operations

1) search operation

Case study: Open the "replace" dialog box in Word

This function can be tested successfully or failed.

　　Pass the test:

1. Search for the input content directly, or search for all

2. Search for the searched content in the combo box, and then find and confirm that the content of the document is correct. For example, if you have searched for a "Test Case", you do not need to enter the search content again, you can search the document directly.

Failed test:

1. Enter a query string that is too long or too short. For example, if the length of the query string is 1 to 255, enter 0, 1, 2,256,255, and 254 for testing;

2. Enter a special character set. For example, in word,. ^ G indicates an image and ^ indicates a column break. You can enter such special characters for testing;

　　2) The replacement test is roughly the same.

Use Cases for functional testing of editing operation windows:

1. Close the find and replace window. Exit without any operation;

2. Attachment and option test. If you set "exact search", "backward" search, and other attachment options to test;

3. Interaction between controls. For example, if the search content is empty, the buttons "search all", "Search", "replace all", and "replace" are gray.

4. hotkeys and Tab keys. Use the Enter key.

　　3) insert operation

1> insert a file

Test Status

A. Insert a file;

B. insert an image;

C. Insert the document itself into the document;

D. Remove the inserted source file;

E. Replace the content of the inserted source file;

2> link file

Test method:

A. Insert the link file;

B. link the document itself to the document;

C. Remove the inserted source file;

D. Replace the content of the inserted source file.

3> insert an object

Content to be tested

A. insert objects allowed by the program. For example, insert an Excel worksheet into word;

B. modify the content of the inserted object. The inserted object can still be correctly displayed;

C. Uninstall the program that generates the inserted object. For example, after an Excel worksheet is inserted into word, the worksheet is still in normal use.

4) EDIT operations

Edit operations include cut, copy, and paste operations.

1> test the cut operation method

A. Cut the text, text box, and text box;

B. Cut the image

C. Text image hybrid Cutting

2> the copy operation method is similar to the cut operation.

3> during the test, we mainly test the paste operation:

A. paste the cut text, text box, and text box;

B. paste the cut image;

C. After cutting, paste it in different programs

D. paste the same content multiple times. For example, paste the content three times in the program after cutting;

E. Use the paste operation to force the input data that is not allowed by the input program.

4. Design of Interface Test Cases

1) Form

Method to test the form:

A. The size and size of the form should be appropriate and the control layout should be reasonable;

B. Move the form. Move the form quickly or slowly. The background and form must be refreshed correctly;

C. Scale the form. Controls on the form should change with the size of the form;

D. Display resolution. You must test whether the display of the program is normal under different resolutions;

During the test, you should also pay attention to whether the status bar is correctly displayed; whether the icons in the toolbar are valid for execution, whether they are consistent with the icons in the menu lazy; whether the error information is correct, whether there is no error, and whether it is clear;

2) Controls

Test method:

A. the font and size of the form or control must be consistent;

B. Pay attention to full-width and half-width mixing.

C. There is no mix of Chinese and English.

3) menu

Note that

A. Select whether the menu can work normally and make it consistent with the actual execution content;

B. Are there any typos:

C. Whether the shortcut keys are repeated;

D. Whether the hotkey is repeated;

E. Are shortcut keys and hotkey operations valid?

F. Is there a mix of Chinese and English?

G. The menu should be related to the context. For example, if users with different permissions log on to an application, users of different levels can view different levels of menus and use different levels of functions;

H. Right-click the shortcut menu

4) special attributes

1. The installation interface should contain company introductions or product introductions, with company icons

2. Company icons are preferred for the main interface and most Interfaces

3. Select "help"-> "about" to view relevant copyright and product information.

[Tool] test points for common functions