Summary of wechat red envelope project test

• Projects without summary and thinking are incomplete

  First step ： Test requirements analysis

       After demand analysis , For each requirement point listed in the original requirement list , Find the test points we need to test , For the identified test points , Analyze the test plan corresponding to the test execution , The more detailed and precise it is, the deeper our understanding of the project . Therefore, when doing the project, you must start from the needs of users , Analogous to the life cycle of software development , The requirement analysis of software is similar to the requirement specification of testing , The strategy of testing is equivalent to the architecture design of software , Test cases are equivalent to detailed design , Use case execution is equivalent to software coding development .

Divided into the following points ：

1、 Understand the background of red envelope requirements

2、 Analyze and test the rationality of red envelope requirements （ This requires deep business skills , Accumulate and summarize more in the project ）

3、 Determine the scope and priority of the test （ draw xmind）

4、 Check for defects and make up for omissions ( Check whether the points in the requirements document are missing and need to be connected with the requirements personnel again )

a key ： Familiar with the business process of the project , Think from the perspective of user needs , When you have some experience , Don't be empiricist , Be alert to thinking inertia , A small change may lead to unexpected consequences .

Wechat red envelope module

 

The second step ：

Between project documents and test cases ：
The requirements document —— The core dependency of test design stage

Business flow chart , Page flow chart —— Test module division reference

Prototype design —— Visualize business processes and expected results

Design document —— Auxiliary algorithm 、 Logic 、 Test design in the technical direction of queue

Test module split ：
Start from the red envelope requirements document

Method 1 、 Disassemble the red envelope module with the function flow method

Method 2 、 The hierarchy method refines the red envelope function points （ Interface start ）

Method 3 、 The type division method disassembles the molecular function

The third step ：

Design a test plan

Step four ：

Selection of test case design method

  Input classification and select equivalent 、 Given range plus boundary 、 Conditional isolation wants to determine 、 Infinite exhaustion takes orthogonality （ Use less methods ）、

  Business complex scenario method 、 Test full coverage

The idea of actual design
1、 In any case, the boundary value analysis method must be used , Experience shows that this method has the strongest ability to design test cases and find program errors

2、 If necessary, use equivalence class partition method to supplement some test cases

3、 If the function description of the program contains the combination of input conditions , Then you can choose the decision table method at the beginning

4、 If the business complexity of the program is relatively high , Use scenario method to supplement some test cases

Wechat change recharge use case design

1） The recharge amount is considered for the boundary value ：0 element 、1 element 、 negative 、 Non amount parameter 、 Multi digit decimal （ After decimal 3 position ）、 Bank card limit

2） Equivalence classes consider multiple different banks and channels

3） Because the overall function does not include the combination of input conditions , So there is no need to add a cause and effect diagram

4） After recharging , The balance will include the recharge record when the change is displayed

technological process ： Wechat evokes recharge —— Top up amount —— My change —— Change details