[Bank Test] Third-party payment function test points + loan FAQ interview questions (details)

---

Preface

1. Third-party payment function test point

Payment process:

When we test a function, we need to understand this logic first, and order payment logic generally has the following content:

1) Create a local unique order number;

2) Call payment and generate a payment order on the payment platform;
will return a payment voucher (payInfo)
The payment order number is in the callback method will get

3) When the payment is pending, the payment platform will call back the notification interface;
Save the order information to be paid locally (there are two order records at this time: one local order and one Payment platform orders, two IDs are associated)

4) The user initiates payment based on the received payment voucher (only successful payments need to be managed, unsuccessful ones can be ignored)

5) Payment platform callback notification interface (payment successful)
Update payment order
Update local order
Follow-up Operation

6) Actively query order status
Update payment order
Update local order
Follow-up operations
Refund or reflection (not detailed)

Abnormal test points for payment actually encountered:

You only need to understand the above content. Most of the content items will be known once you are familiar with them. In many cases, specific projects will be analyzed in detail. Most of the abnormal test points below are prone to abnormal situations that I have personally experienced.

Specific test scenarios:

1) If you access the payment interface 2 times (or more) in a row, if the callback is not completed on the first access, the second access needs to be restricted;

Possible problems: the second result is returned directly, and the first request may be successful, but the result returned by the first request is overwritten by the failure result returned by the second request;

2) Continuously access the callback order interface (submit payment request interface to the payment platform), and generate multiple signatures. It is necessary to verify whether the signature returned by the order is the latest;

Possible problems: If you use a previously generated signature to pay, an error will be reported;

3) An order is repeatedly submitted for payment and then returned. Exiting payment and calling payment again only allows different signatures to be generated. This is based on demand;

4) A signature that needs to be verified can only be paid once, this is based on demand;

5) Verification of payment signature, this depends on needs and individuals. Such as: abnormal/special symbols, etc.;
6) Pay 0 yuan/0.01 yuan/0.001 yuan;
7) Pay negative value;

8) Back-end processing of payment callback timeout: a reasonable copywriting. Method: add baffle/breakpoint;

9) Pay attention to the message callback. If it is a third-party payment system, there will usually be an asynchronous message callback.

For example: after payment, the interface will be queried in an infinite loop within a certain period of time, and success or failure will be returned in the end, but the order will not directly know the result. The system needs to access an interface again to understand the latest status of the payment to know whether the order has been paid successfully;

2. Loan knowledge interview questions

1) If you are asked to test a 6-month p2p loan product, how should you design a case and state the test points?

Answer ideas: 1. Test from the user's perspective. You can test how users use it. 2 A person plays multiple role tests. 3. Come up with more unusual scenarios.

When the bidding end date for loan products is T+7, the bids will be full and unsatisfied.
Before T+7, the bidding end date for loan products, the product will be fully bid in advance
After the product is established, check whether the system has sent an email before the repayment date every month , text messages, and in-site messages to notify borrowers to recharge to the platform account.

On the monthly repayment day, when the borrower recharges money for repayment, check how the system handles the situation if the recharge funds are sufficient, insufficient, or not recharged. When the recharge funds are insufficient or there is no recharge, the system should have penalty interest.

In the scenario where the borrower pays off the balance in advance, some products do not support early repayment, and some products require early repayment after a certain period of time (there is a certain handling fee for early repayment).

These are all testing points to focus on. (You have to act as a borrower to pay off the balance in advance, then act as a backend administrator to review, and then act as an investor to check the arrival of funds in the virtual account)

When the borrower pays off the funds in the last period, go to the backend page to check the status of the loan product. It should have ended normally. Go to the front page and search again, you should not find the loan product. (Or add: Go to the database to check the status of this loan product)

2) Is your P2P online? Can I check it? How long did the project take and how long is it expected to be completed?

Answer:
Two options:
It is not online yet and cannot be checked. This is a new project and is planned to be completed in half a year, but due to the There are some issues that have not been resolved, so it has not been completed within the estimated time.

The project name everyone wrote can indeed be found online, so it is said to be online and can be found. (In fact, the interviewer may not check it)

3) How do you measure real-name authentication? What platform do you want to retrieve data from?

Real-name authentication interface:
Bank card real-name authentication (call the bank interface to verify the card number, name, ID number, and mobile phone number. You need to use the verification code received by the mobile phone)< /span>

Identity verification and name authentication (National Citizen ID Number Inquiry Service Center, or directly the public security interface)

4) Do you also test backend management for P2P? Where do I retrieve the information for my personal Sesame Credit points?

Testing the backend management:
The backend is also tested, but I mainly test the frontend. My focus is on the frontend. The backend is only for use, as long as it can cooperate with the frontend to complete the process normally.

The backend mainly manages the frontend, including loan management and fund management.

Loan management: You can check the investment status of investors, you can also check the borrowing products of borrowers, and manage the borrowing products. For example, approval, repayment reminders for each period, early warnings, etc.
Fund management: Manage and view the user’s recharge, and approve the user’s withdrawal process.

Sesame Credit Points: It calls the interface of Alipay. Sesame Credit: It calls the interface of Alipay (Alipay provides such Sesame Credit service and charges about 0.1 yuan for each check)

5) How many rounds do you usually do for P2P functional testing?

Answer:
Medium version (major revision, online once a month):
The test is generally divided into 2 rounds: the first round: 5 days; Second round: 3 days; 2 days for regression testing; (10 working days in total). (There are 22 working days in a month. Requirements analysis and review, writing test cases, etc. generally take up half of the entire version time, or a few days less)

Small version (minor modifications, once every two weeks): 3 days for one round of testing and 2 days for regression testing.

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

2. Practical implementation of interface automation projects

3. Web automation project actual combat

4. Practical implementation of App automation project

5. Resumes of first-tier manufacturers

6. Test and develop DevOps system

7. Commonly used automated testing tools

8. JMeter performance test

9. Summary (little surprise at the end)

Success belongs to those who dare to challenge and pursue their dreams. No matter how many difficulties lie ahead, as long as we maintain perseverance and faith, we will be able to create our own brilliance.

No matter what situation you find yourself in, believe in your potential and abilities. As long as we pursue bravely and strive actively, we will surely be able to reach the pinnacle of success and maximize our self-worth.

Every challenge in life is an opportunity to shape yourself. Only by having the courage to face difficulties can you break through yourself and achieve higher goals. Fight hard and let your dreams light the way forward!