Basic principles of software test point analysis — generality
Step 1: Understand the basic business process logic of the product: what is it, what does it do, and how does it work?
-
- Draw a flowchart, business logic comb
Step 2: Subdivide the module, and divide each small functional module in detail:
-
-
Note: Make sure not to omit, list the input items abnormal input items \
-
Normal: Cover normal core business processes — testing first? ? — Single feature smoke test
-
Exceptions: All kinds of exceptions? ? — Close to the user’s use scenario, to ensure that the product is handled correctly, prompt friendly!
-
Step 3: Look for each input for a specific function and analyze the test points in detail from the following perspectives
-
- Length, data type, mandatory, repeat
- Constraints on requirements + invisible requirements
- Steps that combine business processes
- Functional interaction — crossover
Step 4: Consider non-functional test points including interface, ease of use, compatibility, security, and performance pressures
The core business process of JD products
Shopping cart process analysis
Entrance to JD Shopping Cart
Jd Shopping cart interface
Failed to log in to purchase the car
The shopping cart is empty:
Shopping cart Function Points
1. Entry test: my shopping cart, go to the shopping cart and settle
2. User type: login user or login user
3. List of Goods:
-
- Display the list of goods according to the store, including pictures, name, unit price, quantity, subtotal, etc.
- Display the total amount of the store, the sum of goods
- The purchase quantity can be increased or decreased — equivalence class, boundary value
- Merchandise support delete, move to attention
4. Choose goods
-
- “Future generations”
- Single check, select part;
- Delete selected items, move them to attention, and clear the cart
5. Go to the checkout
-
- Click “Go to Checkout”
- Jump to the order confirmation interface – interactive verification
6, empty page processing
-
- Select “Go shopping” when shopping cart items are empty
