Test engineers in the interview when the interviewer will encounter a variety of problems mentioned, especially for people without experience often difficult for the correct answer,
So here based on my personal experience finishing part of the problem often encountered
1, submit the bug to develop a bug that this is not how you deal with?
In fact, as long as this problem based on the needs of our test document to answer it, because if the requirements document written in very clear then the developer can not refute, but sometimes the document did not explicitly demand
, So this time we need to make products people need to be confirmed, and it does not require developers argue, we take a realistic attitude just fine.
2, what would you defect management tool?
Common defect management tools are many, such as: Zen, TAPD, jira, Mantis and so on, but for most of the testers are familiar with each impossible, so when we say we answer
The most familiar like that, because no matter what the defect management tool of its defect management process is the same, so the testers can quickly get started.
3. What are the resistance encountered during testing?
Sure to encounter all kinds of resistance testing, such as developer fixes a bug longer time than expected and then compress the time we tested, then the product or who often changes in demand caused slow progress,
This time the interviewer must ask that you encounter such a situation is how to deal with?
4, the developer reduced the time we tested how to do?
This situation is common in many companies, in fact, as a prescient awareness of risk estimates will test the person in charge should do in this situation to plan the time, then they would have to test for when the plan
As much testing time, when we have a surplus of space a little bigger.
Many people think there is no way it will only allow testers to work overtime, in fact, many large companies such cases can be delayed on the line, because you want to protect the quality of the product.
5, product demand personnel changes often how to do?
This is the most small and medium companies testers encountered the most difficult problem, because it means a lot of work you are likely to be overturned to be re-started, this time we and developers are the same front,
Personally I think the best approach is to develop a process needs to change, and then under the premise of sufficient time to be agreed upon in order to develop, test requirements are changing, we are always responsible to the product backside,
With such a standard process in the design of the product who will deliberate the demand.
6, needs assessment which people participate?
Listen to a lot of small partners, said his company needs to open a review meeting is not called when we tested together, it means that the company really is not enough emphasis on the test.
Needs assessment is an opportunity to develop and test the first contact and familiar with the project, so the testing, development must participate, or even a large version of an updated review meetings managers, directors are required to attend.
7, who wrote the test plan?
Many small partners in order to give a good impression on the interviewer directly answer I wrote or wrote our manager, but there are actually testing company responsible person (usually test leader) of the project written
8, you think how can we write a test case?
1, fully familiar with the requirements document
2, using the various test methods designed for use in Example
3, in consideration of various anomalies
4, to ensure 100% coverage function points
5, streamlining the preparation of language
6, taking into account some of the functions associated
All in all we are in the interview to be fully prepared, blacksmith need its own hardware.