[Bank Test] Third-party payment test point + payment business process test analysis...


Preface

1. Payment function test point

1) Functional test
Whether it can support password-free payment and jump directly from the payment page to the payment success page;
Bank card payment The card number is correct, the zero code is correct, and the payment is successful;
The bank card payment card number is wrong, the password is wrong, and the payment fails;
There is a limit on the number of errors. Can it be repeated after one error? Can you try again after 2 errors? Will the card be locked after 3 errors?
Whether it supports scanning QR code for payment;
Whether it supports fingerprint payment; < /span> Whether to support credit cards, different bank cards, online banking, cloud QuickPass, third-party and digital RMB payments; Whether to support WeChat, Alipay, Huabei, Boreibei, Lingqiantong, change, credit card, etc. payment ; Fingerprint payment failure limit; The newly entered fingerprint , password payment is required; The fingerprint recognition is successful, and the payment is successful;
The fingerprint payment finger is injured, the fingerprint cannot be recognized correctly, and the payment fails;




The payment amount needs to be verified whether 0.01 and 50,000 can be paid, and whether the boundary value, such as -1, 50000.01, can be paid, and whether it can be paid by entering Chinese;

Null value payment, the consumption amount reaches the upper limit and cannot be paid;
The balance is sufficient and the payment is successful, but the balance is insufficient to cancel the payment;
It is not necessary to show that the balance is insufficient. The remaining balance will be deducted. Will payment continue if the payment method is changed? Can payment be canceled?

2) Compatibility testing

Different systems, different networks (wifi/4/5G), different browsers, different QR codes

3) Fault tolerance test

The payment process is disconnected;
Refund after successful payment;
Insufficient balance, change payment method;
The fingerprint is incorrect when paying, the phone is shut down during payment, and other pages are redirected when paying;
Refresh the page when paying and cancel and return halfway through the payment;

4) Performance and stress testing

Multiple users pay to one account at the same time;
Page jump time;
Jump to bill information after successful payment;
Power consumption during payment;
When the payment amount is insufficient, the jump time when the payment method is changed;
When the payment password is incorrect, the pop-up message time ;
Payment success response time under different network environments;

5) Interface testing

The payment page is simple and elegant;
The amount displayed on the payment page is in a suitable font;
When entering the password, the font size is clear and reasonable;
The billing information page is complete and clear;

6) Security testing

Whether the password is visible;
If you pay a larger amount, you will be asked if you are sure;
Whether the amount paid is consistent with the amount deducted; On new devices, payment real-name authentication will be prompted;
Will the payment be redirected to the billing information page?

7) Usability test

Password-free payment;
Fingerprint payment;
Easy-to-understand error messages;

2. Sort out the payment business process

Click to pay—> Select payment method—> Confirm the amount—> Enter password—> Successful payment

Completing this process test means completing the smoke test of the project!

Then it is necessary to test each stage and step in the process to specifically analyze the test points that may cause abnormalities, so it can be divided by stages and input items.

3. Payment classification

Generally speaking, online payment is divided into two consumption modes.
One is to pay the amount directly, such as shopping websites such as Taobao and JD.com, or membership services such as 360 cloud disk and video membership;

The other is to recharge to purchase virtual coins such as golden beans, and use the virtual coins to consume products on the website, such as game platforms, Sichuan peppercorns and other products!

1) Functional testing

The next step is testing. The first step is functional testing. Then, by combining various testing methods such as boundary values, equal class division, error speculation, and cause-and-effect diagrams, a relatively comprehensive set of test cases is compiled. The payment functionality is tested to ensure that the entire payment process and the involved payment processes work under all circumstances.

2) Interface testing

Clarify the interfaces that need to be called for the entire payment process, clearly distinguish the interfaces between merchants and third-party platforms, and the request methods for parameters, including encryption of specific parameters of the interface, use of abnormal order numbers to simulate payments, inspection of the server, etc.

3) Security testing

Payments will involve amounts, so we need to consider security testing. Forgery of payment requests, malicious tampering of amounts, malicious simulation of third-party interfaces to call merchant interfaces, etc. are all issues we need to consider clearly.

4. Summary of test points

Payment process test points:

Whether the payment amount and the amount payable are consistent (for example: whether the scanned payment QR code is consistent with the displayed amount payable). Payment still requires the entire payment process. From order confirmation to final payment success, there may be problems at any step.

The same payment method, different payment entrances (for example: as shown in the figure below, Alipay has two payment entrances. You can pay by scanning the QR code, or you can pay through the Alipay web page. During the test process, both entrances must covered.

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

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

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

Payment amount test point:

Normal amount payment;
Minimum amount: 0.01;
Meaningless value: 0 yuan;
Maximum amount: Set the maximum amount of payment;
Bank card or WeChat, etc., set the maximum daily consumption amount or the maximum single consumption amount;
Bank card or Pay when WeChat balance is insufficient;

Payment process test points:

Complete the payment process normally;
After placing the order, cancel the order;
After the payment is interrupted, continue payment;
End payment after payment interruption;
Single payment for a single order;
Combined payment for multiple orders;
Continuous click payment , whether there will be multiple purchases;

Payment method test points:

Alipay payment;
Alipay web payment;
WeChat payment;
bank card payment;

Coupons or discounts (with certain discounts);
When using coupons/discounts in payment, whether the amount payable and the actual payment amount are correct;
Whether coupons/discounts are required, and whether discounts can be omitted;
After the refund of the payment order is completed, whether coupons/discounts can still be used;

Test pit:

Pit 1:
The amount payable displayed on the page is returned through the interface vip.product, and the front-end displays the amount payable. However, the QR code for payment is returned through the interface vip.getPayUrl. As a result, the value scanned out of the QR code is different from the displayed amount payable!

The final problem is that vip.getPayUrl is retrieved from the server cache, causing the amount displayed in the QR code to be inconsistent with the amount payable displayed on the front end.

Therefore, to test payment, you still need to go through the entire payment process. From order confirmation to final payment success, there may be problems at any step.

Pit 2:
When paying through the Alipay website, after the payment is successful, the page does not jump back to the original service package webpage. The final reason is that the return_url of the service configuration is incorrect, resulting in no jump back to the original page after payment.

If the test cases fail to cover this scenario, it will cause very serious online accidents.

The following is the most comprehensive software testing engineer learning knowledge architecture system diagram in 2023 that I compiled.

1. Python programming from entry to proficiency

Please add image description

2. Practical implementation of interface automation projects

Please add image description

3. Web automation project actual combat

Please add image description

4. Practical implementation of App automation project

Please add image description

5. Resumes of first-tier manufacturers

Please add image description

6. Test and develop DevOps system

Please add image description

7. Commonly used automated testing tools

Please add image description

8. JMeter performance test

Please add image description

9. Summary (little surprise at the end)

Life is a struggle. Only by constantly surpassing oneself can we create a better future. Keep chasing your dreams and be positive. Only in this way will the door to success be opened for you.

Bravely pursue your dreams and persevere. Every effort is an opportunity to change your destiny. Believe in your own strength and only by trying your best can you write a wonderful chapter in life.

Every effort is an opportunity for yourself. Don't be afraid of failure. Only by persisting in chasing your dreams can you create your own brilliant life. Believe in yourself and move forward bravely, and you will surpass yourself and achieve extraordinary things.

Guess you like

Origin blog.csdn.net/m0_70102063/article/details/134927141
Recommended