Web Testing Materials

About Web Testing
1 page
(1) Whether the page list is complete (whether all the required pages have been listed)
(2) Whether the page is displayed (whether the page exists at different resolutions and whether the page is displayed in different browser versions)
(3) Whether the page is correctly displayed and beautiful (whether the screen is refreshed correctly when the browser window is adjusted)
(4) Whether to display special page effects (such as special font effects and animated effects)
(5) Whether the display of special page effects is correct

2. Page Element
(1) List of page elements (whether to list all the required elements, such as buttons, single quotes, check boxes, list boxes, hyperconnections, and input boxes)
(2) Whether the element is displayed (whether the element exists)
(3) Whether the page elements are correctly displayed (mainly for text, graphics, and signatures)
(4) shape and placement of page elements (such as buttons, list boxes, check boxes, input boxes, and hyperconnections)
(5) Whether the basic functions of page elements are implemented (such as text effects, animation effects, buttons, and hyperconnections)
(6) fault tolerance list of page elements (such as input box, time list, or calendar)
(7) Whether error tolerance of page elements exists
(8) error tolerance of page elements

3. Functions
(1) Whether data Initialization is performed
(2) Whether data Initialization is correct
(3) whether the data processing function is executed
(4) whether the data processing function is correct
(5) Whether to save the data
(6) Whether the data is correctly saved
(7) Whether it affects other functions
(8) If other functions are affected, will the system respond correctly?
(9) other errors
(10) all functions of the function module can be listed, sorted, and combined to test all functions of the module.
For example, if a function module has the most basic addition, deletion, modification, and query functions, perform the following tests:
Test a single function (ADD, modify, query, and delete)
Add --> Add (continuously add tests)
Add --> Delete
Add --> Delete --> Add (the newly added content is consistent with the deleted content)
Add --> modify --> Delete
Modify --> modify (continuous modification test)
Modify --> Add (the newly added content is consistent with the content before modification)
Modify --> Delete
Modify --> Delete --> Add (the newly added content is consistent with the deleted content)
Delete --> Delete (delete test continuously)
(11) The query function can be divided into two situations to verify the operation results.
1. When the page is opened, the results are automatically displayed without special emphasis;
2. If you need to perform a manual query, the query is performed after other functions are completed.
4. Prompt information
(1) success or failure prompt
(2) operation result prompt
(3) Confirmation prompt
(4) dangerous operations and important operation tips
(5) return to the page displayed after the page prompt
5 Fault Tolerance
Note the following situations:
(1) Empty or non-empty
(2) uniqueness
(3) font length and format
(4) number, postal code, amount, phone number, email, ID number, and password
(5) Date and Time
(6) special characters (for databases), single and double quotation marks (&)
6. Permission Section
Function permission: specifies the functions that a user can use and cannot use.
Data permission: Specifies the data that the user can process and cannot process. Yes
To merge to function test
Operation permission: In terms of logical relationships, the Operation Sequence and data processing status. Can combine
Test the function.
Permission change: can be merged to function test

(1) Whether the function permission exists
(2) Whether the function permission is correct
(3) whether the data permission exists
(4) whether the data permission is correct
(5) Whether the operation permission exists
(6) Whether the operation permission is correct
(7) list of functions that cause permission changes
(8) Changes in function permissions or data permissions, or both
(9) is the permission change correct?

7. keyboard operations
(1) Use of the tab key
(2) Use of the up and down arrow keys
(3) Use of the Enter key
(4) use the shortcut keys set by the system (if any)

8 other precautions during testing
(6) Integrity: whether it is a whole with no functional defects
(7) ease of use: easy to use
(8) Consistency: similar problems are handled in a similar way.
(9) prompt information: whether the prompt information is complete, correct, and detailed
(10) help information: whether to provide help information, the form of help information (page text, prompt information, and help files), and whether the help information is correct and detailed
(11) compatibility: including OS compatibility and application software compatibility, and hardware compatibility
(12) Scalability: whether there is room for upgrade and whether the interface is retained
(13) Stability: hardware and software configurations required for running, resource occupation, fault tolerance in case of problems, and data protection
(14) Running Speed: Speed and bandwidth usage

There are several points:
1. function test: whether the required functions are met
2. String Length check: Enter the content that exceeds the string length stated in the requirement to check whether the system checks the string length and whether an error occurs.
3. character type check: enter other types of content where the specified type of content is to be entered (for example, enter other types of characters where the integer type is to be entered) to check whether the system checks the character type, whether an error will be reported.
4. Check punctuation marks: the input content includes various punctuation marks, especially spaces, quotation marks, and enter keys. Check whether the system processes the punctuation correctly.
5. Chinese Character Processing: enter Chinese characters in a system that can enter Chinese characters to check whether garbled characters or errors may occur.
6. duplicate information, and whether the system correctly processes the entered content by inputting spaces before and after it.
7. Interface Test: the UI is correct, consistent, friendly, and easy to use.

User Interface testing refers to the software from the perspective of the end user, which is hard to understand and is not easy to use because of Software defects. You can check the user interface from the following aspects:
1. Usability check: Make sure the software is easy to understand and easy to use.
2. consistency check:
A. Check whether the style of the system page is consistent, such as the size, color, and font of the text.
B. Whether the expression of the prompt information is consistent.
C. Check whether the order of buttons is consistent.
D. Back, cancel, and so on.
E. Whether the name, position, length, and type of each field are consistent with the design document requirements. For example, the employee no and loginname are inconsistent.
3. correctness check: Check whether the form, button, table, header, footer, prompt information, other text spelling, and sentence syntax on the page are correct.
4. friendliness check:
A. Prompt whether the information is friendly.
B. The system should give a warning and prompt information before the user executes the wrong operation.
C. Check the page resolution and check the friendliness of the system interface in various resolution browsing systems.
5. Rationality check: After performing operations such as delete, update, add, cancel, and back, check whether the page returned by the information is reasonable.
6. Check whether the localization is successful: the English version should not contain Chinese information. The English translation is accurate and professional.
7. Page maximization check: whether the page is processed during the test of maximization/Minimization/restoration.