Speaking of the development of software testing in recent years, it has actually undergone tremendous changes quietly. In the past few years, with the rapid development of the Internet industry, software testing talents were scarce, and the low threshold and high salary prompted a large number of graduates and career changers to flock in. But now, software testing is developing too fast. Looking at the major recruitment websites, the demand for basic functional testing positions has gradually decreased and is basically saturated. Many software testers are in a free state and start to be at a loss. They don’t know what they should learn to improve testing. technology? I don't even know what requirements companies have for testers now? It can be described as "stressful".
If you want to learn automated testing, here I recommend a set of videos for you. This video can be said to be the number one automated testing tutorial on the entire network at station B. At the same time, the number of online users has reached 1,000, and there are notes to collect
https://www.bilibili.com/video/BV17p4y1B77x/?spm_id_from=333.337.search-card.all.click
Today, the editor shares common interview questions and reference answers for test engineers, hoping to help you.
Notes for interviews
1. Software testing interview guidance questions: self-introduction
95% of companies will ask this question, but most of the job seekers’ answers are too simple and plain. Some people will introduce their name, age, work experience, hobbies, personality, etc. In fact, you don’t need to say these things. It is also clear at a glance. The reason why companies like to ask this question is to check whether the applicant is qualified for the job and bring value to the company. It specifically covers the following points:
- best skills
- The most successful project ever done;
- The part that embodies personal value in the team;
- Know the most technical fields and so on...
The above has nothing to do with daily work and study, but you must show your positive attitude and outstanding ability, and only by seeking truth from facts and answering calmly and calmly can you convince the company. And a special reminder that in addition to examining a person's ability, the interviewer also attaches great importance to the person's politeness and behavior, so saying "thank you" after answering each question can add points to your interview.
Frequently Asked Questions about Interview Guidance
1. What are the performance test contents?
1) Load testing: For distributed networks, test the response of the system by testing different numbers of users, focusing on performance indicators and different performances of the system. The same is a software test engineer, why is the monthly salary of performance testing higher?
2) Stress test: Multi-user high-concurrency test (300,000-500,000) under high pressure, mainly focusing on how the system crashes. (memory leak, cpu unresponsive, database unresponsive, network congestion)
3) Capacity test: the maximum number of relevant data supported by the system, the maximum data volume of the database, and the number of users.
2. What is the role of performance testing?
1) At present, the vast majority of applications are distributed applications based on the network. We cannot know the number of users and the uncertainty of user scenarios. As a result, when testing the system, it is not only the function, business logic, interface test, but also the system performance. . One user is fine, but once there are more users, various problems may occur, so system performance testing is required.
2) The number of users increases, the system debt increases, and the system performance test is carried out to know the number of concurrent users the system can withstand, whether the bandwidth is sufficient, whether the CPU is sufficient, whether the memory is sufficient, and whether the hard disk speed can keep up. From the perspective of the server, test whether the server can carry multiple concurrent users, whether the system is stable, and the response time speed from the perspective of users.
3. Performance test evaluation index
1) Response time (response time): Evaluate the response speed of the system from the user's perspective. Usually, the empirical value of the response time is: 2s is smooth, 5s is available, and 10s is slow.
2) Throughput/rate: hard disk IO (reading and writing), network IO (uplink and downlink bandwidth), cupIO, server processing capacity, and the number of pages opened by the client.
3) Transaction processing capability (TPS tansaction per second): Opening a page, logging in to the server, implementing message sending, etc., is called a transaction.
4. The core principles of performance testing and the development of testing tools
The core principles of performance testing and the development of testing tools are mainly based on the first two points:
1) Based on protocol (front-end and back-end communication mechanism), interface (decision and front-end interaction) and code (back-end). Network-based distributed architecture: Based on network protocols to simulate users sending requests.
2) Multi-threading: Simulate multi-threaded operations, multiple people operate at the same time, and simulate large loads (functional testing is used to test functions).
3) Simulate the real scene: In the real network environment, the user's operation time is uncertain, the operation is uncertain, the obtained data is accurate, the scene is wrong, and the data may not be available.
5. What is agile testing?
Emphasis is placed on testing the system from the perspective of the user (customer) who uses the system. Focus on continuously and iteratively testing newly developed features, de-emphasizing the rigorous testing phase of the traditional testing process. At the same time, it is necessary to intervene in the test as soon as possible, and continue to conduct regression testing to ensure the correctness of the previously tested content.
6. How to conduct test requirement analysis?
According to my actual work, the test requirements analysis is generally broken down from coarse to fine, collect all the requirements-related information in the first pass, go through it roughly, draw the basic flow, and record the doubts. The second time you look closely, you can diverge from the basic flow through the mind map.
7. What is the life cycle of a defect?
Bug submission, bug confirmation, bug opening, bug fixing, bug regression, bug closing.
8. How to ensure the requirement coverage in test design
Comprehensive test requirements analysis and design of use cases from business and technical perspectives not only need to consider the feasibility of current requirements and divergent thinking about related demand points. At the same time, other processes must follow relevant industry and business norms and so on.
9. What are the types of general defects?
Requirements, data, logic, performance, functionality, security, compatibility, change, ease of use, etc.
10. How to ensure the quality of software testing?
From the description of each stage of the overall project process, software quality must be well controlled in every link.
11. What are the contents of the test plan?
Product testing background, testing resource allocation, testing strategy, risk response measures, testing methods, testing tools, testing cycle, testing reference materials.
12. How to conduct regression testing?
Described in stages. But each stage needs to calculate the scope of regression testing and the time required.