[software test] the most complete interview questions and answers. I'm familiar with the full text. If I don't win the offer, I'll lose

Generally, you need to apply for a job about testing , Will the interview questions be difficult ? The following is a compilation of the interview questions and answers for software testing , Welcome to !

1、 What is your testing career development ?

The more experience in testing , The higher the ability to test . So my career development needs time to accumulate , Step by step toward the Senior Test Engineer . And I also have a preliminary career plan , front 3 Years of testing experience , According to the key points of how to do a good test engineer to ask yourself , Constantly update and correct yourself , Do the test well .

2、 What qualities do you think testers need to have

You should have a certain coordination ability to do the test , Because testers often have to contact with developers to deal with some problems , If it's not handled properly, it will cause some conflicts , In this way, it will be difficult to do work . And testers have to be patient , Sometimes it's boring to do tests . Except for patience , Testers can't let go of every possible error .

3、 Why can you do testing

Although my testing technology is not very mature , But I think I can still be competent for the job of software testing , Because doing software testing requires not only good technology , And have some communication skills , Patience, 、 Care and other external factors . All in all, I think I am qualified for this job .

4、 What is the purpose of the test ?

The purpose of testing is to find out the mistakes in the software products , Is the software to meet the user's requirements as much as possible . Of course, software testing is impossible to find out all the mistakes .

5、 What are the stages of testing ?

Generally speaking, it is divided into 5 Stages ： unit testing 、 Integration testing 、 Confirmation test 、 The system test 、 The acceptance test

6、 Test object of unit test 、 Purpose 、 Test basis 、 The test method ?

The test object is a program error inside the module , The purpose is to eliminate errors and defects in the logic and function of local modules . The test is based on the detailed design of the module , The test method is white box test .

7、 What do you think of overtime

If I work overtime, I don't have much opinion , But I still think if we can arrange our time reasonably , There won't be much overtime .

8、 Combine your previous study and work experience , How do you think to do well in testing .

According to my previous work and learning experience , I think to do a good job, we must first have a good communication , Only communication is accessible , There will be good cooperation , Will have better efficiency , Another is that technology must pass the test , Be patient enough to do the test , And a good working habit , Ask if you don't understand , Communicate with colleagues in real time, so as to do a good job of testing .

9、 Why did you choose the software testing industry

Because I know the software testing industry before , I think his development prospect is very good .

10、 Describe software development based on your previous work or learning experience 、 Testing process , Which roles are responsible for , What do you do?

There must be an architect 、 Development Manager 、 Test Manager 、 The programmer 、 Testers . I am mainly responsible for the execution of test cases by the assigned modules .

11、 Based on your experience, tell me about your experience in software testing / Understanding of quality assurance

Software quality assurance and testing is a group of test cases carefully designed according to the specifications in the software development stage and the internal structure of the program ( That is, input data and expected output results ), And run the program according to these test cases , To find the wrong process . It tests all aspects of the application to check its functionality 、 Language effectiveness and its appearance layout .

12、 What is the process of software testing ?

Demand survey ： Overall understanding of the system 、 Application field 、 Software development cycle 、 Software development environment 、 The development organization 、 Time arrangement 、 functional requirement 、 Performance requirements 、 Quality requirements and test requirements, etc . Personnel required to carry out the project according to the System Overview 、 Time and workload estimation and project quotation .

Develop preliminary project plan .

Test preparation ： Organize test team 、 train 、 Establish testing and management environment, etc .

Test design ： Carry out the test design of each test item according to the test requirements , Including the design of test cases and the development of test scripts .

Test implementation ： Carry out the test according to the test plan .

Test evaluation ： According to the results of the test , Issue test evaluation report .

13、 You are right about SQA Responsibilities and work activities ( Such as software metrics ) The understanding of the ?

SQA Is a project team independent of software development , By monitoring the software development process , To ensure that the software development process follows the specified CMM Rules ( If there is a corresponding CMM Rules ), Timely put forward suggestions and improvement plans for nonconformities , Report to the senior manager when necessary to solve the problem . In this way, the introduction of defects can be prevented , So as to reduce the maintenance cost of later Software .SQA The main work activities include developing SQA Work plan , Participate in the review of phase products , Conduct process quality 、 Audit of functional configuration and physical configuration, etc ; Measure the data generated in the process of project development, etc .

14、 Talk about your understanding of software configuration management

During the development of the project, the corresponding configuration management tools shall be used to manage the configuration items ( Including the products of each stage ) Change control , The use of configuration management depends on the size and complexity of the project and the level of risk . The larger the size of the software , Configuration management becomes more and more important . And in configuration management , There is a very important concept , That's the baseline , It is the combination of various configuration items at a certain stage , A baseline provides a formal standard , Subsequent work is based on this standard , And this standard can only be changed after authorization . Configuration management tools mainly include CC,VSS,CVS,SVN etc. , I used it SVN, Not very familiar with other tools .

15、 How to write test plans and test cases

Simple point , The test plan shall include detailed test strategies and methods , Reasonable and detailed resource arrangement, etc , As for test cases , That depends on demand ( Including functional and non functional requirements ) Whether to refine to function points , Whether it can be tested, etc .

16、 Talk about the mainstream software engineering ideas ( Such as CMM、CMMI、RUP,XP,PSP,TSP etc. ) General situation and understanding of them

CMM:SW Capability Maturity Model Software Capability Maturity Model , Its function is to improve the software process 、 Evaluation and software capability evaluation .

CMMI:Capability Maturity Model Integration Capability Maturity Model Integration CMMI Incorporate most of the latest software management practices , At the same time, it makes up for SW-CMM Defects in the model .

RUP:rational unified process It's a software engineering process .

XP:extreme program, Extreme programming means , Software development for small teams , Like the third question above, we can adopt such a development process in combination with the prototype method . Understand that testing is important for xp The importance of development , Stress test ( The focus is on unit testing ) The idea of going first . Programming can significantly improve the quality of code , Continuous integration is good for quickly locating problems .

PSP,TSP They are individual software process and group software process . Everybody knows ,CMM Just tell you what to do, but don't tell you how to do , therefore PSP/TSP Is to tell you that the enterprise is implementing CMM How to do in the process of ,PSP Emphasis on building personal skills ( How to make a plan 、 Control quality and how to cooperate with others ). and TSP Focus on producing and delivering high-quality software products ( How to effectively plan and manage the project development tasks ). All in all , The implementation of CMM, Never really achieve the improvement of capability maturity , Only... Will be implemented CMM And implementation PSP and TSP Combine organically , To be most effective . therefore , The software process framework should be CMM/PSP/TSP Organic integration of information technology .

17、 How do you ensure software quality , In other words, how do you think you can maximize the quality of the software ?

Testing does not guarantee the quality of software to the greatest extent , The high quality of software is developed and designed , Not tested , It not only needs to monitor the software development process , All stages of software development should be carried out according to the specified procedures , Through the review of products in each stage ,QA Process monitoring , Audit the function and configuration to optimize the development . Of course, testing is also an important way to ensure software quality , It is an important part of software quality assurance engineering .

18、 Based on China's current national conditions , Most companies have tight project schedules 、 Fewer people 、 The requirements document is not at all or very nonstandard , How do you think to ensure the quality of software in this case ?( What most companies want to know is how to ensure the quality of software in the face of such difficulties , Because this is generally the case in these companies – I don't want to invest too much and want to ensure quality )

The above occurs , If you just want to improve software quality through testing , That's almost impossible , The reason is that there is not enough time for you to test , Few and non-standard documents lead to the failure to refine the test requirements into sufficient and line specific tests . therefore , As a result of the company's quality assurance, we should work with the project manager to determine the software life cycle model consistent with the project itself ( such as RUP Building materials , Prototype method ), Clarify the development process of the project and urge the project team to carry out work according to this process , All project team members ( The project manager is more important ) Make a reasonable work plan , Strengthen unit testing of code , Within the product delivery date set by the customer , Continuous integration of products, etc , If time permits, we can cooperate with customers to carry out necessary system function tests .

19、 What qualities and skills a test engineer should have ?

1- Master basic testing theory

2- Test in the attitude of finding out the problems in the software , Don't show up as a prick

3- Can read requirement specification and other documents skillfully

4- From the user's point of view

5- Strong quality awareness

6- Careful and responsible

7- Good and effective way of communication ( With developers and customers )

8- With previous testing experience, can timely and accurately judge where the high-risk area is

20、 Some key points of software testing

1- Testers must be trained in basic test knowledge and theory

2- Testers must be familiar with system functions and business

3- Testing should be planned , And the test plan should be well coordinated with the whole project plan

4- You must write test cases , The test execution phase must be carried out according to the test cases

5- Ease of use , function , Branch , The border , Performance and other functional and non functional requirements shall be tested

6- For complex processes, process branching must be carried out , Combinatorial condition analysis , Then divide equivalence classes and prepare relevant test data

7- An important part of test design is to prepare specific test data , Know that the test data is used to test that scenario or branch .

8- Individual tasks should find at least one in every three test cases BUG, Otherwise, it can only indicate that the quality of test cases is poor

9- In addition to the repeated tests built every day, test automation can be considered , Don't think about other automatic words for the time being

21、 The quality training of software testers

1- First , Be interested in software testing and have confidence in yourself , If you have these two points , So no matter what difficulties you encounter in the development process , I believe we can overcome

2- Be good at doubting , In fact, there is no absolutely right , There are always mistakes , Rebellious , What others think impossible , I thought it might happen , Others think it's right , I don't think it's right .

3- Break the spirit of asking in the casserole , For those who have only appeared once BUG Be sure to find out why , Never give up until it is solved .

4- Keep a good mood , Otherwise, you may not be able to do the test well . Don't bring the unpleasant emotions in life to work .

5- Be careful when doing the test , Not all BUG Can easily find out , You must be careful to find these BUG.

6- Be flexible , Be smart , Making more is easy to produce BUG Example .

7- When conditions permit , Communicate more with customers , They have what you need .

8- Put yourself in the customer's shoes , Test the system from their point of view .

9- Don't let programmers , With “ This is unlikely to happen ” This sentence convinces you , contrary , You should convince him , Tell him in customer psychology , It's not like that

10- Think in a comprehensive way , Combined with the needs of customers , Business process and system architecture .

11- Don't complicate asking questions , This contradicts the previous point , If you are a novice , Leave that alone for the time being , Because eventually your team members will discuss and solve .

12- Pursue perfection , For new testers , Strive for perfection , It's good for you , Although some things can't be done , But you should try .

13- A sense of humor , Good communication with the development team is the key , Try to find one for your development team BUG killer , Or say to them “ I can't believe , The program you wrote has not been found yet BUG”.

22、 Why test in a team ?

Because it's hard to know the quality of software that hasn't been tested before it's released , like ISO Quality certification is the same , Testing also requires quality certification , At this time, we need to carry out software testing in the team . Problems found in the software during testing , Let developers know and correct the problem in time , When it's about to be released , Get the quality of the software from the test report .

23、 What types of software testing are you familiar with ?

The test types are ： A functional test 、 Performance testing 、 Interface tests

Functional testing accounts for the largest proportion of testing work , Functional testing is also called black box testing .

Performance testing is to simulate a variety of normal through automated testing tools 、 Peak and abnormal load conditions to test the performance of the system . Load testing and stress testing are both performance testing , The two can be combined .

Interface tests , The interface is the most direct layer for software to interact with users , The quality of the interface determines the user's first impression of the software .

The difference lies in , Functional testing focuses on all functions of the product , Consider every detail function , Every possible functional problem . Performance testing mainly focuses on the stability and robustness of the product under multi-user concurrency . Interface testing focuses on user experience related content , Whether the user has used... When using the product , Is it easy to understand , Standard or not ( The user inadvertently entered invalid data , Of course, considering experiential , Don't pop up the warning too rudely ). When you do a performance test , First of all, it may be a function point , First of all, make sure that there is no problem with her function , Then consider the problem of performance .

24、 What do you think is the key to do a good job in test case design

The key of white box test case design is to cover as many internal program logic structures as possible with fewer use cases . The key of black box test case design is also to cover module output and input interfaces with fewer use cases . It's impossible to do a full test , Find the most problems in a reasonable time with the least use cases . The black box test of software means that the test should be carried out at the interface of the software , This method regards the test object as a black box , Testers don't consider the logical structure and internal characteristics of the program at all , Only according to the requirement specification of the procedure , Check whether the function of the program conforms to its function description . Therefore, black box testing is also called function testing or data-driven testing . The main purpose of black box testing is to find the following types of errors ：、

1- Is there any incorrect or missing function

2- On the interface , Whether the input can be accepted correctly ? Can you output the correct result .

3- Is there any data structure error or external information ( For example, data files ) Access error

4- Whether the performance can meet the requirements

5- Whether there are initialization or termination errors

White box testing of software is a detailed examination of the process details of the software . This approach treats the test object as an open box , It allows testers to take advantage of the logical structure and information inside the program , Design or select test cases , Test all logical paths of the program . By checking program status at different points , Determine whether the actual state is consistent with the expected state . Therefore, white box testing is also called combination testing or logic driven testing . White box test is mainly to check the program module as follows ：

1- Test all independent execution paths of program modules at least once .

2- For all the logical decisions , take “ really ” And take “ false ” Both of them can be tested at least once .

3- Execute the loop body within the bounds of the loop and the bounds of its operation .

4- Test the effectiveness of the internal data structure , wait .

25、 Please describe in detail the meaning of various test types

1- unit testing ( Module test ) It's a small piece of code written by developers , A small tool for verifying the code under test 、 It's very clear whether the function is correct . generally , A unit test is used to determine a specific condition ( Or the scene ) The behavior of a particular function . Unit testing is done by the programmer himself , It's also the programmers themselves who benefit in the end . You can say that , It's the programmer's responsibility to write functional code , At the same time, you have the responsibility to write unit tests for your own code . Perform unit tests , Just to prove that the behavior of this code is consistent with what we expect .

2- Integration testing ( It's also called assembly testing 、 The joint test ) It's a logical extension of unit testing . Its simplest form is ： Two tested units are combined into one component , And test the interface between them . From this level , Component refers to the integration and aggregation of multiple units . In the real plan , Many units are combined into components , And these components make up a larger part of the program . The way to do this is to test the combination of fragments , And eventually extend the process , Test your module with modules from other groups . Last , Test all the modules that make up the process .

3- System testing is to assemble the tested subsystem into a complete system to test . It is an effective method to check whether the system can really provide the functions specified in the system scheme specification .( Common joint debugging test ). The purpose of system testing is to test the final software system comprehensively , Ensure that the final software system meets the product requirements and follows the system design .

4- Acceptance testing is the last test operation before deploying the software . The purpose of acceptance testing is to ensure that the software is ready , And users can perform the established functions and tasks of the software . Acceptance testing is to show future users that the system can work like reservation requirements . After integration testing , All the modules have been assembled into a complete software system according to the design , Interface errors have been basically eliminated , Then we should further verify the effectiveness of the software , This is the task of acceptance testing , That is, the function and performance of the software are as expected by users .

26、 What is the purpose of the test planning effort ? What are the contents of the test planning work ? Which of these are the most important ?

Software test plan is a programmatic document that knows the test process , Includes product overview 、 The test strategy 、 The test method 、 Test area 、 Test configuration 、 Test cycle 、 Test resources 、 Test communication 、 Risk analysis, etc . With software test plan , Project members participating in the test , Especially test managers , Test tasks and methods can be specified , Maintain smooth communication during test implementation , Track and control test progress , Respond to changes during testing .

Test plan and test details 、 There is a strategic and tactical relationship between test cases , The test plan mainly plans the scope of testing activities from the macro level 、 Methods and resource allocation , And testing detailed specifications 、 Test cases are specific tactics for completing the test task . Therefore, the most important ones are test strategies and test methods ( It's best to review first ).

27、 What do you think is the key to good test planning ?

1- Define the goal of the test , Enhance the usability of the test plan

The important purpose of writing software test plan is to enable the test process to find more software defects , So the value of a software test plan depends on how it helps manage the test project , And find out the potential defects of the software . therefore , The test scope in the software test plan must cover the functional requirements highly , The test method must be practical , Test tools and have high practicability , Easy to use , The test results generated are accurate

2- insist “5W” The rules , Clarify the content and process

“5W” Rules refer to “WHAT( What do you do )”、“WHY( Why do )”、“WHEN( When to do )”、“WHERE( Where is the )”、“HOW( How to do )”. utilize “5W" Rules create software test plans , Can help the test team understand the purpose of the test (WHY), Define the scope and content of the test (WHAT), Determine the start and end dates of the test (WHEN), Point out the testing methods and tools (HOW), Give the location of test documents and software (WHERE).

3- Use review and update mechanism , Ensure that the test plan meets the actual needs

After the test plan is completed , If it's not reviewed , Send it directly to the test team , The content of the test plan may be inaccurate or missing , Or the change of software requirements causes the increase or decrease of test scope , The content of the test plan was not updated in time , Mislead test executors .

4- Create test plan and test specification separately 、 The test case

The detailed test specifications should be included in the test specification document created independently , Put the test cases used to guide the execution process of the test team into the independently created test case document or test case management database . Test plan and test details 、 There is a strategic and tactical relationship between test cases , The test plan mainly plans the scope of testing activities from the macro level 、 Methods and resource allocation , And testing detailed specifications 、 Test cases are specific tactics for completing the test task .

28、 When developers say it's not BUG when , How do you deal with ?

Developers say it's not BUG, Yes 2 In this case , First, the demand has not been determined , So I can do this , At this time, you can find the product manager to confirm , Do you need to change .3 Fang discusses and decides whether to change it . Second, it is impossible for this to happen , So there's no need to modify , This is the time , I can say as much as I can first BUG What's the last sentence ? If the user finds out or has a problem , What's going to happen ? Programmers may give you a lot of reasons , You can refute his explanation . If it still doesn't work , Then I can ask this question , Confirm with development manager and Test Manager , If you want to change it, change it , If you don't change it, don't change it . In fact, some of them are not BUG, I just suggest the way to write it into the test document , If developers don't modify it, there's no big problem . If not BUG Words , Be sure to stick to your stand , Let the question be finally confirmed .

29、 What do you think is the advantage of testing ?

The advantage lies in my unswerving confidence and enthusiasm for testing , Although experience is not enough , But the basic skills required for testing I'm confident that I can play them in my work .

30、 What are system bottlenecks ?

Bottleneck mainly refers to the ability of one aspect or several aspects of the software system composed of the whole software and hardware can not meet the specific business requirements of users ,“ given ” It means that the bottleneck will appear under certain conditions , Because after all, most systems are before they are put into operation .

Strictly speaking from a technical point of view , All systems have bottlenecks , Because the resource allocation of most systems is not coordinated , for example CPU The utilization rate just reached 100% when , There are not many systems that just run out of memory . So we discuss the system bottleneck from the perspective of application ： The key is to see whether the system can meet the needs of users . In the case of users limiting their use of the system , The response of the system is still normal , We can think that there is no bottleneck or bottleneck will not affect the work of users .

So we test the system bottleneck mainly to achieve the following two purposes ：

- Find out “ The surface of the ” Bottleneck . It mainly simulates the operation of users , Find out the bottleneck when users limit the use of the system , And then solve the bottleneck , This is the basic goal of performance testing .

- Identify potential bottlenecks and resolve , Ensure the long-term stability of the system . It is mainly to consider when the user expands the system or the business changes in the future , The system can adapt to change . The system that meets the current needs of users is not the best , Our goal of designing the system is to ensure that the whole software life cycle of the system can constantly adapt to the changes of users , Or by simply expanding the system, you can adapt to new changes .

31、 What is the main content of document testing ?

In the domestic software development management , Document management is almost the weakest , Therefore, it is not surprising that document testing is particularly easy to ignore in testing work . To provide users with a complete product , Document testing is essential . Document testing generally focuses on the following aspects ：

Integrity of documents ： It mainly tests the completeness and completeness of the document content , Grasp the quality of the document as a whole . For example, the user manual should include all functional modules of the software .

The description is consistent with the actual situation of the software ： It mainly tests the consistency between the software document and the actual software . For example, after the user manual is basically complete , We should also pay attention to whether the user manual is consistent with the actual function description . Because the document often can't keep up with the update speed of software version .

Intelligibility ： The main thing is to check the documents on the key 、 Is there any graphic explanation for the important operation , written words 、 Whether the chart is easy to understand . For the key 、 It's certainly not enough for important operations to be written only , A diagram should be attached to make the explanation more intuitive and clear .

Examples of operations are provided in the document ： This check is mainly for the user manual . Whether the application examples provided for main functions and key operations are rich , Whether the instance description provided is detailed . It's just a simple illustration , The user manual without instance looks like a simple copy of the software interface , For users , It doesn't really help .

Printing and packaging quality ： It is mainly to check the commercialization degree of software documents . Some user manuals are simply printed 、 It's bound , Too rough , It's not easy for users to save . Excellent documentation such as user manuals and technical white papers , Commercial packaging should be provided , And it's beautifully printed .

32、 How detailed a functional test case needs to be before it is qualified ?

This is also a question that test engineers often ask . Some people advocate that test cases should be written down in detail to what each step performs , The goal is that even a novice who doesn't know the system can follow the test case to perform the work . Those who advocate this kind of writing can also give examples ： Europe and the United States 、 Japan and other software outsourcing documents do this .

Another point of view is to write more roughly , It's like writing a test outline . The person who advocates this view is because software development requirements management is not standardized , Change is very frequent , So we can't write test cases according to the high standards in Europe and America . Such test cases are easy to maintain , It can let the test executor have more room to play .

actually , The detailed level of software test cases should first cover the test point as the basic requirement . for instance ：“ User login system ” The test case can not write specific execution data , But write at least five situations (), If only one sentence is used to cover this function, it is unqualified test case . Covering function points does not mean listing function points , It's about writing down all aspects of the function point ( If there are many combinations, equivalent partition can be used ).

Another factor that affects test cases is the organization's development capabilities and test object characteristics . If the development force is relatively backward , It is unrealistic to write detailed test cases , Because there's not that much investment in resources , Of course, this situation has gradually improved with the development of the team . The key point of test object characteristics is that the test object is in progress 、 The cost of the requirements , If the schedule is tight , There is no time to write high-quality test cases , Sometimes testing is just a kind of auxiliary work , So don't write test cases .

therefore , Test cases should be written according to the characteristics of the test object 、 The team's execution ability and other aspects combine to determine the writing strategy . Finally, the tester must not complain , Strive to continuously improve the level of test case writing at the same time , Constantly improve your ability .

33、 What's the difference between configuration and compatibility testing ?

The purpose of configuration testing is to ensure that the software can run normally on its related hardware , The compatibility test is to test whether the software can cooperate with different software correctly .

The core content of configuration test is to test the running condition of software with various hardware , Generally include ：

(1) How software works on different hosts , for example Dell and Apple;

(2) How software works on different components , For example, the dialing program is developed to test the products produced by different manufacturers Modem On the operation of ;

(3) Different peripherals ;

(4) Different interfaces ;

(5) Different options , For example, different memory sizes ;

The core content of compatibility testing ：

(1) Test whether the software can be compatible on different operating system platforms ;

(2) Test whether the software can be compatible with different versions of the same operating system platform ;

(3) Whether the software itself can be forward or backward compatible ;

(4) Test whether the software is compatible with other related software ;

(5) Data compatibility test , It mainly refers to whether data can be shared ;

Configuration and compatibility testing are very important for developing system software , For example, drivers 、 operating system 、 Database management system, etc . It is still executed according to the test case .

34、 What is the main content of software document testing ?

With the software documentation system becoming increasingly large , Document testing has become an important part of software testing . The main test objects are as follows ：

- Packaging text and graphics ;

- Marketing materials 、 Advertisements and other inserts ;

- to grant authorization 、 Registration Form ;

- End user license agreement ;

- Setup and setup wizard ;

- User's Manual ;

- Online help ;

- Examples 、 Demonstration examples and templates ;

-……

The purpose of document testing is to improve ease of use and reliability , Reduce support costs , Because users can solve problems by themselves through documents . Because the inspection contents of document test are as follows ：

- Target audience —— It is mainly about whether the content of the document can be understood by readers at this level ;

- The term —— It is mainly to check whether the term is suitable for the reader ;

- Content and theme —— Check whether the theme is appropriate 、 Is it missing 、 Whether the format is standard or not ;

- Icons and screen shots —— Check the accuracy and accuracy of the chart ;

- Examples and examples —— Whether it is consistent with the software function ;

- Spelling and grammar ;

- The relevance of documents —— Whether it is consistent with the contents of other relevant documents , For example, whether it is consistent with the advertising information ;

The test document is very important , Not only should we give full attention to , More seriously to complete , Treat document testing like a functional test .

35、 Can black box testing be performed without product specifications and requirements documentation ?

This problem is often encountered by domestic test engineers , The root is that the management of domestic software development documents is not standardized , The management of change is even more unreasonable . When there's actually no documentation , Testers can do black box testing , This kind of testing can be called exploratory testing , The specific way is to test engineers according to their own professional skills 、 Domain knowledge and so on, constantly in-depth understanding of the test object 、 Understanding software functions , And then find the defects .

In this way, the software is basically regarded as a product manual , During the testing process, we should communicate with the developers constantly . Especially when working on projects , There is a lot of pressure on the schedule , It can be used as an urgent test plan . The biggest risk is not knowing if some features are missing .

36、 In the test “ Pesticide Freaks ” What is it? ?

“ Pesticide Freaks ” The word is used by BorisBeizer In his compilation of 《 Software Testing Technology 》 In the second edition . It is used to describe that the more times a tester tests the same test object , There will be fewer and fewer defects . It's like using a pesticide all the time , Pests will have immunity , Pesticides don't work . The root cause of this phenomenon is that testers are too familiar with the testing software , Form a mindset .

In order to overcome this phenomenon , Testers need to constantly write new test programs or test cases , Test different parts of the program , To find more defects . You can also use new people to test software , New comers often find unexpected problems .

37、 In configuration testing , How to judge whether the defects found are ordinary problems or specific configuration problems ?

During configuration testing , Test engineers will still find some common defects , This is a bug that has nothing to do with the configuration environment . So judge the newly discovered problem , The steps to discover software defects need to be re performed in different configurations , If the software defect does not appear , It could be a configuration defect ; If it appears in all configurations , It could be a common defect .

It should be noted that , Configuration problems can occur in a large class of configurations . for example , The dialer may be in all external locations Modem There are problems in both , And the built-in Modem There will be no problem .

38、 Why try not to let time rich employees do some tests ?

On the surface, it shows the efficiency and flexibility of management , But in fact, it also shows that managers despise testing . Testing has a lot to do with the people who are testing . The testing staff should be diligent and patient , Good at learning 、 Think and find problems , Careful and organized , Summary questions , If you have this advantage , It would be great to do other jobs as well , So here's another requirement , Just like testing this job . If he's a professional , So it must be more experienced and confident . It seems that young people in China like to be programmers , The nature of their work is different , Different treatment , Different status , The value of self realization is also different , This is a problem that needs to be improved in the industry . If you do a task just to get it done , Or find a few problems and feel satisfied , It doesn't work in any other job .

39、 Is it possible to fully test the program ?

Software testing beginners may think that after getting the software, they need to do a full test , Find all the software bugs , Make software “ Zero defect ” Release . In fact, complete testing is impossible . There is one main reason ：

- Full testing is time consuming , Time does not allow ;

- Full testing usually means more resources invested , This often doesn't work in reality ;

- Too much input , You can't test one by one ;

- Too much output , It can only be classified for verification ;

- There are too many ways to implement software ;

- There are no objective standards for software product specifications , From a different point of view , There are different standards for software defects ;

Therefore, the degree of testing should be determined according to the actual situation .

40、 Where are the risks of software testing ?

We didn't fully test the software , In fact, the risk is chosen , Because it's very likely that there are parts of the defect that haven't been tested . for instance , Programmers for convenience , When debugging the program, some prompt information box will pop up , And these tips only pop up under certain conditions , It happened that some of the code was not commented out before the program was released . During the test, the test engineer did not test it . If the customer comes across it , It's going to be a costly flaw , Because it was discovered by the customer after delivery .

therefore , We should try our best to choose the most suitable test quantity , Minimize the risk .

41、 The more defects are found , Does it mean that there are more software defects ?

This is a common phenomenon . Test engineers will rack their brains before finding defects , But when you find one , You'll find a lot of defects one after another , A sense of personal accomplishment . The main reasons are as follows ：

- Code reuse 、 Copying code makes it easy for programmers to make the same mistakes . Class inheritance causes all subclasses to contain base class errors , Copying the same code over and over again means that the defect may have been copied as well .

- The more tired programmers can lead to more functional defects in some continuous writing . It is a common phenomenon for programmers to work overtime , So it's easy to write programs with more defects when you're not only physically active . And these continuous latent defects are just the place where the testing engineers show their hands .

“ Defects one by one ” It's not an objective law , It's just a common phenomenon . If the software is well written , This kind of phenomenon is not common . Testers just need to test the program seriously .

42、 Can all software defects be fixed ? All software defects need to be fixed ?

Technically speaking , All software defects can be fixed , But there's no need to fix all the software bugs . What testers need to do is to be able to correctly judge when they can't pursue the perfection of software . For the entire project team , What we have to do is to make a trade-off for each software defect , Determine which defects to fix based on risk . The main reasons for this phenomenon are as follows ：

- There's not enough time . In any project , Usually, developers and testers are not enough , Moreover, there is not enough time budget for regression testing in the project , In addition, modifying defects may introduce new defects , So under the strong pressure of delivery deadline , Some defects must be abandoned .

- Some defects only appear in special cases , This defect is in commercial interest , It can be fixed in future upgrades .

- Defects that are not defects . We often encounter functional problems that are treated as defects , This kind of problem can be considered and dealt with later .

The last thing to say is this , Whether the defect is modified is up to the software tester 、 project manager 、 Programmers discuss together to decide whether to fix , People in different roles think from different angles , To make the right decision .

43、 Software testers are just QA Do you ?

The responsibility of software testers is to find out the software defects as early as possible , Make sure it's fixed . And quality assurance people (QA) The main responsibility is to create or develop standards and methods , Improve the ability to promote software development and reduce software defects . The main job of the tester is to test , The important content of quality assurance personnel's daily work is inspection and review , Testing work is also the work object of test assurance personnel .

Software testing and quality are complementary , All work to improve the quality of software .

44、 How to reduce the loss caused by job hopping ?

stay IT Job hopping is a common phenomenon in the industry , And job hopping will bring certain losses to both the company and the individual . The testing team will undoubtedly face the threat of job hopping , As test Manager Manager , It's only from the day to day work , To minimize the loss . It is suggested that we start from the following two aspects ：

- Strengthen mutual learning among employees in the Department , Learning from each other is the basic requirement of establishing a learning organization , It's the process of knowledge transferring to each other . On this basis , You can deposit your own technology in the form of knowledge , The transformation from tacit knowledge to explicit knowledge is completed .

- Usually , When the enterprise can provide enough development space for employees , If it wasn't for the extremely low treatment , Employees will not take the initiative to leave the enterprise . So we want to keep employees , Managers should connect the personal growth of employees with the development of enterprises , Set up reasonable development plans for employees and put them into practice . But this requirement is compared to , We should rely on a better corporate culture .

45、 What's the difference between a test product and a test project ?

It is customary to commercialize the development after completion 、 Software that can be sold to users without code modification becomes a software product , That is, you can buy “ Selling copies ” Software for , for example Windows2000. Software developed for one or several specific users is usually regarded as a software project , A software project is a personalized product , It can be completely redeveloped according to user requirements , You can also modify existing software products to meet specific user needs . Different characteristics of projects and products , There will still be a lot of differences between deciding that we test products and testing projects ：

- Different quality requirements . Usually the quality of the product is higher , The cost of fixing defects in the released product is high , It will even bring a lot of negative effects . The project is usually aimed at a certain user , Although the higher the quality, the better , But generally, as long as the requirements of users can be satisfied .

- How much testing resources are invested . Software products are usually developed by R & D centers , Schedule pressure should be less . At the same time, due to the high quality requirements , Therefore, more manpower will be invested 、 Material resources .

- At the end of the project, the project should be accepted and tested with the user , This is a feature that product testing doesn't have .

Besides , Test products and test projects in defect management 、 Test strategy development can be very different , The test manager should combine with the specific environment , Get the job done properly .

46、 Testing with users (UAT test ) What's the point of attention ?

Before the software product is put into production , User acceptance testing is usually done . If the user acceptance test fails , The direct result is that it's not “Money”, The indirect effect is to damage the company's image , The impact of the latter is often more serious . According to the author's experience , User acceptance testing must satisfy users .

In fact, user field testing tends to be more of a demonstration . Without cheating users , We show users the benefits of our software , Finally let “ lord ” Satisfied and gladly take out “ silver ” That's our goal . Therefore, user testing should pay attention to the following matters ：

(1) It is impossible to test all the functions in the user field test , So test the core functions . This needs to be prepared in advance , These core functions must be tested in advance , Prove that there is no problem before you can test with the user . The purpose of testing core modules is to build user confidence in the software . Of course, if these modules have more problems , There should be no demonstration .

(2) If some modules do have problems , We can demonstrate other important business function modules , Make a reasonable explanation to the user when necessary . After winning time , Correct the defect in time to make up for .

(3) Never cheat users , slip by . It's simple , Because the software is for users , The problem will come out sooner or later , Unless you can change it right away .

Test with users and pay attention to various communication skills , Not only are short-term interests satisfied , And lay a good foundation for future cooperation .

47、 How to write a test report to the user ?

As testing becomes more and more important , It's inevitable that development teams provide test documentation to customers . A lot of people will ask ：“ Can we provide the test report in work to the customer ?” The answer is No . Because it provides internal test reports , It may make customers lose confidence , Even deny the project .

Test report is generally divided into internal test report and external test report . The internal report is the project document for our testing work , It reflects the implementation of the test work , There is no more discussion here , Readers can refer to relevant textbooks . This paper mainly discusses the writing method of external test report , Generally, the external test report should meet the following requirements ：

- Write according to internal test report , You can usually extract ;

- Serious defects cannot be reported to the customer , Even defects that have been modified , There is no need to let customers know about the defects in development ;

- The report can list some defects , But it has to be an intermediate defect , And these defects have to be fixed ;

- The contents of the report should be as authentic as possible ;

- The whole test report should be carefully reviewed , Try not to bring negative effects to the project , Especially the performance test report .

All in all , External test reports should be carefully written .

48、 What is the status of testing tools in testing work ?

Many test engineers in China are infatuated with testing tools , Especially for beginners , It is even expected that testing tools can replace manual testing . Testing tools play an auxiliary role in the testing work , It is generally used to improve test efficiency . Automated testing makes up for the lack of manual testing , Reduce a certain amount of work . In fact, testing tools cannot replace most manual testing , Some automated tests such as performance testing can't be done by hand .

For automated testing technology , It should be treated according to different situations of software , General automation techniques will be used where a lot of repetitive work is caused 、 The pressure point of the system 、 And any place where it's appropriate to use programs to solve mass input data . Then look for the right automated testing tool , Or develop your own test program . Never use... For the sake of using a test tool .

49、 What are the common test case design methods ? Please use specific examples to illustrate the application of these methods in test case design .

1- Equivalence class division

The common software test interview questions are divided into equivalence classes : An equivalence class is a subset of an input field . In this subset , Each input data is equivalent to exposing errors in the program . And reasonably assume that : Testing representative values of an equivalent class is equivalent to testing other values of this class . therefore , All input data can be reasonably divided into several equivalent classes , Take one data in each equivalence class as the input condition of the test , You can use a small amount of representative test data . Good test results are obtained . There are two different cases of equivalence division : Effective equivalence class and invalid equivalence class .

2- Boundary value analysis

The boundary value analysis method is a supplement to the partition method of equivalence classes . Testing experience tells me , A lot of errors occur at the boundary of the input or output range , Not inside the I / O range . Therefore, test cases are designed for various boundary conditions , We can find out more mistakes .

Use boundary value analysis to design test cases , First of all, boundary conditions should be determined . Generally, the boundary of input and output equivalence classes , It's the boundary situation that should be tested . It should be chosen exactly equal to , Just greater than or just less than the boundary value as test data , Instead of selecting typical values or arbitrary values in equivalent classes as test data .

3- Wrong guess

Based on experience and intuition, we can infer all kinds of possible errors in the program , So as to design test cases with pertinence .

The basic idea of the wrong way of guessing : List all the possible errors in the program and the special cases that are prone to errors , Choose test cases based on them - for example , Many of the common errors in modules that have been listed during unit testing - Mistakes found in previous product tests, etc , These are the summaries of experience . also , The input data and output data are 0 The situation of . Input form is blank or input form has only one line - These are all error prone situations . The examples in these cases can be selected as test cases .

4- Cause and effect diagram method

The equivalence class partition method and boundary value analysis method introduced above , They all focus on the input conditions , But the connection between input conditions is not considered , Combination, etc - Consider the combination of input conditions , There may be something new - But it's not easy to check the combination of input conditions , Even if all input conditions are divided into equivalent classes , There are quite a lot of combinations between them - Therefore, it is necessary to consider a combination suitable for describing multiple conditions , The corresponding form of multiple actions to consider the design of test cases - This requires the use of cause and effect diagrams ( logical model )- The final result of causality diagram is the judgment table - It is suitable for checking various combinations of program input conditions .

5- Orthogonal table analysis

occasionally , There may be a surge in the number of test cases due to the combination of a large number of parameters , meanwhile , There is no obvious priority gap between these test cases , And testers can't do so many tests , We can use orthogonal table to reduce some use cases , So as to achieve the possibility that as few use cases as possible cover as wide a range as possible .

6- Scene analysis method

It refers to the operation steps of simulating users according to user scenarios , This comparison is similar to the cause and effect diagram , But the depth and feasibility of execution may be better .

50、 What do you think is the key to test case design ?

The key of white box test case design is to cover as many internal program logic results as possible with fewer use cases

The key of black box use case design is to cover module output and input interfaces with fewer use cases . It's impossible to do a full test , Find the most problems in a reasonable time with the least use cases

51、 Describe the complete process of a test activity in detail .

1- Project manager through communication with customers , Complete the requirements document , The review of requirements documents is completed by developers and testers , The contents of the review include ： The requirements are not clearly described and there may be obvious conflicts or functions that cannot be realized . Project managers through integrated developers , Comments from testers and customers , Complete the project plan . then sqa Entry project , Start counting and tracking

2- The developer completes the requirement analysis document according to the requirement document , The tester reviews , The main contents of the review include whether there are omissions or differences between the two sides . The tester completes the test plan document , The test plan includes the content described above .

3- The tester starts to write test cases according to the modified requirements analysis document , At the same time, the developer completes the outline design document , Detailed design documents . These two documents serve as supplementary materials for testers to write test cases .

4- After the test case is completed , Testing and development needs to be reviewed .

5- The tester builds the environment

6- The developer submits the first version , There may be unfinished functions , To be sure . The tester tests , Find out bug Submit to bugzilla.

7- Development commit second version , Include bug fix And added some functions , The tester tests .

8- Repeat the above work , It's usually 3-4 After a version bug Decrease in the number , Meet the requirements of shipment .

9- If there is a customer feedback question , Testers are required to assist in reproducing and regression testing .

52、 Have you ever been engaged in performance testing before ? Please describe the whole process of your previous performance testing in detail as much as possible .

Have done a set of network management system performance test , The main test of this software is to manage a large number of terminals at the same time , In response time ,cpu/ disk / Whether the parameters such as memory meet the requirements .

I have also done the call performance test of softswitch system , It mainly tests the Softswitch System in the case of a large number of calls , response time , Call success rate ,cpu/ disk / Whether the memory and other parameters meet the design requirements .

53、 In your previous work , A software bug ( Or call it bug) What does the record contain ? How to submit high quality software defects (bug) Record ?

1- In traditional bugzilla in ,bug The description should include the following information

2- and bug Generate the corresponding software version

3- Development of the interface personnel

4-bug The priority of the

5-bug Severity of

6-bug Modules that may belong to , If you can't confirm , It can be judged by developers

7-bug title , The phenomenon needs to be clearly described

8-bug describe , Need to give as much as possible to re bug Steps for

9-bug The attachment can give the relevant log and screenshot .

High quality bug A record is something that is easy to understand bug Record , therefore , High requirements for description , It can provide more and more accurate information , Very good to help developers locate .

54、 When you work on performance testing , Have you ever used any testing tools ? If there is , Please describe how the tool works , A practical example is given to illustrate how the tool is applied in practical work .

Test the network management system , The use of mimic To simulate the terminal , Can save a lot of cost .

When testing the Softswitch System , The use of prolab To simulate the terminal and send the call Softswitch , He's done the off hook dialing job that hundreds of people can do at the same time , The main working principle is to produce something that meets the requirements ip Packet and send it to softswitch system , At the same time, the response of softswitch system is processed , Decide what to do next .

55、 What do you think the purpose of performance testing is ? What is the key to doing a good job in performance testing ?

It is mainly to ensure that in the case of a large number of users , The service can be used normally .

Finally, thank everyone who reads my article carefully , The following online link is also a very comprehensive one that I spent a few days sorting out , I hope it can also help you in need ！

These materials , For those who want to change careers 【 software test 】 For our friends, it should be the most comprehensive and complete war preparation warehouse , This warehouse also accompanied me through the most difficult journey , I hope it can help you ！ Everything should be done as soon as possible , Especially in the technology industry , We must improve our technical skills . I hope that's helpful ……

If you don't want to grow up alone , Unable to find the information of the system , The problem is not helped , If you insist on giving up after a few days , You can click the small card below to join our group , We can discuss and exchange , There will be various software testing materials and technical exchanges .

Click the small card at the end of the document to receive it

Typing is not easy , If this article is helpful to you , Click a like, collect a hide and pay attention , Give the author an encouragement . It's also convenient for you to find it quickly next time .

Self study recommendation B Stop video ：

Zero basis transition software testing ： Self taught software testing , Got the byte test post offer, Is the B The best video station ！

Advanced automation testing ： Huawei has landed , Salary increase 20K,2022 Most suitable for self-study python Automated test tutorial , Spend it yourself 16800 Bought , Free sharing