Arrangement of payment function test points of test cases [recommendation]

1. The payment business process is summarized as follows:

  Click to pay ---> select the payment method ---> confirm the amount ---> enter the password ---> successful payment

  Completing this process test means completing the smoke test of the project! Then we need to test for each stage and step in the process, and analyze the test points that may cause exceptions in detail, so we divide it by stage and input item.

  as follows:

  In the era of non-cash payment, non-cash payment has become an indispensable part of life. We only need a mobile phone to travel all over the country (the premise is Alipay, WeChat is rich <00>), so as a tester, pay the test It is also a very important part, so let me combine some problems encountered in my work and summarize the common payment tests:

  One: Payment classification:

  First of all, according to different dimensions, we can usually divide payments into types as shown in the figure below:

 

Secondly, generally speaking, online payment is divided into two consumption modes. One is to pay the amount directly, such as Taobao, Jingdong and other shopping websites, or membership services such as 360 cloud disk, video membership, etc.; Consumption, such as game platforms, pepper and other products!

  Secondly, generally speaking, online payment is divided into two consumption modes. One is to pay the amount directly, such as Taobao, Jingdong and other shopping websites, or membership services such as 360 cloud disk, video membership, etc.; Consumption, such as game platforms, pepper and other products!

  Two: functional testing

  The next step is the testing work. The first thing to do is functional testing. Then I combined various testing methods such as boundary value, class division, error guessing, and causality diagram to sort out a relatively comprehensive set of test cases. The payment function is tested to ensure that the entire payment process and the payment processes involved are usable under all circumstances.

  Three: interface test

  Clarify the interface that needs to be called in the entire payment process, and clearly distinguish the interface between the merchant and the third-party platform and the method of requesting parameters, including the encryption of specific parameters of the interface, the use of abnormal order numbers to simulate payment, and the inspection of the server, etc.

  Four: Security testing

  The payment will involve the amount, so we need to consider the aspect of security testing, forgery of payment requests, malicious tampering of the amount, malicious simulation of third-party interfaces to call merchant interfaces, etc., are all issues that we need to consider clearly.

  Five: Payment process

  As shown below:

 

 Six: Test point

  Payment Process Test Point

  1. Whether the payment amount is consistent with the payable amount (for example: whether the scanned payment QR code is consistent with the displayed payable amount). Payment still needs to go through the entire payment process. From confirming the order to the final successful payment, there may be problems in any step.

  2. The same payment method, but different payment portals (for example, as shown in the figure below, Alipay has two payment portals. You can pay by scanning the QR code or paying through the Alipay webpage. During the test, the two portals must be covered.

  3. After the payment is successful, whether the product purchase is successful.

  For example, membership service products, whether the membership expiration time is normally delayed after purchase; for example, whether the order status is changed after the payment is successful, whether the product type and quantity are correct, etc.

  4. After the payment is successful, whether the user's amount is deducted successfully.

  Payment Amount Test Point

  1. Normal payment

  2. The minimum value of the amount: 0.01

  3. Meaningless value: 0 yuan

  4. Maximum amount: set the maximum amount paid

  5. Bank card or WeChat, etc., set the maximum daily consumption amount or single maximum consumption amount

  6. Pay when the bank card or WeChat balance is insufficient

  Payment Process Test Point

  1. Complete the payment process normally

  2. After calling the order, cancel the order

  3. After the payment is interrupted, continue to pay

  4. End the payment after the payment is interrupted

  5. Single payment for a single order

  6. Combined payment for multiple orders

  7. Continue to click to pay, whether there will be multiple purchases

  Payment Method Test Point

  1. Alipay payment

  2. Alipay web payment

  3. WeChat Pay

  4. Bank card payment

  · Coupons or discounts (with certain offers)

  · Whether the coupon/discount is used in the payment, the payable amount and the actual payment amount are correct

  · Whether the coupon/discount is mandatory or not

  · After the refund of the payment order is completed, can the coupon/discount still be used?

  Pit 1: The payable amount displayed on the page is returned through the interface vip.product, and the payable amount is displayed on the front end. However, the payment QR code is returned through the interface vip.getPayUrl. As a result, the value scanned by the QR code is different from the displayed payable amount! ! ! The final problem is that vip.getPayUrl takes the server cache, which causes the amount displayed by the QR code to be inconsistent with the payable amount displayed on the front end. Therefore, the test payment still needs to go through the entire payment process. From confirming the order to the final successful payment, there may be problems in any step.

  Pit 2: Pay through the Alipay website. After the payment is successful, the page does not jump back to the original service package page. The final reason is that the return_url of the service configuration is incorrect, resulting in the failure to return to the original page after payment. If the test case does not cover this scenario, it will cause very serious online accidents.
 

Finally, I would like to thank everyone who has read my article carefully. Seeing the fans’ growth and attention all the way, there is always a need for reciprocity. Although it is not a very valuable thing, you can take it away if you need it:

 

These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey. I hope it can help you too!

In my QQ technology exchange group (technical exchange and resource sharing, no advertising)

Guess you like

Origin blog.csdn.net/lzz718719/article/details/131584378