During the graduation season, a large wave of job seekers came. Do you have loopholes every time you interview and feel that you haven’t answered the interviewer’s questions well?
1. Self-introduction
I believe you all don’t like this opening remark, but interviews all start with a cookie-cutter self-introduction. HR mainly wants to use your self-introduction to quickly find out whether you, this person, is in line with the company’s requirements.
So everyone can organize language from these aspects: working time , education background , work experience , project experience , good skills , your personality , and try to be consistent with your personal resume
The following is an example of the students in the lemon class:
Hello, my name is XX. I am from XXXX. I graduated from XXX college majoring in computer science. I have been working in software testing at XXX company for one and a half years since I graduated.
The project we are doing is mainly XXX, which is a XXX system platform, and the modules involved are mainly XXX. In the project, I have been responsible for web and app functional testing, interface testing, and stress stability testing. (Consistent with the resume project), able to independently build a test environment.
Familiar with the use of testing tools jmeter, soapui, loadrunner Fiddler Appium Monkey Postman... etc. (These are the students who graduated from the whole lemon class. According to your actual situation, you will talk about several types, because you will be asked relevant technical questions later)
Also have development experience, good at c/c++, Java, JavaScript programming language (if you have this experience, you will add it)
I am a patient and serious person, and I have a lot of confidence to do a good job of testing (not to mention, the impact is not big).
2. Tell me about the testing process of your project?
Answer: First, a demand analysis meeting will be held. Participants will have products, development and testing, mainly to discuss some of the main functional points of the demand. After that, the development was scheduled for development, and the supervisor began to write test plans and assign tasks to us.
We write test cases with reference to the requirements specifications and prototype drawings. After writing, we will conduct a use case review. If there is review and modification, we will modify and organize the final use case version. After the developer version is compiled, we will first make predictions, mainly for the main Functional business is tested.
If the main business process does not pass, directly return to the development for modification. The prediction is passed, and the system is tested according to the test cases. During the test, bugs are submitted, tracked, and regression tests are performed until there are no serious bugs to meet user needs. After the test is completed, test reports are written, and after the launch, pay attention to whether the web is running normally.
ps: (This is the case of the lemon class students) You can follow your actual company's situation, because every company has its own process, it is impossible for all companies to be very standardized. But I suggest that everyone is better to be standardized
3. Introduce a project you have done recently?
The project statement can be the whole first, then the partial, the whole can be quantified (project size, time cost, labor cost), then the test environment (if you know it), and then the role responsibilities.
Cases of lemon class students:
This XXX project is a XXX system platform, the main business scope is XXX. The project module is mainly XXX. The project will enter the project establishment, design and development from March this year (the time is changed according to the resume time), and the test release will be completed at the end of June (the time is changed according to the resume time).
On our testing side, there are three people responsible for this project. After the requirements review is completed, the boss will give us a test task and write test cases. Which modules I am mainly responsible for (explain according to your specific situation).
The first round of testing took a week to complete. The entire project was tested for more than a month. A total of 4 rounds of testing were conducted. Nearly 100 bugs were found in the first round. (The few bugs left before the project went live are To what extent, how did you deal with it in the end (say this sentence if you are prepared))
4. A bug is submitted and the development considers it to be not a bug. What should I do as a test?
Answer: First confirm whether the development environment is consistent with your own test environment (sometimes the development verifies bugs in the environment where they have updated the code, so the bug does not appear, but it will appear on the test environment), and confirm that the test environment can be reproduced. Now, if it is confirmed that it is a defect, maintain effective communication with the development:
If it is a low-level advisory bug, you can log it to the bug platform first, and keep the communication first;
If it is a problem with a higher level of bug, the expected results of the corresponding requirements document and the development instructions will be more convincing; patiently explain the harm of the bug, find the product to confirm if it fails, confirm that the bug is noted and assign it to the development again
5. How to deal with bugs with low recurrence rate?
Answer: Try to reproduce the problem in the environment first, keep the browser environment, the specific account where the problem occurred, and so on. If you still can't reproduce it after several attempts, you should also record it on the bug platform.
Describe the characteristic steps of the problem as clearly as possible, attach screenshots of the problem and log screenshots, and indicate the occasional occurrence; if the project time permits, the bug level is high, and development assistance is required to reproduce; if time does not allow, record it on the bug platform and follow up later .
After you have answered the above, the interview is basically half of the success. Of course, it is mainly based on your actual situation. The interview will continue to be broadcasted later. What questions do you encounter during the interview did not answer well. You can leave a message in the background, we will make a special topic next time~
Above are some videos and interview questions I collected.
For software testing friends, it should be the most comprehensive and complete interview preparation warehouse. In order to better organize each module, I also refer to many high-quality blog posts and projects on the Internet, and strive not to miss every knowledge point. Friends relied on these contents to review, and got offers from big factories such as BATJ. This warehouse has also helped many software test learners, and I hope it can also help you.
Follow my WeChat public account [Programmer Erhei] Get it for free