1. The main process business logic of the project
2. Elements, interfaces, operations, implicit logic
3. Upstream and downstream relationships (implicit logic, accounts, business processes, etc.)
4. Deeply explore the content and user experience
5. Different account roles -》 Different menus - "Different businesses
6. Keep a backup of common use cases, which will be used frequently to save repeated writing (for example, page number operations)
7. Click on the non-first page, and then enter only one record to query, see Whether the front-end code resets the page number
8. Learn to read f12: interface request return value, application
9. Capture packets, jmeter, fiddler, jenkins, docker, sonar, git, database (sql), ecs and read logs
10. New Whether to arrange in flashback
11. When deleting, whether to perform a second confirmation
12. Whether there is a copy prompt for successful addition after adding
13. Deletion of non-first page, deletion of data on the last page
14. Learn to read logs
Analysis of common test concerns myself
Guess you like
Origin blog.csdn.net/budaoweng0609/article/details/124844496
Recommended
Ranking