1. Testing process
1. Manual testing process
- Requirements analysis and review
- Write test plans and test solutions
- Design test cases and review
- Execute test cases and defect tracking
- Write test report
2. Automated testing process
- Convert functional use cases into automated use cases (add a column in the functional use case template to determine whether it is automated)
- Build an automated testing environment (native dependent environment: Python, pycharm, browser, browser driver, selenium, parameterized)
- Build an automation framework (PO mode + data-driven + log + report)
- Write code
- Execute use case
- Generate reports and analyze logs
2. Test case design method
1. Equivalence class division method
Equivalence class: a subset of data that has some common characteristics
Valid equivalence class: a subset of data that meets requirements
Invalid equivalence class: a subset of data that does not meet requirements
A test case covers as many uncovered valid equivalence classes as possible;
a test case can only cover one invalid equivalence class;
- Equivalence class details:
(1) Length
(2) Type
(3) Composition rules
(4) Whether it is empty
(5) Whether it is case-sensitive
(6) Whether it is repeated
(7) Whether to remove spaces
Applicable scenarios: A large amount of test data is required Input, but cannot be tested exhaustively Typical
representative: input box test on the page
2. Boundary value method
Function: (Orderly, with range) Supplementary point of equivalence class
Upper point : Point on the boundary
Inner point : Point within the interval
From point : Point closest to the boundary value
Optimized equivalence class value: Does not belong to the same point as the upper point The outlier of the equivalence class can be tested without taking a value (for decimals, there is no outpoint, so there is no need to take it).
For example, (-99,99] upper point: -99, 99, inner point: 50, outpoint: -100, -98, 98, 100, of which -100 and 98 can not be tested
. Each boundary of the equivalence class must be used as a test condition.
3. Determination table method
- The decision table consists of
condition piles : all condition
action piles of the problem: all output
condition items of the problem : value
action items for the condition piles : output results under various values of the condition items. - Steps
(1) List all conditions and action piles
(2) Fill in the condition items
(3) Fill in the action items
(4) Simplify the judgment table
4. Scenario method
Simulates the scenario when users operate the software, mainly used to test the business process of the system.
According to an operation path implemented by the correct business process (simulating the correct operation process), the
operation process that causes the program to appear incorrectly (simulating the wrong operation process)
should also add some abnormal situations.
Smoke testing mainly uses the scenario method.
5. Error inference method
6. Flow chart method
It is suitable for sequential testing and is often used for business process testing, installation process testing, etc.
Generally, each process is verified with a test case.
3. Selection of test case methods
- Has input function, but no combination relationship between outputs → Equivalence class division
- The input has boundaries, such as length, type → boundary value supplement
- Multiple inputs, multiple outputs, there is a combination relationship between inputs and inputs, there are dependencies and constraints between inputs and outputs → Decision table
- Combination testing of multiple functions → scenario method
- Supplementary test cases → Error inference method