Table of contents
Interface Test Interview Questions
Living Items Test Interview Questions
Performance testing basic interview questions
Interface Test Interview Questions
1. What methods are used in the design of test cases?
The most commonly used test case design methods include equivalence class partitioning, boundary value analysis, scenario , and error guessing. Among them, the boundary value method is the easiest to find errors, and the scene method is the most used. Take registration as an example: first determine the length and type constraints of user names and passwords from the requirements, write test points according to the requirements, then design test data and write test cases.
2. What are the main steps and information included in the test plan?
The test plan includes an introduction, basic test content (test purpose, test scope, test environment, test tools, testers), implementation plan (task assignment, schedule), risk control, etc.
3. What should be included in the test report? What are the test report delivery documents? What do you think the focus of the test report is?
The test report includes: introduction, basic test information, test results and defect analysis, test conclusions and suggestions, and delivery documents.
Delivery documents include test cases, submitted bugs, and test reports.
The focus of the test report is the test results and defect analysis, test conclusion.
4. The life cycle of bugs? How do you follow up on bugs?
A:
The life cycle of a bug is the process from when a bug is discovered to when the bug is closed. General defect status in the life cycle: New, Assigned, Resolved, Pending, Closed.
The specific process is as follows: 1. Create a new bug and record the bug to the defect management platform ; 2. Assign it to the corresponding developer; 3. The developer confirms the bug; 4. The developer repairs the bug ; Update the test environment with the new code package, and then perform bug verification ; 6. If the bug has been fixed, the tester will close it directly; 7. If the bug to be inspected is not resolved during verification, we need to reopen > assign > resolved > pending inspection , to cycle through this process. Other states in the middle: reopen, reject, postpone, etc.; 8. If the development has not modified the status after submitting the bug, we will remind the development. For bugs that are postponed or not to be modified, communicate with the developer, and find the product to confirm whether to modify it.
Living Items Test Interview Questions
1. How to test a cup?
function test:
1. Pour in warm water to test whether the cup can hold water normally;
2. After filling the water, can you drink water normally;
3. Whether the cup has heat preservation function, and whether the heat preservation function is normal;
4. After tightening the lid, turn the cup up and down, left and right , to see if the cup is leaking;
Capacity test:
1. Pour warm water and test the maximum water capacity of the cup;
2. Whether the maximum water capacity of the cup complies with international measurement standards and whether there is no error;
Compatibility testing:
1. Pour different liquids (ice water, hot water, warm water , fruit juice , wine) respectively, and test whether the cup is normal;
2. Use the cup to make tea, coffee, milk, and test whether the cup can be used normally;
3. Whether the cup can be used normally in strong wind, heavy rain, heavy snow and high temperature weather;
4. Will the cup explode if it is placed in a microwave oven?
5. When the cup is put in the refrigerator , will it melt?
Security testing:
1. Whether the material of the cup complies with international standards and whether it is harmful to the human body;
2. Whether the cup will chemically react with the liquid it contains to produce harmful substances (bacteria, viruses, etc.);
3. Whether the cup will undergo chemical reaction at high temperature or sub-zero temperature to produce harmful substances;
4. Whether the cup will undergo a chemical reaction and produce harmful substances when placed in a microwave oven or refrigerator;
5. After the cup is damaged, is it easy to cause harm to the user;
Performance Testing:
1. Pour water at 0-100 degrees Celsius respectively, whether it can withstand different temperatures;
2. Pour different liquids and let it stand for a period of time (more than 24 hours), whether the cup will leak;
3. Whether the thermal insulation of the cup meets the requirements;
4. Whether the heat resistance of the cup meets the requirements;
5. Whether the cold resistance of the cup meets the requirements;
pressure test:
1. Press the cup with your hand to see if it is easy to deform;
2. How damaged is the cup when it is dropped from different heights;
3. Fill the cup with a small amount, a half cup, and a full cup of liquid to see if the loading capacity meets the design standard;
Usability test:
1. Whether the shape of the cup is easy to pour liquid into;
2. Whether the weight and size of the cup are appropriate;
3. Whether the cup is non-slip;
4. Whether the mouth of the cup is smooth and convenient for drinking;
5. Whether the cup will fade when held in the hand;
6. Whether the cup is insulated and not hot;
UI tests:
1. Whether the cup design conforms to the required specifications;
2. Whether the shape and color of the cup meet the aesthetic needs of the public;
3. Whether the cup is marked with a scale, Logo, etc.;
Interactive test:
Whether the interaction between the cup, the cup cover and the cup holder conforms to the user's usage habits;
Documentation test:
Does the user manual describe in detail the usage, restrictions, and conditions of use of the cup;
Maintenance test:
After the cup is damaged, whether there are repair measures;
Performance testing basic interview questions
1. Explain the names and specific meanings of commonly used performance indicators
Performance testing is to test various performance indicators of the system by simulating various normal, peak and abnormal load conditions through testing tools. Verify whether the software system can meet the performance indicators proposed by the user, discover the performance bottlenecks in the system and optimize them.
The performance indicators are divided into two aspects:
- System indicators: indicators related to user scenarios and requirements;
- Resource indicators: indicators related to hardware resource consumption;
System indicators :
Response time : that is, system response time (Transaction Response Time), the time taken by the application system from sending a request to receiving a response from the client, is the software performance business experience that users are most concerned about from the perspective of users. Response time is the sum of network response time and application response time;
Generally, the response time is within 2s, and users will feel more satisfied;
Between 2s and 5s, users can barely accept it;
If it is longer than 8s, the user may not accept it and refresh the page or leave;
Average response time : the average time spent on all requests;
Throughput : the number of customer requests that the system can handle per unit time, which directly reflects the performance carrying capacity of the software system, and is calculated by dividing the number of completed transactions by the time;
Number of concurrent users : Concurrency is mainly for the server, the number of online users who interact with the server at the same time (pointing to the server to send requests);
Number of online users : the number of users accessing the system within a certain period of time, such as multiple users browsing the web, but not making data requests to the server at the same time, needs to be distinguished from the number of concurrent users;
The maximum number of concurrent users : There are two ways to understand it. One is to simulate real user access from a business perspective, which reflects the number of concurrent business users, which refers to the number of users accessing the system within the same time period. The other is to consider the pressure on the server side. The "number of concurrent users" here refers to the number of clients who send requests to the server side at the same time. It is generally used in conjunction with concurrency testing (Concurrency Testing) to reflect the load on the server side. Maximum number of concurrent accesses;
Transaction : It can be regarded as an action or a collection of a series of actions, such as login, from the beginning of login to the end of login as a transaction.
TPS : Transaction per second, the number of transactions or transactions that the system can process per second, that is, the server's ability to respond to client requests, is an important indicator to measure the system's processing capabilities.
Throughput : the amount of data transmitted by the network (the number of requests processed by customers);
Throughput rate : the amount of data successfully transmitted by the network per unit time (can be seconds/minutes/hours/days), such as the number of requests/second, the number of pages/second;
Number of hits : the number of HTTP requests received by the Web Server;
Click rate : HPS, the number of HTTP requests submitted by users to the Web Server per second;
APP interview questions
1. Please introduce the APP testing process?
The APP testing process is similar to the web testing process and is divided into the following seven stages:
1. Write a test plan according to the requirements specification;
2. Develop a test plan, mainly the allocation of test tasks, testers and test time;
3. Test preparation, including setting up the test environment, preparing test data, and determining the test method;
4. Design and write test cases, review and supplement test cases;
5. When executing the test, first conduct a smoke test, and then test the main functional process, including a single functional module of the client, and functional business logic, functional interaction, and regression testing;
6. Submit test results, including test cases and test plans;
7. Routine maintenance test;
MySQL interview questions
1. How does MySQL implement the ACID feature?
A = atomicity: undo log to ensure atomicity, rollback after exception or execution failure;
C = Consistency: The ultimate purpose of the transaction requires guarantees at the database level and at the application level;
I = Isolation: The read and write between transactions rely on the MySQL lock mechanism to ensure isolation, and the write operations between transactions rely on the MVCC mechanism (snapshot read, current read) to ensure isolation;
D = Persistence: redo log and binlog to ensure persistence, to ensure that when MySQL is down or power outage, the data can be finally saved to disk through redo log;
-
How does MySQL make large table DDL?
MySQL 5.7 already supports native online DDL statements, but it involves some parameter configurations, and it may not be known how appropriate the configuration is, so generally large tables still use percona-tools.
3. What are the principles and benefits of MySQL master-slave replication?
Master-slave replication means that data can be replicated from a MySQL database server master node to one or more slave nodes. MySQL adopts the asynchronous replication method by default, so that the slave node does not have to keep accessing the master server to update its own data, the data update can be performed on a remote connection, and the slave node can replicate all databases in the master database or a specific database, or a specific table .
The benefits of MySQL master-slave replication :
- In a complex business system, if there is a SQL statement that needs to lock the table, resulting in the temporary inability to use the read service, it will greatly affect the running business. Using master-slave replication, the master library is responsible for writing and the slave library is responsible for reading. In this way , even if the main database locks the table, the normal operation of the business can be guaranteed by reading the slave database.
- Do hot backup of data.
- Conducive to the expansion of the structure. The business volume is increasing, and the I/O access frequency is too high for a single machine to satisfy. At this time, multi-library storage is used to reduce the frequency of disk I/O access and improve the I/O performance of a single machine.
Summarize
Due to space limitations, I have summarized all the interview questions into a document. If you need it, you can click the business card below to find me for free, and there are various resume templates. Real Dachang interview questions and practical project tutorials are waiting for you, don’t miss it.
