Software Test interview questions (partial collection)

Software Test interview questions (partial collection)
01. Why should I perform software testing in a team?
Because it is difficult for a software without tests to know the quality of the software before release, just like ISO quality certification, testing also requires quality assurance, in this case, you need to perform software testing in the team. Discover problems in the software during the testing process, let the developers know and modify the problems in a timely manner, and obtain the quality of the software from the testing report when the problem is about to be released.

02. In the past, what have you been engaged in? Which part of the job is best?
I have performed Web Testing, background testing, and client software, including functional testing, performance testing, and user experience testing. What is best at is functional testing.

03. What types of software testing are familiar to you? Try to compare the differences and connections between these different 04. Test types (such as function test and performance test ......)
Test types include function test, performance test, and interface test.
Functional testing accounts for the largest proportion in testing. Functional testing is also called black box testing. Is to regard the test object as a black box. When using the black box Testing Method for Dynamic Testing, You need to test the functions of the software product, and do not need to test the internal structure and processing of the software product. Black box technology is used to design test cases in the following ways: equivalence classification, Boundary Value Analysis, Error Prediction, cause and effect, and comprehensive strategies.
Performance testing uses automated testing tools to simulate a variety of normal, peak, and abnormal load conditions to test the system's performance indicators. Both load testing and stress testing are performance tests. The two can be combined. Through the load test, determine the system performance under various workloads, the goal is to test the changes in the system performance indicators when the load increases gradually. Stress testing is to determine the bottleneck of a system or the performance points that cannot be received by the user, to obtain the maximum service level test that the system can provide.
Interface testing: the interface is the most direct layer for software-to-user interaction. The quality of the interface determines the first impression of the software. In addition, the well-designed interface can guide the user to complete the corresponding operations and play a wizard role. At the same time, the interface, such as the face of the same person, has the direct advantage of attracting users. A well-designed interface can give users a relaxed and pleasant feeling and a feeling of success. On the contrary, the failure of the interface design gives users a sense of frustration, the practical and powerful functions may be lost in the fear and abandonment of users.
The difference is that functional testing focuses on all the features of the product, taking into account each detailed feature, each possible functional problem. Performance testing focuses on the stability and robustness of the entire product under multi-user concurrency. Interface tests focus more on user experience. Are users easy to use, easy to understand, standard (shortcut keys and so on), and beautiful (whether they can attract users' attention) when using this product ), is it safe (do not enter invalid data in the foreground as much as possible. Of course, the warning should not be too rude considering the experience )? When performing a performance test, it may be a function point first. First, ensure that its function is correct, and then consider the performance test of this function point.

04. What do you think is the key to designing test cases?
The key to white-box test case design is to cover as many internal program logic results as possible with fewer Use Cases
The key to the Black Box case design is also to overwrite the module output and input interfaces with fewer use cases. It is impossible to perform a full test. The most problems can be found with the least number of use cases within a reasonable period of time.

05. Try to compare the differences and connections between black box testing, white box testing, unit testing, integration testing, system testing, and acceptance testing.

Black box testing: the functional design specifications of products are known. You can perform tests to verify that each implemented function meets the requirements.
White-box testing: it is known that the internal working process of the product can be tested to verify whether each internal operation meets the design specifications and whether all internal components are inspected.

The software black box testing means that the testing should be performed at the software interface. In this way, the test object is regarded as a black box. The tester does not consider the logical structure and internal characteristics of the program, but only according to the specification of the program, check whether the function of the program complies with its function description. Therefore, black box testing is also called function testing or data-driven testing. Black box testing mainly aims to discover the following types of errors:
1. Are there any incorrect or missing functions?
2. Is the input correct on the Interface accepted? Can I output the correct result?
3. Are there any data structure errors or external information (such as data files) access errors?
4. Can the performance meet the requirements?
5. Are there any initialization or termination errors?

The white box test of the software is to carefully check the procedural details of the software. In this way, the test object is regarded as an open box, which allows the tester to design or select a test case to test all the logical paths of the program using the logical structure and related information in the program. Check the program status at different points to check whether the actual status is consistent with the expected status. Therefore, the white-box test is also called the structure test or logic-driven test. The white box test mainly aims to check the program module as follows:
1. test all independent execution paths of the program module at least once.
2. You can test all logical judgments in either case of true or false.
3. Execute the loop body within the loop boundary and running boundary.
4. test the effectiveness of the internal data structure.

Unit testing (Module Testing) is a small piece of code written by developers. It is used to check whether a very small and clear function of the tested code is correct. Generally, a unit test is used to determine the behavior of a specific function under a specific condition (or scenario.

Unit testing is done by the programmer himself, and the ultimate benefit is the programmer himself. In this case, programmers have the responsibility to write functional code and unit tests for their own code. The unit test is executed to prove that the behavior of this Code is consistent with what we expected.

Integration Testing (also called Assembly testing, Joint Testing) is a logical extension of unit testing. The simplest form is to combine two tested units into one component and test the interfaces between them. In this sense, components refer to the integration and aggregation of multiple units. In practical scenarios, many units are combined into components, and these components are aggregated into a larger part of the program. The method is to test the combination of fragments and expand the process. Test Your modules with modules in other groups. Finally, all modules that constitute the process are tested together.

System testing is to assemble the tested subsystem into a complete system for testing. It is an effective way to check whether the system does provide the functions specified in the system solution manual. (Common joint debugging tests)

The purpose of system testing is to conduct a comprehensive test of the final software system to ensure that the final software system meets product requirements and follows the system design.

Acceptance testing is the last test operation before the software is deployed. The purpose of the acceptance test is to ensure that the software is ready and end users can use it to perform the stated functions and tasks of the software.
The acceptance test indicates to future users that the system can work as required. After integration testing, all modules have been assembled into a complete software system according to the design, and interface errors have been basically ruled out. Then, the effectiveness of the software should be further verified, this is the task of acceptance testing, that is, the functions and performance of the software are as reasonably expected by the user.

06. What is the purpose of the test plan? What are the content of the test plan? Which of the following are the most important?
The software testing plan is a programmatic document that guides the testing process, includes Product Overview, test strategy, test method, test area, test configuration, test cycle, test resources, test communication, risk analysis, and so on. With the help of the software test plan, project members participating in the test, especially test managers, can clarify the test tasks and test methods, maintain smooth communication during the test implementation process, and track and control the Test Progress, changes during the test.
There is a strategic and tactical relationship between the test plan and the test detailed specifications and test cases. The test plan mainly plans the scope, methods, and resource configuration of the test activities from a macro perspective, the detailed test specifications and test cases are the specific tactics to complete the test task. Therefore, the most important part is the test strategy and method (it is best to review it first)

07. What do you think is the key to a good test plan?
1. Clarify the test objectives and enhance the practicability of the test plan
The important purpose of preparing a software test plan is to enable the test process to discover more Software defects, so the value of the software test plan depends on its ability to help manage test projects and identify potential Software defects. Therefore, the test scope in the software test plan must cover the functional requirements highly, and the test method must be feasible. The test tool is highly practical and easy to use. The generated test results are intuitive and accurate.
2. adhere to the "5 W" rule and clarify the content and process
"5 W" Rules refer to "what", "why", "when", and "where) "," how )". Using the "5 W" rule to create a software test plan can help the test team understand the purpose of the test (why), clarify the scope and content of the test (what ), determine the Test start date and end date (when), identify the test method and tool (how), and provide the test documentation and software storage location (where ).
3. Adopt review and update mechanisms to ensure that the test plan meets actual needs
After the test plan is written, if it is not reviewed, it is directly sent to the test team. The test plan content may be inaccurate or missing, or the software requirement change may cause the increase or decrease of the test scope, however, the content of the test plan is not updated in a timely manner, misleading the test execution personnel.
4. Create test plans, test detailed specifications, and test cases respectively.
Detailed test technical indicators should be included in the detailed test specification documents created independently, place the test cases used to guide the test team to perform the test process in the independently created test case document or test case management data library. There is a strategic and tactical relationship between the test plan and the test detailed specifications and test cases. The test plan mainly plans the scope, methods, and resource configuration of the test activities from a macro perspective, the detailed test specifications and test cases are the specific tactics to complete the test task.

08. What test case design methods are familiar to you? Use specific examples to describe the application of these methods in the test case design.
1. Division of equivalence classes
Division equivalence class: an equivalence class refers to a subset of an input field. in this subset, each input data is equivalent to exposing errors in the program. it is also reasonably assumed that testing the representative value of an equivalence class is equal to testing other values of this type. therefore, we can reasonably divide all input data into several equivalence classes, and take a data in each equivalence class as the input conditions for testing. Then we can use a small number of representative test data. A good test result is obtained. there are two differences between equivalence classes: Valid equivalence classes and invalid equivalence classes.

2. Boundary Value Analysis
The boundary value analysis method is complementary to the equivalence classification method. Test experience tells me that a large number of errors occur on the boundary of the input or output range, rather than inside the input and output range. therefore, you can design test cases for various boundary conditions to identify more errors.
When using the Boundary Value Analysis Method to Design test cases, the boundary condition should be determined first. generally, the boundary of the input and output equivalence classes is the boundary that should be tested. we should select a value equal to or greater than or less than the boundary as the test data, rather than a typical value or any value in the equivalence class as the test data.

3. incorrect estimation
Based on experience and intuition, all possible errors in the program can be inferred, so as to design the test case method in a targeted manner.
The basic idea of the error inference method: list all possible errors and special circumstances that are prone to errors in the program, and select test cases based on them. for example, many common errors in modules are listed during unit testing. errors found in previous product tests are a summary of experience. in addition, when the input and output data are 0. enter a space in the table or only one row in the table. these are prone to errors. you can select an example in these cases as a test case.

4. The Causal Method
The equivalence division and boundary value analysis methods described above both focus on the input conditions, but do not consider the associations and combinations between input conditions. considering the combination of input conditions, there may be some new situations. however, it is not easy to check the combination of input conditions. Even if all input conditions are divided into equivalence classes, there are many combinations between them. therefore, we must consider using a combination suitable for describing multiple conditions and generating multiple actions to consider the design of test cases. this requires the use of the logical model ). the Cause-to-cause method is used to generate a decision table. it is suitable for checking various combinations of program input conditions.

09. Take your previous work as an example. 10. Describe the complete process of a test case design in detail.
Let's talk about the latest test of website functions.
First, get the relevant documents (Requirement documents and design documents), understand the requirements and design ideas, and think about the test strategy (the test plan is simple). Considering the test environment and test cases, test Time and other issues.
Step 2: design test cases. The test strategy is to test the functional points of the website and then perform system tests. (another tester is responsible for the other modules, you can conduct joint debugging tests. The test of website module is basically a function test and a Interface Test (the possibility of user concurrency is very small, so do not consider it ): the input data of this website uses a table record in the database. If a data record is newly added to the table (not processed yet, there is a flag ), after the website starts, it immediately refreshes the table to obtain multiple data records and then processes them. During the process, the website completes the task after three steps. In three steps, we can design test cases for these three steps separately, covering various input situations (including data in the database and user input) as much as possible ), about 50 use cases are obtained. Interface testing, that is, what the user sees, including sending emails and page display of user information.
Step 3: Build a test environment (why do you consider the test environment at this time? Because I am familiar with the website environment and can only test this function with machines left empty.) because the environment of the website is a little different from that of other systems, it requires a complicated testing environment and requires a web server (APACHE and tomcat). However, in this case, only Tomcat is used for some websites, so you only need tomcat.
Step 4: perform the test

11. Have you ever performed performance testing? If so, 12. Describe the complete process of your previous performance tests as much as possible.
Yes, I used to perform performance tests on my website. Although it was not long (2 months), what happened at that time, I am a senior with rich experience in website performance testing.
Performance testing includes load testing, strength testing, and Capacity testing.
Load Testing: Server Load balancer is a Performance Testing Index for running programs in overload environments.
Strength Testing: it is a performance test. It runs software systems with low system resources.
Capacity Test: determines the maximum number of users that the system can process simultaneously online
When the website traffic increases gradually, we begin to consider performance testing. First, we need to write a performance testing plan and obtain the page with the highest traffic according to the operation data (if this is the first time, generally, it is the homepage, download page, and the personal account page has the largest traffic and is in a certain percentage ),

Web Server metrics:
* Avg rps: Average response times per second = total request time/second;
* Successful rounds: Successful requests;
* Failed rounds: Failed requests;
* Successful hits: Number of successful clicks;
* Failed hits: the number of failed clicks;
* Hits per second: the number of clicks per second;
* Successful hits per second: the number of successful clicks per second;
* Failed hits per second: the number of failed clicks per second;
* Attempted connections: number of attempted connections;

13. Have you used some testing tools when performing performance testing? If so, 15. Explain how the tool works. 16. Describe how the tool is applied in actual work with an example in the work.

17. What do you think is the purpose of Performance Testing? What is the key to a good performance test?

18. In your past work, 19. What content does a software defect (or bug) record contain? How can I submit high-quality software defect (Bug) records?

20. In your previous software testing work, 21. Have you used some tools to manage software defects (bugs? 22. Use this tool to describe the software defect (Bug) tracking management process.

23. During the communication between testers and 24. Developers, 25. How can we improve the communication efficiency and effectiveness? What is the key to maintaining good interpersonal relationships between testers and other members of the development team?

27. In your previous testing work, 28. What are the things that make you feel less satisfied or less satisfied? How do you deal with these things?

31. before completing this test, 32. Are you willing to talk about your work experience and experience in your previous studies and work? (May include software testing, process improvement, software development, or other aspects unrelated to this)

33. Where are your greatest interests in testing? Why?
The biggest interest is that testing is difficult and challenging! The longer you take the test, the more difficult it is to do the test. I once saw an article on the carefree test website about how to be a test engineer. A total of points are listed, some of which are related to people's character, and some need the efforts of the day after tomorrow. However, I am not sure about the points 1 and 2 related to my personality, and I am confident that I can do it well.
When I first started the testing industry, I learned some information about the tests from the worry-free testing network. At that time, it was aimed at testing that required a lot of skills. Although it was easy to get started, but it is difficult to do well, and it is more difficult than development. Although I really wanted to do development at the time (I am not absent in my professional courses because I like my major ), however, we can see that testing is more challenging than development, and we will be more determined if we want to do a good job of testing.
In less than a year and a half of the testing work, the feeling and enthusiasm at that time were not diminished (even if the environment problems, their own experience, and technical deficiencies, you can certainly understand the test ).
I think there are two points in the test process that make me feel very difficult (for me, I am very interested in difficult things). The first is the design of test cases, because the essence of the test lies in the design of the test case. before the release of the test case, what test method should be used to write the test case? (That is, test plan or test strategy). If you are just testing a new task, you have to spend some time digesting business needs and technical basics, business needs are well understood (communication with product managers and developers can achieve the goal), and the technical foundation is not that simple. This requires your conscious learning ability, such as websites, you need to know how the website operates internally and how the background responds to user requests? How to build a test environment? These require the earliest learning. At least make basic preparations before starting the test. What problems may be encountered? Are you sure you want to confirm the requirement details? These problems can be found during case design.
Second, it is time to discover bugs. This should be the most basic task for testers. Generally, most bugs can be found after testing based on test cases, there are also some bugs that need to be tested. More information is obtained from the tested versions, test cases are supplemented, and bugs are tested. How can we find bugs? This requires careful and patient detection of bugs when the test cases are effective. Each case may discover bugs, and errors may occur everywhere, therefore, the thinking should be clear during the testing process (the data stream and results of the testing process must be carefully checked, and bugs should be found in it ). It is also very important to describe the bug. Under what circumstances will the bug be generated? If the condition changes a little bit, there will be no such bug and the minimum operation steps will be used to reproduce the bug, what is the rule of this bug? If you are good enough, you can help developers locate problems.

34. What is your career development in testing?
The more test experience, the higher the test capability. Therefore, it takes time for me to develop my career and start to work for senior test engineers step by step. In addition, I have a preliminary career plan. I have accumulated testing experience in the past three years. I want to update myself and correct myself as required by test engineers at and do a good job in testing tasks.

35. What do you think are the advantages of testing?
The advantage lies in my unwavering confidence and enthusiasm for testing. Although I am not experienced enough, I have the confidence to use the basic skills required for testing in my work.

36. What is the test process during your previous work?
The company does not specify how to do the test process, but each tester has its own test process. Let me talk about the process after I continue to make corrections over the past year (I will summarize it myself and learn from my peers. Requirement Review (with developers, product managers, testers, and project managers)-> Requirement Determination (produce a specific requirement document) -> development and design documentation (the developer can output the design document before writing code)-> think about the test strategy, write the test case-> send it to the developer and test Manager (informal review case)-> receive the test version-> execute the test case (the test case may be supplemented in the middle) -> submit bugs (some bugs need to be determined by developers (serious or suddenly found out of the scope of test cases, which is difficult to reproduce ), some can be directly recorded into TD)-> developer modifications (can be quickly modified during the test)-> regression testing (new problems may be discovered, and then start running according to the process ).

37. When a developer says no 38. It's a bug, 39. How do you deal with it?
Developers say it is not a bug. There are two situations: first, the requirement is not determined, so I can do this. At this time, I can ask the product manager to confirm the requirement, and no changes are required, after the three parties discuss and determine whether to change it again. Second, this situation is not possible, so you do not need to modify it. At this time, I can first try to say what is the basis for a bug? What are the negative results if they are discovered or have problems? The programmer may give you many reasons to refute his explanation. If it still doesn't work, I can ask this question and confirm it with the Development Manager and test Manager. If it is to be modified, it will be changed. If it is not to be modified, it will not be changed. In fact, some of them are really not bugs, and I just suggest writing them into TD. There is no major problem if developers do not modify them. If it is a bug, you must stick to your own position so that the problem can be finally confirmed.

23. Why do you want to leave your current position?
Because the company's operation is not ideal, the company needs to adjust the Department system. Considering the reduction of Department staff, the company has laid off a large number of employees (6 or 7). This is my first job, I also have deep feelings for the company, because I found a career ideal (that is, testing) Here, so the company needs to streamline the staff, and I voluntarily quit. Although reluctant, I will have a new stage to play.

24: How much do you know about our company?

25: What are the most important considerations when looking for a job?
Can the nature and content of my work enable me to develop and grow.

26: why should we accept you?
You can see the objective data presented by me in my past work performance, clearly showing my best-effort work attitude.

27: Let's talk about your personal highlights.
I have a high degree of persistence. I will never give up without satisfactory results.

28. What are white box tests and black box tests? What is regression testing?

29. What are the focuses of unit testing, integration testing, and system testing?

30. What are the methods and basis for designing use cases?

31. What qualities and skills should a test engineer possess?

32. What policies does integration testing usually have?

33. What are the main functions, performance, and other features of the testing tool you have used?

34. Composition of a defect Test report

35. What factors should be taken into account when testing the Web Information Management System?

36. When will the software testing project start ,? Why?

37. What are precautions for the requirement test?

38. Briefly describe the lifecycle of a defect

39. What are precautions for testing and analysis test cases )?
How did you perform the test in your company? How is it organized?
What do you think is the ideal test process?
How did you work?
What is the lifecycle of a software test activity?
Please draw a flowchart of the software testing activity?
How to manage defects?
What is test evaluation? What is the scope of the test evaluation?
If you can perform a perfect black box test, do you still need to perform a white box test? Why?
What are the criteria for the end of the test?
In addition to alpha and beta tests, what other types of Software acceptance tests are available?
How long has the test been performed?
What projects have you done before?
What was your previous test process?
<Answer: Test Plan-test case design-test execution-Test Analysis Report>
What test tools have you used?
Why test this line?
<A: it is an emerging industry with development potential. It is also very practical and requires more skills, which is more difficult than development.>
Why is it worthwhile for their company to hire?
If I hire you, what contribution can you make to the department?
How can you see from your work that you are a self-conscious person?
Can your work be completed within the time limit? (I want to ask what is the motivation for her to ask this question)
What kind of reaction do you usually have to criticize others?
If you knew this was wrong, would you still follow the instructions of the supervisor?
What do you do if you receive a call from a Customer complaining that the problem cannot be solved?
What kind of people do you think are the most difficult to get along?
Why is it worthwhile for their company to hire?
Help the company improve the software quality and the technical level of the testing department
If I hire you, what contribution can you make to the department?
Share my testing experience and skills to improve the technical skills of the testing department
How can you see from your work that you are a self-conscious person?
Wide Scope of automatic awareness
1. Achievements
2. Quality of Work
Can your work be completed within the time limit? (I want to ask what is the motivation for her to ask this question)
With sufficient resources and reasonable workload, it can be completed on time and better than the average person.
What kind of reaction do you usually have to criticize others?
If something is wrong, you can't help it.

If you knew this was wrong, would you still follow the instructions of the supervisor?
Is there any channel for appeal within the company?

What do you do if you receive a call from a Customer complaining that the problem cannot be solved?
Why? What's the problem?
If the problem is caused by customer service, submit it to the customer service department for resolution.
If it is a quality problem, analyze the cause and make improvements in the next version
What kind of people do you think are the most difficult to get along?
Self-righteous person

What is unit test?
Let's talk about the basic qualities that software testers should possess.

Let's talk about how to control software quality in development.
Briefly describe the significance of software testing and the classification of software testing

1. Functional testing, performance testing, interface testing, and security testing (for example, only cookies are involved), stress testing (commercial websites), etc, b/S software should also adopt different testing strategies based on its specific functions.
2. Attitude, responsibility, self-confidence, keen observation, and good divergent thinking
3. Design the Development Mode first, enhance unit testing, and enhance code inspection. There is a complete white box testing method. The key is to strengthen the quality awareness of developers and improve the development of programmers to engineers.
4. Let's think about the meaning. Software testing classification, which many people divide according to various methods. There is no clear answer for you.

Understanding of the test-Basic test knowledge, is it recognized for the test? 75.
3. Talk about your work in the past-understand your experiences, provide materials for further questions, and express your abilities.
Test skills
Test Design Method and example -- Use of Test Technology
Test Tool-familiarity, can it match with the current job?
How to make a plan? How to track plans? -- Daily work ability
What should I do if the version provided by the developer does not meet the test conditions? -- Ability to work with developers
Familiar with Unix and Oracle databases? -- System knowledge?
Have you done development? What code have you written? -- Development skills
What are the explanations for reading English articles? -- Partial English proficiency
The meaning of the document-Are you good at thinking? (Simplest concept, different levels of understanding)
What can we do if we enter our company? -- Talk about your expertise
Search for an item and test the actual operation capability.
What are the methods for software testing?
Software testing process?
There is a new software. What should you do if you are a test engineer?

Which two methods are involved in software testing? What are the applicable situations?
2. What stages should a complete set of tests be composed? Each stage is described separately.
3. What types of software testing are available? Compare the differences and relationships between these different test types.
4. What is the content of a test case? Focuses on the practice of compiling Test Cases
5. What methods should be used to test the C/S structure of winform and the software for testing the web structure respectively? What are their differences and relationships?
6. When testing winform's C/S structure software, you find that the software runs slowly. What do you think is the reason? What methods do you take to check the cause?
7. Describes how to use the bugzilla defect management tool to track Software defects (bugs ).
What are your personal and career goals in five years?
You can analyze this question to understand your planning capabilities. Through this question, the interviewer can also know whether your goals meet the company's requirements for you.
I want to consider this question at some point in the future. Nowadays, enterprise leaders change frequently. I think it is ridiculous to make too many personal plans, isn't it?
Comments are a type of objectionable answer. First, when someone wants to understand your goals, the popular saying "some time in the future" does not work. Second, the saying that enterprises are very fragile and leaders change frequently is undoubtedly objectionable and unreasonable. Finally, I think it is ridiculous to make a plan. I look down on this question and ask the interviewer. These are all doomed to the failure of such job seekers.
Correct answer: within the five years from now on, I hope to stay in a good position for several years, and it is better to have a promotion, and then I look forward to the next step. For me, whether it is upgrading up or horizontal transfer within the enterprise, I hope to find a company-a company willing to invest in each other-to stay for a while.
Commenting on this question is not answered too specifically (it may lead to a vulnerability), and it shows that you are ambitious and think about how to grow in the enterprise. By expressing your desire for horizontal movement and upward improvement, you are a flexible person.
Question 23 how do you make your career choices?
The analysis of the interviewer's question is to understand the motivation of the job seeker and check whether he or she has applied for the job for any historical reasons and career plans, is it true that I only apply for a lot of jobs without any aim.
I always wanted to work in the business world. Since I was a child, I have dreamed that I would at least become vice president of a large enterprise.
In addition to being untrustable, this kind of answer also has a question: it indicates that job seekers are not interested in the positions below vice president.
Correct answer: In the summer before the fourth year of college, I decided to focus on development in a certain field. Although I am a business student, I don't know which industry I will work in. I spent some time thinking about my own goals, figuring out what I was good at and what I wanted to get from my work. Finally, I came to a firm conclusion, that is, this industry is the most suitable for me.
Such a comment indicates that job seekers have carefully made some plans, reduced their concerns, and determined the way forward. This answer also shows that job seekers understand the importance of personal career planning and are capable of making serious personal decisions.
1. What test methods do you use?
2. How to Write Cases
3. How can we fully test each point?
1. What test methods do you use?
There are different testing methods for different products, systems, or modules. In general, there are white box tests and black box tests.
2. How to Write Cases
The compilation of cases is closely related to the definition of the test phase. The cases for system testing and unit testing may be different. In general, the test case depends on the requirements of the system.
3. How can we fully test each point?
The comprehensiveness of the test mainly needs to be considered during the design of the test plan, from the testing strategy, product requirements, and so on, so as to define all the test points.
1. Talk about software testing technology and how to improve it
2. Talk about software testing career development and personal plans
3. Talk about the position of software testing in the enterprise, or the software life cycle.
A clear idea may be more important than a definite answer.
Here we will discuss the questions about the test and interview.
1. What is the actual software testing process in a company? What is your company like?
2. What qualities should software engineers possess?
3. What test tools will you use? How?
4. Can you talk about your 3-5 year career plan)
5. What advantages do you think you have to apply?
I can't say anything about the rest, but there are 4th problems! I hope you can give me some comments.
Level 1: First of all, we need to introduce ourselves. What kind of personality do we have? What have we learned from our current work experience and what is worth talking about. Then I want to say, right, what about software testing? What else do you have to think about software testing. Why do you want to do this? (because my resume has no testing experience ). Oh, you still have the expected salary.
Level 2: What should you do if you think that software testers must possess the basic qualities they need? Then there are some basic concepts, such as what are the software testing procedures? How can I start my work plan first if I take office.
(The first two passes and the last two passes. This is too much)
Level 3: Let me introduce my company's situation and tell me what I want to test and whether I will use the database. Tell me what to do and get familiar with it later.
This is probably so much. I don't know if it is helpful for those who haven't passed this level. It's just for your reference.
I think, as Li Bo said, the key is to make a good impression on each other :)

At last, the interviewer will ask you any questions. As a candidate, you should not ask questions without questions. This will give the interviewer a bad impression that you do not pay much attention to the job. So if you want to get this job, you should seize this final opportunity to show yourself:
You can ask:
1. What are your company's development goals in the near future and in the long term?
2. What are your main competitors?
3. How many developers and testers does your company have?
4. Is your company planning to further expand testers?
5. How can I develop if I am lucky enough to enter your company?
6. the communication skills of testers are very important. Does your company have standard communication channels?
7. Introduce your company's benefits.
8. When can I know the results?