Test case design ideas:
A QR code is actually a url address. When the mobile phone scans the code, it will be parsed into a url address according to the black and white (black pigment blocks represent 1, and white pigment blocks represent 0) areas on the QR code.
Analyzing the usage scenario, here actually involves a payee and a payer. The payee generates a QR code, and the payer takes a mobile phone to scan the code.
Know the usage scenario, and then split the function points, literally "QR code scan code payment", these 7 words can be split into 3 keywords: QR code, scan code, payment QR code scan code
payment
How to test the payment function
Scan a QR code for payment, how to test it?
1. Requirements testing
User perspective:
2. Interface test
After opening Alipay, can the interface be displayed correctly, whether the interface of the QR code is correct, and whether the interface of each step of payment is correct. There will be no front-end interface errors, or the interface cannot be opened.
Whether the interface is clear and free of typos Automatically adjust the screen brightness when presenting the QR code
3. Functional test:
Whether the user can successfully generate a QR code or QR code for payment, whether the screen can be brightened after the QR code appears, whether the user can successfully select different payment methods, such as "Huabei", "Account Balance", "Ye Bao", "Bank Account", etc. After scanning the code, can the user receive a successful payment interface, and the interface can correctly display the amount paid by the user, including payment information, whether to use discounts, discounts, etc.
Functional test: Can the code scanning gun successfully scan the QR code in the user's mobile phone, can receive money after scanning the code successfully, and successfully generate the payment interface. Whether the Alipay background, the merchant background, and the user's mobile phone can successfully transmit the payment result information.
4. Performance test: (including stress test, network test)
Stress test: Continuously scan the code to test how the scan code payment function works under strong pressure.
Network test: Test whether the entire payment process is stuck in different network environments and different network signal strengths, and where the stuck points are likely to appear.
Ease of use test: (Whether the operation steps are simple and convenient during the entire user payment process.)
Can the function of scanning the code to collect payment be successfully completed under different light conditions and different brightness of the screen.
Response time of user operations Multiple users are using code scanning operations at the same time, system performance
5. Compatibility test:
Test the scan code payment function, whether it is compatible with different mobile phone brands and different operating systems.
6. Safety test:
Can the two-dimensional code be automatically updated to a new two-dimensional code if it exceeds the safety time. Test whether the security mechanism of the entire payment process can be successfully implemented.
Forgery of payment requests, malicious tampering of amounts, malicious simulation of third-party interfaces to call merchant interfaces, etc. are all issues that we need to consider clearly. Is
there a time and frequency limit for the QR code? If the secure socket layer is used, test whether the encryption is correct , whether the information before and after encryption is complete
7. Interface test
Clarify the interface that needs to be called in the entire payment process, distinguish the interface of the merchant and the third-party platform and the request method of parameters, including the encryption of specific parameters of the interface, the use of abnormal order numbers to simulate payment, the inspection of the server, etc.