Test for how a product should be tested. Summarize four points (right, wrong, extreme, perverted)
Before testing, get as much information about the product under test as possible (through extensive communication).
White box: (Statement overlay, decision overlay, conditional override, arrange overlay)//general development do unit tests.
Equivalence class Partitioning: input data Two types: valid, invalid.
Boundary value: The range of Values: (1~10). In the case of pressure line, the use of the program.
Causality diagram: The receiving interface: entering conditions. Through different conditions, different results. (different combinations of conditions, whether to achieve different results in practice)
Orthogonal practice Design Method: Large module, sub-module, sub-page, frame body, the interface has how many elements. (By the annoyance of Jane)
Function Diagram method: Flowchart test of the state.
Error inference: The test is derived from experience, intuition, and error.
Requirements Document Conversion method: Test According to the requirement file.
Random test Method (exploratory): Test at the user's point of view.
object Property Analysis: Set properties, state, and design test cases according to different attributes and states.
Subsequent additions .....
Summary of mobile phone test----Experience Summary two