Common test points on the web side:
1. Link test:
- The link takes the user to what it says, what you see is what you get
- The linked page exists,,, there will be no response status codes of 4**, 5**
- Ensure that there are no isolated pages on the web application system. The so-called orphaned page means that there are no other links pointing to this page and no friendly links
Dead link check:
Tool: Xenu
2. Form test
1. The correctness of the content is judged by the submitted database content or the returned page information. ( Fill in the valid equivalence class first to ensure that it can be submitted normally )
2. Equivalence classes and boundary value tests for each field. The type of each field and the actual data type it accepts. (number, text, date) ( test according to the definition of SRS, each form item must be tested )
3. Does the page have source code that should not be there?
4. Required items:
If you don't fill in, there will be a prompt?
When prompted, is it prompted in order?
Do you want to be reminded which one is not filled?
5. Pull down:
- Selectivity and fillability of the dropdown (male, female?)
- The selection content of the drop-down list is provided, fuzzy matching (input the prefix bi, bicycle, etc.)
- Secondary drop-down box, linkage selection. For example, if you select the delivery address, if you select Shanghai, Shanghai’s district, Huangpu District, etc. will appear automatically (apply equivalent class)
Another example of linkage: here you can use the method of equivalence class, such as municipalities, provinces and cities, Hong Kong, Macao and Taiwan each choose a test
6. The independence of the radio button
· Independence
Can multiple selections be made by holding down ctrl or shift
7. Scroll bar for long text
Use boundary values , watch out for boundary violations
8. SQL injection (described later)
9. Time:
1) Start time = end time, verify the data within one day;
2) Start time < end time, verify data across days, months, and years;
3) If the start time is greater than/less than the current time, if you search for the date of birth, verify that it is greater; if you search for a timed task time and verify that it is less than;
4) Only enter the start time or only the end time; neither the start time nor the end time;
5) If the end time is earlier than the start time, verify whether the system gives a reasonable reminder;
6) Format the time text box (_ _ _ _/_ _/_ _), and pay attention to the time format validation such as 20180612 format
10. Form submit button test:
— Whether to support carriage return/click
-Quick multiple clicks whether to submit the form repeatedly
- Network outage (weak network) submission
-Whether there is a prompt after submission , such as "Successful submission"
-Whether the content is encrypted after submission (fiddler captures the package to see)
—Whether the submission is subject to authority verification control (such as point deduction, some people enter the payment page for verification, and need to check whether the verification is done by clicking the submit button)
- Scenario test where multiple people operate on the form at the same time
11. Some business-related constraints,
-For example, shared bicycles are only allowed to ride when they are over 12 years old, so the registration age is >=12 years old.
- Another example, C1, C2 driver's license age is 18-70 years old, when applying for a driver's license, it must be verified
===============================================================================
UI：
Correctness of page text
Text wrapping due to page zoom
If the maximum length of the input box on the interface can be loaded, is it not displayed or truncated?
==============================================================================
Other supplementary content: (interview supplementary content)
1. Search box: (orthogonal method)
1) Any single condition query: normal input search, fuzzy search, super long search, no matching condition, empty;
2) Any two combination queries: ensure the correctness verification of any two combination queries, and verify all situations of the two combinations;
3) Three combination query: There is no need to test all level combinations of three combinations. Because the search for all single conditions and all combinations of two combinations have been tested before, then 2-3 groups of three combinations can be selected for testing here;
4) All-condition combination query: to ensure the correctness of the maximum combination;
5) Default condition query: Supplement the use cases of default condition query;
6) According to requirements or business rules, select key condition combination queries. If this point is repeated with 1) 2) 3) 4), repeated testing is not required.
2. Report
1) Content data correctness verification
2) Turn pages
-Functional verification of the first page, previous page, next page, and last page; pay attention to whether the previous page supports clicks in the case of the lower home page; in the case of the last page, whether the next page supports clicks;
-Verification of the correctness of the total number of pages and the current number of pages;
- Specify the jump page verification; for example, enter 8, click to jump, then whether it can normally jump to the data on page 8;
- And also note that the effective range of the next jump is 1-total number of pages; (equivalent class, boundary value)
So we consider 1. Valid value verification of the maximum number of pages,
And also need to consider 0, total number of pages + 1, negative number, decimal, non-numeric, empty outlier verification