Shulou(Shulou.com)06/02 Report--

In this article, the editor introduces in detail "what are the common problems in the software test interview", the content is detailed, the steps are clear, and the details are handled properly. I hope this article "what are the common problems in the software test interview" can help you solve your doubts? let's follow the editor's ideas to learn new knowledge.

Q1: can the test communicate directly with the customer about the requirements in the project?

A1: yes, the tester is directly involved in the initial communication with the customer, so we can have a meeting with the customer's representative directly.

A2: no, in general, we need to put the problems together and let the project manager and the test manager communicate with the customer as interfaces.

A3: no, our demand is raised by the product line, and the product line communicates directly with the customer, so we go to the product line directly about the demand.

Q2: how to solve the uncertain requirements in requirement determination?

A2: generally speaking, it will be discussed and solved within the project team, and if it is still not solved, it will be confirmed directly with the demand side.

Q3: what is the test plan and what is the test strategy?

A3: the test scheme is a question that guides us how to test, and the main content is the test point. The strategy is to guide us on what aspects to test, such as functional testing, performance testing, compatibility testing, etc., and indicate what tools we need to rely on.

Q4: what does the test plan contain?

A4: description of business functions, understanding of requirements functions, business flow charts, business tables, test points, etc.

Q5: what are the test case design methods?

A5: equivalence class, boundary value, error inference method, scene method, causality diagram, decision table.

Q6: what are the contents of the test cases?

A6:ID, title, priority, preset condition, operation procedure, expected result, actual result, tester, test time.

Q7: why do test cases need to have priorities, and what are the priorities?

A7: because the number of use cases executed in different stages is different, and the degree of importance of the corresponding functions of the use cases is also different, we are using high, middle and low levels.

Q8: how many test cases are there in your project?

A8VR 500-to 2000, specific project analysis is related to project size and granularity.

Q9: who does the test case need to be reviewed?

A9: reviewed within the test team, because our solution is reviewed by all project team members (PM/SE development and testing) and the test points in the solution are written to the level of the test case title. We are the whole project team to review, after all, testing is the last link to ensure software quality, test cases are the basis for test execution, so test cases are very important, the project team attaches great importance to the review of test cases, hoping to minimize omissions, so our test cases are reviewed by all members of the project team.

Q10: how to estimate how many test cases a project needs to write?

A10: this is evaluated according to the test points after the requirements analysis, our test points are written in great detail, so the number of test cases is almost equal to the number of test points.

Q11: can't you find that BUG's test cases are not good test cases?

A11: I don't think so. I think every use case may find defects before execution. A good test case is a complete set of test cases that can be executed by other testers. Whether the use case is good or not can't be explained by whether the BUG is found or not.

Q12: why cross-test?

A12: because you execute your own designed use case, you will execute the use case in accordance with the idea of designing the use case, and you may ignore some accidental or abnormal situations, and cross-execution may find a new BUG. Of course, if the use case has been written very carefully and the granularity is very small, the results of comprehensive cross-execution of input and output will be the same, no matter who implements it.

Q13: what is a pre-test, how is the pre-test conducted, and how long is the pre-test usually?

A13: pre-testing means that the opening has just been developed, and the test environment has just been set up. At this time, we need to test whether the various functions of the system can run smoothly and whether the business process can be completed, that is, the smoke test. This is the transfer test. It will take us about a day to switch to the test.

Q14: what is your testing career development?

A14: the more testing experience, the higher the testing ability. So my career development takes time to accumulate, step by step towards a senior test engineer. And I also have a preliminary career plan. I have accumulated testing experience in the first 3 years. I ask myself according to the main points of how to be a good test engineer, constantly update myself, correct myself, and do a good job in testing tasks.

Q15: what qualities do you think testers need to possess?

A15: testing should have a certain degree of coordination, because testers often have to contact the developer to deal with some problems, if not handled properly, it will cause some conflicts, so it will be difficult to do the work. And testers have to be patient, and sometimes it's boring to do tests. Apart from patience, testers can't let go of every possible error.

Q16: why can you do testing?

A16: although my testing technology is not very mature, I think I can still be qualified for the job of software testing, because software testing requires not only good skills, but also certain communication skills. Patience, carefulness and other external factors. Taken together, I think I am qualified for the job.

Q17: what is the purpose of the test?

A17: the purpose of testing is to find out the errors in the software product, so that the software can meet the requirements of users as much as possible. Of course, it is impossible for software testing to find all the errors.

Q18: what are the stages of testing?

A18: generally speaking, it is divided into five stages: unit testing, integration testing, confirmation testing, system testing, and acceptance testing.

After reading this, the article "what are the common problems in software testing interviews" has been introduced. If you want to master the knowledge points of this article, you still need to practice and use it yourself to understand it. If you want to know more about related articles, welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.