Having been deeply involved in the IT industry for many years, we have discovered that for a programmer, being able to go to a first-tier Internet company will have a great impact on our future development.
Many people want to say, I know this too, but it is too difficult to get into a big factory. Once you submit your resume, it will basically come to nothing, let alone get an interview invitation.
Today, I interviewed a programmer with 3 years of experience. When asked about his salary standard, he asked for 25k. However, it is undeniable that his technical foundation is indeed pretty good, and he was very confident in the interview, which immediately made several interviewers present. The officer bucked up and wanted to know more about it. As expected, he was able to answer all the automation technology questions he asked. The basic parts were also explained in detail. It was not difficult for him at all. The next step was for the HR to directly ask him how long it took for him to come to work... .
Sure enough, people are different when they have abilities, and they shine wherever they go! ! !
Check out some of the questions we asked him:
What is the purpose of software testing?
- In order to find defects in the program and ensure software quality.
- Meet user needs
What is the general process of software testing?
- After the project is approved, participate in the needs review
- Develop test cases based on requirements documents and then conduct use case review
- After the project is proposed and tested, the use cases are executed, the problem is recorded in CP4, and the problem resolution is followed up in a timely and effective manner.
- After passing the test environment test, the product undergoes acceptance testing.
What are the common types of tests? Explain each one?
- 1. Black box testing , also known as functional testing
- 2. White box testing , that is, unit testing, is usually completed by developers and tests program classes and methods.
- 3. Compatibility testing, mainly browser compatibility testing
- 4. Integration testing , that is, testing of each module
- 5. System testing, after each module test is completed, the integrity test of the entire system
- 6. Regression testing
- 7. Acceptance testing
Explain unit testing, integration testing, system testing and acceptance testing?
- 1. Unit testing, usually done by developers, tests program classes and methods
- 2. Integration testing, that is, testing of each module
- 3. System testing. After each module test is completed, the integrity of the entire system is tested.
- 4. Acceptance test. After passing the test environment test, the product or user will conduct an acceptance test to see if the product implementation meets their original design needs.
What is exploratory testing? What should be done?
When the requirements document is incomplete or there is no requirement document at all, tentative testing based on experience is the basic thinking test formed during the testing process.
What is smoke testing and how to carry out smoke testing effectively?
1. The most basic functional testing of software is usually completed by development. Only products that pass all smoke points will be more meaningful if they are tested. 2. Smoke testing runs through all stages of testing, such as integration testing and system testing. wait
What should a high-quality defect record (Bug) contain?
- 1. Record the prerequisites for the bug to occur
- 2. Detailed steps to generate bugs
- 3. Screenshots to intuitively display problems and effectively help developers quickly locate problems.
What is the life cycle of a defect ?
1 New – Submit – Assign – Repair – Verify – Verify Pass Close – Verify Not Pass Reopen
What is the difference between Alpha testing and Beta testing?
- Alpha testing: Invite users to the developer’s premises for testing. Users conduct testing in a simulated actual operating environment. The developer records user feedback issues.
- Beta testing: Testing done when development and testing are basically completed. Many different users operate in different environments. Then users regularly send the problems they generate to developers for repair (development is not on site)
- Usually there is alpha testing and then there is beta testing.
What qualities do you think should be possessed to do a good job in software testing?
- Good technical skills
- Understanding of business logic
- good communication skills
- Ability to solve and analyze problems
As a tester, how can we effectively improve communication efficiency and effectiveness when communicating with developers?
- Communicate patiently with the developer and explain to him the importance of explaining it to him to convince him to solve the problem.
- Fully respect the other person, and don’t underestimate him even if he has a low-level bug.
- Be tolerant to others and put yourself in others' shoes. Even if the developer refuses to cooperate due to pressure or other reasons, you must calmly communicate with him and discuss the priority of bugs.
- Communicate more often with developers, whether it’s work or life issues, but testing must have its own principles and be responsible for the quality of the products tested.
- Locate the problem yourself first to help development narrow down the scope of investigation.
What do you think software test engineers need to do in a team? What's the value?
- During the product demand meeting, you can put forward some suggestions that fit the user's needs from the user's perspective.
- During the testing phase, based on your own understanding of the project and professional testing skills, try to detect as many problems as possible before the project goes online to ensure product quality.
- Conduct reasonable and effective risk assessments for problems that arise during the testing process.
- Those who fail to pass the strict quality control test must not be released for production.
What is your greatest interest in software testing?
- The industry prospects are relatively good, and more and more companies have paid more attention to testing in recent years.
- The longer the test lasts, the more difficulties and challenges you face. While solving problems, you also improve your own abilities.
- My personality is outgoing and cheerful, and I can easily communicate with products and developers to get things done and get twice the result with half the effort.
What are your career plans for yourself?
If there is a chance, I would like to do advanced testing first. I would like to develop in the direction of management. I am currently working as a test team leader at Ctrip, and I will also prepare for future management.
In your previous work, what bugs did you find that had a big impact or impressed you? Why?
Impressive bug: In a recent project, x is an order and n is a qmq message. The order service is called to automatically issue an order. During the test process, I added a manual order to the development proposal - as an issue where the order failed or was not issued. To compensate, the development team strived to ensure that there would be no failure to issue orders during production, but I was later persuaded to add a manual issue function before going online. On the second day after going online, there was a problem with the company's qmq framework, which caused a delay in message consumption. As a result, orders within a period of time could not be automatically issued. At this time, everyone manually issued orders to solve some orders. After the incident, the development confirmed my proposal at that time. The bug fix is correct
In your past experience, what is the most difficult problem you have solved?
Environmental issues are a problem faced by all testers; among the many problems solved, the unavailability of the test environment and the inability to quickly intervene in the test are still prominent. Once in an environment that had not been used for a long time, based on experience and clog positioning, the calls between various services were adjusted step by step.
What was your biggest gain from your previous work or study? What did you learn?
- Business accumulation
- Through various automations, such as UI automation, job automation, and API automation, I not only improve my coding skills, but also play a decisive role in regular weekly releases.
- During the long-term testing process, I improved my ability to solve problems.
How do you conduct testing without any documentation?
- Try to obtain other documents, such as some design documents developed - outline design, functional design, detailed design
- Try to find similar project documents online. If you are lucky, you can find similar documents from the company's database.
- According to the developed interface or design document and divided into functional modules, roughly write some use cases, and then conduct exploratory testing, and gradually improve your own use cases during the testing process.
Finally, I would like to thank everyone who reads my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, if you can use it, you can take it directly:
These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey. I hope it can also help you! Anyone in need Partners can click on the small card below to receive it