As the technical requirements in the field of software testing become more and more clear, the job requirements of testers in the market have become more and more complex. The vast majority of enterprises are beginning to have more needs for automation testing positions. Naturally, the interview is relatively important.
As a test engineer, every interview may be an opportunity for us to be promoted. Before each interview, we may remind ourselves: have a sense of teamwork; be patient, careful, and responsible; no matter what the interviewer asks, be gentle and polite...
However, when you are asked some "inexplicable" questions during an interview, you will find that your patience is about to run out: When are interview questions so difficult?
Written part
1. Describe the phases of the software life cycle? What are the common software life cycle models?
Software life cycle refers to the whole process (from brewing to abandonment) of a computer software from function determination, design, to successful development and use, and continuous modification, supplementation and improvement during use, until the use of the software is stopped. The period starts from the receipt of the application software and ends when the software is no longer used. It covers the following areas: initial conception, requirements analysis, functional design, internal design, documentation planning, test planning, documentation preparation, integration, testing, maintenance, upgrades, retesting, phase-out, etc.
Waterfall model, iterative model, rapid prototyping model, spiral model
2. What are the commonly used testing methods for black box testing and white box testing, for example?
Black boxes have equivalence class division method, boundary analysis method, cause and effect diagram method and wrong guess method.
White box has logic coverage method, circular testing path selection, and basic path testing.
Example: In a completeness query where multiple conditions are entered at once. Using the equivalence class division rule and the boundary analysis rule, firstly using the equivalence class division method, one or more test cases with OK results can be obtained, and then multiple NG test cases can be confirmed, and then the boundary value analysis method can be used. The test cases of OK and NG are respectively extended and supplemented.
3. What are the principles of software testing?
- "Test software early and continuously" should be the motto of software developers.
- A test case should consist of test input data and corresponding expected output results.
- Programmers should avoid examining their own programs.
- When designing test cases, reasonable input conditions and unreasonable input conditions should be included.
- principles of software testing
- Pay full attention to the clustering phenomenon in the test. Experience has shown that the number of bugs remaining in a program after testing is proportional to the number of bugs found in that program.
- Strictly implement the test plan and exclude the randomness of the test.
- Every test result should be thoroughly checked.
- Properly save test plans, test cases, error statistics and final analysis reports to facilitate maintenance.
interview questions
- English version of self-introduction
- What is the understanding of testing and testing?
- What does a process for software testing look like?
- How did you test the login function in your own project?
- What is the process of completing the project you have done?
- When you get a project, how do you test it?
- What do you think will change when you study at school and leave for internships?
- Are there more courses for senior year? How many days in a week?
- rhetorical question
PS: The interviewer is really nice, tell me the general principles of some mainstream frameworks, and express some of the conditions she needs to have for candidates for this position; I answered some questions not very comprehensively, she will help me organize the language Repeat it again.
Interview software testing thoughts
1. Introduce yourself
Don't repeat the gossip about the information in your resume. Simply introduce the company's experience from near to far, then introduce the project, highlight the technical points used in the project, your responsibilities, and your performance, and guide the interviewer to ask questions that you are proficient in. skills.
2. Don’t dig a hole for yourself
Don't pull out some skills you are not familiar with in the interview, the interviewer will follow you when they hear it.
3. Reduce the embarrassment of silence
After understanding the question, think quickly and answer in a different way, or answer an answer similar to skill points.
Otherwise, you haven't figured it out for a long time. If you stay silent for a long time, it will not only cause the atmosphere to be awkward, but also increase your tension, and your brain will be even more difficult to use later.
4. Analyze the thoughts that the interviewer wants to express in the words of the interviewer
Often "Umm, yes." – Appraisal Security
Brief silence, no comment on your answer. - no play
5. The importance of automated testing
No matter what level of test engineer you are interviewing, the interviewer will ask, "Do you know how to program? Do you have any experience in automated testing?"
The pressure faced by those students who have been in the industry for a few years but are still functional tests can be imagined. After all, the software testing industry is still a technical position. Since it is a technical position, it must rely on technology to speak. Continue to master new skills. As a past person, I will give all testers some advice: a tester, you really shouldn’t be just a little bit. With the change of the system, for the current testers, it is not automation or code. How important it is, but understanding automation, understanding code, and being able to understand the implementation of the system has become a must-have skill.
Summarize
I feel that in terms of technology, I am basically satisfied with what I have mastered, but I lack experience in large companies and large projects.
In fact, step by step, it is not just as simple as brushing the questions before the interview, but more of the usual accumulation. The editor has sorted out the core knowledge of the advanced road of software testing, and it is also the knowledge points that the interviewer must ask during the interview. The chapter also includes many knowledge points, including testing theory, Linux, MySQL, Web testing, and API testing. , App testing, management tools, Python basics, Selenium related, performance testing, and more. . . . .
The above is a diagram of the knowledge architecture system for the development direction of software testing engineers that I have compiled for you. I hope everyone can follow this system and complete the construction of such a system. It can be said that this process will make you want to die, but as long as you get through it. Life will be much easier in the future. As the saying goes, the beginning of everything is difficult. As long as you take the first step, you have already succeeded in half. The ancients said, "If you don't make a small step, you can't go to a thousand miles." a lot.
As a past person, I also hope that you will take less detours. If you don’t want to experience the feeling that you can’t find materials when you study again, no one answers your questions, and give up after a few days, I will share with you some automated testing learning. Resources that hopefully will help you along the way. Friends in need can pay attention to the public number: Bean Bear, get it for free!
Including, software testing learning roadmap, more than 100 days of video tutorials, 16 assault actual projects, more than 30 software testing software, 37 testing documents, 70 software testing related issues, 40 testing experience-level articles to share, There is also a collection of 2022 software testing interviews, as well as various selected resumes for software testing jobs.
Come on, testers! If you need to improve your planning, do it, it is better to be on the road than to wait and see at the beginning.
In the future, you will definitely thank yourself for working hard now!