In 2023, the latest summary of the software testing book by major manufacturers, after reading it, you are not afraid that you will not get an offer

1. When do testers need to participate in demand analysis?

If the conditions are sequential, in principle, the earlier you intervene in the requirements analysis, the better, because the deeper the testers understand the requirements, the more beneficial it is for the development of the test work. You can determine the test ideas as early as possible to reduce the interaction with the developers and reduce the deviation in understanding the requirements.

2. The relationship between software testing and debugging

The test conditions are known, the procedures can be defined, and the results can be predicted

The test can be planned and the process can be controlled

Testing is inspection, debugging is reasoning process

Tests show program fails, debug shows correct

Tests don't need to know design details

Testing is done by non-designers

The test has a theoretical basis

Tests can be automated

3. 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 test object is regarded as a black box, and the tester does not consider the logical structure and internal characteristics at all, and only checks whether the function of the program meets its function description according to the requirement specification of the program. White-box testing: Treat the test object as a transparent box, allowing testers to use the internal logical structure and related information of the program to design or select test cases to test all logical paths of the program. Unit testing: A type of white box testing that tests unit modules in software design. Integration test: Based on unit test, test the connection and assembly between unit modules. System Testing: The system is tested with all things considered. Acceptance testing: Testing performed by a third party to confirm that the software satisfies the requirements.

4. What is compatibility testing? What aspects does compatibility testing focus on?

Compatibility testing is mainly to check whether the software can run normally on different hardware platforms and software platforms, which is commonly referred to as software portability.

Compatible types, if subdivided, include platform compatibility, network compatibility, database compatibility, and data format compatibility.

The focus of the compatibility test is the analysis of the compatible environment. Usually, compatibility is only required when the environment in which the software is running is not very certain. According to the needs of software operation, or according to the requirements document, it is generally possible to obtain the environment in which the user will use the software, organize these environments into a form, and then obtain the compatible environment for compatibility testing.

The difference between compatibility and configuration testing is that configuration testing is usually not done under Clean OS, while compatibility testing is mostly done under Clean OS environment.

5. Can all software defects be fixed? Do all software bugs have to be fixed?

Technically, all software defects can be repaired, but it is not necessary to fix all software defects. What testers have to do is to be able to correctly judge when they cannot pursue the perfection of the software. For the entire project team, what has to be done is to make trade-offs for each software defect, and decide which defects need to be repaired according to the risk. The main reasons for this phenomenon are as follows:

- Insufficient time resources. In any project, there are usually not enough developers and testers, and there is not enough regression testing time budgeted in the project. In addition, modifying defects may introduce new defects, so the strong pressure on delivery deadlines In this case, certain deficiencies must be waived.

- Some bugs only appear in special cases. This kind of bug is considered in commercial interests and can be repaired in future upgrades.

-Not a defect of a defect. We often encounter some functional issues that are treated as defects, which can be considered and dealt with later when there is time.

The last thing to say is that software testers, project managers, and programmers should discuss whether to fix the defect or not. People with different roles think from different angles to make the right decision.

6. Briefly describe the life cycle of defects?

Reference answer: Submit -> Confirm -> Assign -> Fix -> Validate -> Close

7. If a defect is submitted, the developer thinks it is not a problem, how to deal with it?

1. First, submit the problem to the defect management library for filing.

2. Then, to obtain the basis and standards for judgment:

(1) According to the requirements specification, product description, design documents, etc., confirm whether the actual results are inconsistent with the plan, and provide a direct basis for confirming whether the defect is confirmed;

(2) If there is no document basis, you can explain whether there is any inconsistency based on the general characteristics of similar software to confirm whether it is a defect;

(3) According to the user's general usage habits, to confirm whether it is a defect;

(4) Discuss with relevant personnel such as designers, developers and customer representatives to confirm whether it is a defect;

3. Make a reasonable discussion, explain the reasons for your judgment to the test manager, pay attention to objectivity, rigor, and do not mix personal emotions.

4. Wait for the test manager to make a final decision. If there are still disputes, you can report to the superior through the channels provided by the company policy, and the superior will make a decision.

8. If a defect is submitted, the developer thinks it is not a problem, how to deal with it?

1. First, submit the problem to the defect management library for filing.

2. Then, to obtain the basis and standards for judgment:

(1) According to the requirements specification, product description, design documents, etc., confirm whether the actual results are inconsistent with the plan, and provide a direct basis for confirming whether the defect is confirmed;

(2) If there is no document basis, you can explain whether there is any inconsistency based on the general characteristics of similar software to confirm whether it is a defect;

(3) According to the user's general usage habits, to confirm whether it is a defect;

(4) Discuss with relevant personnel such as designers, developers and customer representatives to confirm whether it is a defect;

3. Make a reasonable discussion, explain the reasons for your judgment to the test manager, pay attention to objectivity, rigor, and do not mix personal emotions.

4. Wait for the test manager to make a final decision. If there are still disputes, you can report to the superior through the channels provided by the company policy, and the superior will make a decision.

9. What is a relational database, what are the primary key, foreign key, and index?

A relational database is a database composed of multiple two-dimensional row-column tables that can be connected to each other

The primary key is one or more fields in the table whose value is used to uniquely identify a record in the table

A foreign key represents a related link between two relationships. A table with a foreign key of another relationship as its primary key is called a primary table, and a table with a foreign key is called a secondary table of the primary table. foreign key

In a relational database, an index is a separate, physical storage structure that sorts the values ​​of one or more columns in a database table. A list of logical pointers to the data pages in which these values ​​are physically identified.

Friends who still want to work in the software testing industry now, if you want the job you want, you must study harder . I compiled a PDF document for you with more than 800 real software testing interview questions. The high-definition print version is packed and taken away, sweeping the high-frequency questions of software testing interviews, covering testing basics, Linux operating system, MySQL database, Web function testing, interface testing, APPium mobile terminal testing, Python knowledge, Selenium automated testing related, performance testing, performance Tests, computer network knowledge, Jmeter, HR interviews, the hit rate is high. (Everyone brush up...)

1. What are the stages in the software life cycle? What are the common software life cycle models?

2. What is version control, and what are the commonly used version control systems?

3. What are the three major database paradigms?

4. How many tables are related to permissions in mysq|?

5. How many input formats does MySQL binlog have? What are the differences?

6. Storage engine selection?

7. What is an index?

8. What are the advantages and disadvantages of indexes?

insert image description here

insert image description here

insert image description here

1. What command is used to switch directories?

2. How to view process information?

3. How to view the current path?

4. Which command is used to delete files?

5. Statistics on the content of the file? (line number, word count, byte count)

6. What is the use of the grep command?

insert image description here

insert image description here

1. Please write down which label elements will be included under the table label?

2. Many websites do not use the two elements of table iframe, do you know the reason?

3. What is the difference between jpg and png format images?

4. What are the commonly used browsers and what are their kernels?

5. Which attribute defines the request type on the form tag? Which attribute defines the request address?

6. Briefly describe the difference between src and href?

7. What is the difference between before and ::before?

8. How to center a div. up, down, left, and right?

insert image description here

insert image description here

1. What is the focus of automation tool selection?

2. What are the commonly used automated testing tools for mobile applications?

3. What is automated testing?

4. What are the advantages of automated testing?

5. What are the advantages and disadvantages of Jmeter?

insert image description here

insert image description here

insert image description here

1. What is the type of processor in JMeter? 

2. Explain what is a preprocessor element? List some preprocessor elements?

3. Is the execution order of the test elements mentioned?

4. What do "contains" and "match" in regular expressions mean?

5. What should I do if the server CPU indicator is abnormal?

6. Where do your performance testing requirements come from?

7. Do you perform performance testing in the foreground or in the background?

8. What are the performance test indicators?

insert image description here

insert image description here

1. Tell me about your biggest weakness?

2. What is your opinion on overtime?

3. What are your salary requirements?

4. When completing a certain job, you think that the method required by the leader is not the best, and you have a better method. What should you do?

5. If you make mistakes in your work and cause economic losses to the company, what do you think should be done?

insert image description here

insert image description here

at last

The entire document has a total of nearly 200 pages. It is definitely unrealistic to show you all of them. In order not to affect your reading experience, only part of the content is shown. I hope everyone will bear with me. I hope it can help you review before the interview and Find a good job, and save everyone's time searching for information on the Internet to learn!

Guess you like

Origin blog.csdn.net/weixin_50829653/article/details/131405882