First, test case writing
1. The most important document in the test is the core of the test work. It is a set of input and output standards during the test and a specific comparison of software requirements. Writing test cases is the basic skills of testers, and there are not many people who can write well.
2. Contents of test cases: Case number, case name, test background, preconditions, priority, test data, test procedure, expected results, actual results, remarks.
3. When the testing partner gets the first requirement document, analyze it, extract test points, write test cases, and then call development, product and related personnel to review the use cases.
4. Common methods for writing test cases: equivalence class division method, boundary value analysis method, error inference method, flow chart method, etc.
5. Learn to question requirements, do not write test cases according to requirements, to understand requirements from the user’s point of view, see functions and experiences beyond requirements.
HTTP and HTTPS protocols
1. Principle of HTTP protocol
HTTP is short for Hyper Text Transfer Protocol. It is used to Transfer hypertext from the World Wide Web server to the local browser. —- self Baidu brain supplement
2. Differences between TCP and UDP
TCP and UDP are protocols in the transportation layer of the OSI model. TCP provides reliable traffic, while UDP is often used for broadcast and detailed control of traffic handed to applications. – Brain supplement on baidu
3. Get and POST
1) Get, it is used to Get information, it is only used to Get and query data, that is, it does not modify the data on the server, from this point of view, it is data secure, while Post, which will be mentioned later, can modify data, so that is one of the differences between the two.
2) Post, it can send a request to the server to modify the server, so as to modify the server, for example, we want to Post on the forum, comment on the blog, this will use Post, of course, it can only obtain data.
Three, business understanding ability
First of all, it is clear that we must understand the business. Only by understanding the business can we do a good job in functional testing, and there will be certain improvement.
When to plug into automation —– when your system is stable.
When to intervene in interface testing —– when the interface is developed.
When to intervene in performance testing —– when there is a sale, or when there is a rush, etc.
Four, the use of test tools
1. Interface test tool: APIPost
Use apiPOST interface test, input URL address, request method, parameter click send to check whether the interface is correct.
Use Jmeter to test the system performance, stress test, load test, stability test, etc
Five, automatic test code writing ability
1. UI automation writing
A. Web automation: Generally, Python + Selenium is used to write UI automation scripts for Web sites
B. App automation: Generally use Python + APpuim to write UI automation scripts for mobile terminals
2, interface automation writing
Interface automation is typically done using Python + Requests
6. Proficient in SQL
1. Common SQL statements, such as add, delete, modify, and search.
2. Familiar with database transactions, able to write stored procedures and familiar with common system functions.
3. Understand and be able to backup, migrate, restore and mirror the database.
4. Tune SQL statements and monitor the performance of statements that can be run.
5. Learn about database clusters.
Seven, Linux
1.Linux is the basic skills of the tester. There is no need to master difficult or uncommon Linux commands.
2. Junior testers often encounter bugs, which are not acknowledged or solved by developers. How can testers get rid of such problems?
According to the log level of the found bug, to view the log, locate the problem, then here first to talk about the log level. The higher the log level is, the less information is displayed.
Info: indicates the code info, excluding debugging information such as SQL statements.
Warning: Indicates code warning information.
Error: The program itself reports an error message
General bugs that do not meet requirements are displayed in the debug, and errors reported by the program itself are displayed in error.