During a software testing interview, you can ask the interviewer a few questions

The interview is the threshold for us to enter a company, and only after passing the interview can we enter the company to work, and your interview results are closely related to your salary and benefits. So how can you successfully pass the interview and get HR's approval? What should I pay attention to in the interview software test?

Software testing interview FAQs are usually divided into two broad categories, one that looks at professional skills and the other that looks at your stability and effort.

1. Examine professional skills.

In terms of professional skills, you need to have a solid test foundation. You can search for interview questions from big IT companies to fill in the gaps, or you can review what you have learned and prepare for more background knowledge for the specific position you are interviewing. There are not many shortcuts to this, and even if you happen to pass an interview for a position that is higher than your ability because you have memorized some difficult questions, you will be fired if you are not qualified for the job during the probationary period.

So consolidate what you know within your ability and then try to avoid mistakes.

2. Examine your stability and level of effort.

The second category mainly examines your stability and level of effort, and even career planning and other issues. For example, ask how you think about testing work, whether you can accept overtime, and your future career plans. This kind of question cannot be agreed to unreservedly for the sake of work for the sake of work, and if you accept overtime, then you will also resign because you can't stand the 996 work system.

Therefore, it is appropriate to ask about the specific frequency and intensity of overtime, and make a commitment within an acceptable range. Regarding your future career plan, if you are ambitious and want to be promoted and raised, then you can show it appropriately. If you just want stability at the moment, then you can also humbly say that you will try to accumulate experience at this stage and consider it when the opportunity comes.

These kinds of questions are flexible, and there is usually no fixed answer, as long as you don't agree to any conditions too hypocritically, or simply refuse them without leaving room for anything. The main thing is to show a humble attitude and negotiable margin in the process, and I believe that it will definitely win the favor of HR and leaders.

The above are some methods and skills for common problems in software testing of Sichuan excellent employment, we have mastered the technology, if you want to pass the interview and get an offer, you still have to prepare for the interview and have a good performance in the interview. I believe that as long as you prepare carefully and practice diligently, it should not be a big problem to pass the interview.

Because when you are new to a new company, when the interviewer asks: What else do you want to ask, you can seize the opportunity to show your charm, such as, 1If I am hired by your company, what do I need to improve to better integrate into your company's work? 2.

If I am hired by your company, how can I make up for the lack of relevant work experience?

It is inevitable to ask about the basics of software testing, such as what is black box and white box testing, the difference, etc.; What do various tests such as performance testing, stress testing, etc. mean? What is a test case? How to design?

Then you might give an example and ask you how to design a test case and how to start testing.

That's pretty much it.

Hope it helps.

You go to the forum section of the 'China Software Testing Alliance'** to find it, there is an interview section in it, which is full of real interview questions.

1.Theoretical knowledge of software testing, such as what software testing is, the purpose of software testing, what qualities software testers should have, black box testing methods, and white box testing methods.

Or knowledge of C++.

3.The interviewer learns about your personality traits through conversations with you.

You've met a few of them, so you should be able to figure out why you've failed. ~~

Let me probably say that if you are interviewing for software black box testing, you will probably ask about the writing method of the test case, such as cause and effect diagrams, equivalence class divisions, boundary values, scenario methods, etc., and how they are used, and there will be questions on the spot, such as how you should test if you are given a cup, etc.

If you're interviewing for a white box or performance test, that's another story. If you are interested, you can chat individually.

The written test is basically a process, and no one will carefully see if your answer is correct or not. Generally, the interviewer will get to know your specific situation by chatting with you. The interviewer is also an employee of the company, but he is a little cunning, don't be afraid, you just treat him as a stranger asking for directions.

Whatever he asks, you just have to answer.

Good luck!

It depends on what level you are.

Beginner level is easy, intermediate level is more difficult, and advanced level is difficult.

You have to look at luck, and the interviewer looks at the impression of you.

In fact, no matter what you are applying for, you must pay attention to the appearance of the first person. Dress formally, and there is your work (if you don't make some up), and nothing else, you just pose with him at will, so that he knows that in addition to your skills, you are also very capable of collusion.

As follows:

1. What is a bug?

Answer: Software bugs refer to problems in the software that do not meet the needs of users.

Common software bugs fall into the following three categories:

There is no functionality implemented.

The required features are completed, but there will be some functional or performance issues when running.

Implements redundant functions that users do not need.

2. Briefly summarize the defect report and explain what items are included?

A: Defect reports are no longer written in paper files, but with dedicated test management tools (such as testdirector), which is convenient for defect management. In these tools, each defect is entered as a record into the specified defect management system.

The defect report includes: software name, version number, function template, defect number, corresponding use case number, writing time, writer, tester, expected result, actual result, defect description, severity, and priority.

3. After the developer fixes the defect, how to ensure that other functions are not affected?

4. When is the functional test?

A: Functional testing is to run all the functions of a software system for a specified period of time to verify that the software system is free of serious errors.

5. Why did you choose to test this line?