Software testing interview questions--for personal use

1. Eight principles of software testing

1. All testing standards are based on user needs
2. Always maintain the awareness of "quality first". When time and quality conflict, time must obey quality.
3. The requirements stage should clearly define the quality standards of the product
4. Software testing begins as soon as the software project is started, rather than waiting for the program to be written before testing begins.
5. Testing by a third party will be more objective and effective
6. Software testing plan is the prerequisite for good software testing work
7. Test cases are designed, not written
8. Program sections with more errors should be tested more deeply

2. You found a bug during testing, but the development manager thinks it is not a bug. How should you solve it?

1. Submit the problem to the defect management database for filing.
2. To obtain the basis and standards for judgment:
Based on the requirements specification, product description, design documents, etc., confirm whether the actual results are inconsistent with the plan, Provide a direct basis for whether the defect is confirmed; if there is no documented basis, you can confirm whether it is a defect by explaining whether there are inconsistencies based on the general characteristics of similar software; confirm whether it is a defect based on the user's general usage habits; 4. Make a reasonable argument and explain your judgment to the test manager Reasons should be objective and rigorous, and should not be mixed with personal emotions. Wait for the test manager to make a final decision. If there are still disputes, you can report it to your superiors through the channels provided by company policy, and your superiors will make a decision.
3. Discuss with designers, developers, customer representatives and other relevant personnel to confirm whether it is a defect;

3. Given a website, how do you test it?

1. Search for requirements description, website design m and other related documents, and analyze the testing requirements.
2. Develop a test plan, determine the test scope and test strategy, which generally includes the following parts:
Functional testing; Interface testing; Performance testing; Database testing ; Security testing; Compatibility testing
3. Design test cases:
Functional testing can include, but is not limited to, the following aspects:
**Link test. **Whether the link jumps correctly, whether there are empty pages and invalid pages, whether there are incorrect error messages returned, etc. Submit a test of the feature.
Multimedia elements can be loaded and displayed correctly. Whether multi-language support can correctly display the selected language, etc.
Interface testing can include but is not limited to the following aspects:

• Is the page style consistent and beautiful?
• Whether the page layout is reasonable, and whether the key content and hot content are prominent
• Whether the control is used normally
• For spaces that are required but for installation, is there an automatic download and installation function?
• text check

Performance testing is generally considered from the following three aspects:
Stress testing; Load testing; a> Security test: Database testing should be specifically determined whether it needs to be carried out. Databases generally need to consider aspects such as connectivity, data access operations, and verification of data content. Strength Test

• Basic login functionality check
• Is there an overflow error, causing system crash or permission leakage?
• Check common security issues related to development languages, such as SQL injection, etc.
• If you need advanced security testing, be sure to obtain help from a professional security company, outsource testing, or obtain support for compatibility testing. Determine the supported platform combinations based on the content of the requirements description:

Compatibility includes: browser compatibility; operating system compatibility; software platform compatibility; database compatibility

4. Carry out testing and record defects. Reasonably arrange and adjust the test progress, obtain the resources required for testing in advance, and establish a management system (for example, demand changes, risks, configurations, test documents, defect reports, human resources, etc.). Regularly review, evaluate and summarize the test, and adjust the content of the test.

Enter Chinese characters in the search engine and the corresponding domain name can be parsed. Please tell me how to use r LoadRunner to test.
Establish a test plan, determine test standards and test scope

Design test cases for typical scenarios, covering common business processes and uncommon business processes, etc.

Develop automatic test scripts and scenarios based on test cases:

Record test script
Create a new script (Web/HTML protocol)
Click the record button and enter "about" in the URL of the pop-up dialog box :blank".
After performing the normal operation process in the opened browser, end the recording.
Debug the script and save it. Character set dependencies may be noted.
Set test scenarios
Set test scenarios for performance, mainly to determine whether the average transaction response time of the system meets the standard under normal circumstances
Set up test scenarios for pressure loads, mainly to determine whether the system will collapse if it is at full load for a long time or exceeds the system's carrying capacity
.

Execute tests, obtain test results, and analyze test results

4. What is the difference between one client with 300 clients and 300 clients with 300 clients putting pressure on the server?

300 users on one client will occupy more resources of the client and affect the test results.
Interference between threads may occur, resulting in some exceptions.
300 users on one client require more bandwidth.
For IP address issues, you may need to use IP Spoof to bypass the server's limit on the maximum number of connections for a single IP address.
If all users are on one client, there is no need to consider distributed management issues; while users are distributed on different clients, you need to consider using a controller to overall deploy users on different clients. At the same time, corresponding permission configuration and firewall settings need to be given.

5. Describe the concepts and characteristics of software? What does software reuse mean? What are the components included?

Software is another part of the computer system that is interdependent with the hardware. It is a complete collection of programs and documents.
Software Reuse is the use of various relevant knowledge of existing software to create new software to reduce the cost of software development and maintenance. Software reuse is an important technology to improve software productivity and quality. Early software reuse was mainly code-level reuse, and the reused knowledge specifically referred to programs. Later, it was expanded to include domain knowledge, development experience, design decisions, architecture, requirements, design, code, documentation, and all other relevant aspects.

Software components that can be reused are generally called reusable components

6, Q: What is the software life cycle and its model?

The software life cycle is the structural framework of all software development processes, activities and tasks. It is the process from feasibility study to requirements analysis, software design, coding, testing, software release and maintenance.
After going through requirements, analysis, design, implementation, and deployment, the software will be used and enter the maintenance stage, until it gradually dies due to lack of maintenance costs. Such a process is called "Life Cycle Model".

7.What is software testing? The purpose and principles of software testing

The process of operating or testing a system using manual or automated means. Its purpose is to test whether it meets specified requirements or to clarify the difference between expected results and actual results. The purpose of software testing: Testing is the execution process of the program, the purpose is to find errors A successful test case is to find So far undiscovered bugs A successful test is one that finds hitherto undiscovered bugs Ensure that the product does what it promised or announced, and There are clearly written instructions for the functions that users can access. Ensure that the product meets performance and efficiency requirements Ensure that the product is robust and adaptable to the user environment Principles of software testing: What the textbook says: Software testing should be performed as early as possible and throughout the entire software life cycle Software testing should trace requirements< /span> Focus on bug fixes Repeated use of the same test will Make software resistant Testing should start from "small scale" and gradually move to "large scale" Check whether the program does what it should not do Pay attention to legal and reasonable inputs, but also pay attention to illegal and unexpected inputs Strictly implement the test plan and eliminate the arbitrariness of the test Defect 28 Theorem Pay full attention to the clustering phenomenon in the test Each test result must be thoroughly checked Expectations must be determined Output (or results) Exhaustive testing is impossible, the Good-enough principle must be followed Testing should be constructed by a third party

8.What is the role of software configuration management? What does the software configuration include?

As a necessary link in the software development process and the basis of software development management, software configuration management runs through the entire software life cycle. It also plays an important supporting role in the macro management of the software development process, that is, project management. A truly effective implementation of software configuration management by a software development organization will make the software development process more predictable, make the system repeatable, and greatly improve the competitiveness of the software organization.
Software configuration includes the following:
Configuration item identification
Workspace management
Version control
Change Control
Status Reporting
Configuration Audit

9.What is software quality?

Software quality: The ability of software product features to meet users’ functional and performance requirements.

10.What are the current main test case design methods?

White box testing:
Logic coverage
Loop coverage
Basic path coverage

Black box testing:
Boundary value analysis method
Equivalence class division
Error guessing method Random Test Scenario Method Test Outline Method State Chart Method
Cause and Effect Diagram Method

11.In what aspects should the security of software be tested?

Software security testing includes program and database security testing. Testing strategies vary based on system security indicators.
Issues to consider when testing user authentication security:
Clearly distinguish different user permissions in the system
Will there be any users in the system? Conflict
Will the system be confused due to changes in user permissions?
Is the user login password visible and copyable?
Yes You can log in to the system through absolute means (copy the link after the user logs in to enter the system directly)
Whether the user deletes all authentication marks after exiting the system, and whether the user can use the back key to enter the system without entering a password
Issues to consider when testing system network security
Test whether the protective measures taken are correctly installed and whether relevant system patches are applied
Simulate unauthorized attacks to see if the protection system is strong
Use mature network vulnerability checking tools to check system-related vulnerabilities (that is, use the most professional hacker attack tools to try to attack,
The most commonly used ones now are NBSI series and IPhacker IP)
Use various Trojan checking tools to check the Trojan situation of the system
Use various anti-plug-in tools to check the system Plug-in vulnerabilities of each group of programs
Database security considerations:

Whether the system data is confidential (for example, this is particularly important for banking systems, but general websites do not have high requirements)

Integrity of system data (there was incomplete data in the enterprise real-name verification service system that I just completed, which hindered the realization of the functions of this system
)< /span> System data independence
System data manageability

System data backup and recovery capabilities (whether the data backup is complete, whether it can be restored, and whether the restore can be complete)

12.What is a test case? What is a test script? What is the relationship between the two?

A specific set of input data, operations, or various environmental settings and expected results provided to the system under test for the purpose of conducting testing.
Test scripts are scripts written for automated testing.
The writing of test scripts must correspond to the corresponding test cases.
Briefly describe what static testing, dynamic testing, black box testing, white box testing, α testing β Testing
Static testing is the process of looking for possible errors in the program code or evaluating the program code without running the program itself.
Dynamic testing is to actually run the program under test, input the corresponding test instance, check the difference between the running results and the expected results, and determine
whether the execution results meet the requirements. To test the correctness, reliability and effectiveness of the program, and analyze the system's operating efficiency
and robustness.
Black box testing is generally used to confirm the correctness and operability of software functions. The purpose is to detect whether each function of the software can be
implemented and to The tested program is treated as a black box, without considering its internal structure. After knowing the relationship between the input and output of the program or the function of the program, the software specifications are relied on to determine the test Correctnessof use case and inferred test results. White box testing is based on the analysis of the internal logical structure of the software. It is a code-based test. Testers read the program code or use development tools. Single-step debugging is used to judge the quality of the software. Generally, black box testing is implemented by the project manager during programmer development. Alpha testing is a test conducted by a user in a development environment, or it can be a controlled test conducted by users within the company in a simulated actual operating environment Testing, Alpha testing cannot be done by programmers or testers. Beta testing is a test conducted by multiple users of the software in the actual use environment of one or more users. Developers are usually not present at the testing site, and beta testing cannot be done by programmers or testers. What is the software quality assurance system? What are the national standards related to quality assurance management? ? What are their numbers and their full names? ?< /span> Try. (it) should include requirements document review, code control, code review, change management, configuration management, version management and software testing SQA consists of a set of software engineering processes and methods to ensure quality (of software). SQA runs through the entire software development process,

13.What are the quality characteristics of software products? ?

Functionality: adaptability, accuracy, interoperability, compliance, security.

Reliability: maturity, fault tolerance, and recovery.
Usability: easy to understand, easy to learn, and easy to operate.
Efficiency: time characteristics, resource characteristics.
Maintainability: easy analysis, easy change, stability, and easy testing.
Portability: Adaptability, easy installation, compliance, and easy replacement.

14.What is the strategy for software testing? ?

Software testing strategy: Under the guidance of certain software testing standards and testing specifications, and based on the specific environmental constraints of the test project
, the principles, methods, and methods of software testing are specified gather.

15.Software testing is divided into several stages. What are the testing strategies and requirements for each stage? ?

Software testing can be divided into several stages: unit testing, integration testing, system testing and <acceptance testing> (not necessarily)
stages< a i=2> Unit test testing strategy: Top-down unit testing strategy Summary: The cost is much higher than isolated unit testing, not unit testing A good choice. Bottom-up unit testing strategy Summary: A more reasonable unit testing strategy, but the test cycle is longer. Isolated unit testing strategy Summary: The best unit testing strategies. Testing strategy for integration testing: Big Bang Integration Suitable for a maintenance project or the system being tested is small a> Testing strategy for system testing Disadvantages: The workload of stubs and drivers is large; some interface tests are insufficient; some tests are repeated and wasteful. Advantages: It has a high degree of parallelism; it can effectively shorten the development schedule of the project. Progress-based integration Adapt to the fact that the underlying interface is relatively stable; the high-level interface changes frequently; the underlying components are completed earlier. Bottom-up integration behavior. Modification; The production port control component has a large technical risk and needs to be verified as soon as possible; I hope to see the system function of the product as soon as possible It is suitable for product control structures that are relatively clear and stable; high-level interfaces change little; low-level interfaces are undefined or may often be modified Top-down integration

Data and database integrity testing; functional testing; user interface testing; performance benchmarks; load testing; strength testing; capacity testing;
; security and access control testing; failover and recovery testing; configuration testing; installation testing; encryption testing;
Usability testing; version verification testing; documentation testing
What work is usually done at each stage of software testing? What are the result files for each stage? What is included?
Unit testing phase. Each independent unit module is tested in isolation from other parts of the system. The unit test needle
performs a correctness check on each program module to check whether each program module is implemented correctly. specified functions. Generate
unit test reports and submit defect reports.
Integration testing phase. Integration testing is based on unit testing and tests whether the work of each part is achieved during the process of assembling all software units into modules, subsystems or systems in accordance with the requirements of the outline design specifications. Or achieve corresponding technical indicators and activities required. At this stage, an integration test report is generated and a defect report is submitted. System testing phase. The software that has passed the validation test will be used as an element of the entire computer system, combined with other system elements such as computer hardware, peripherals, certain supporting software, data and personnel, and Under the actual operating environment, comprehensive functional coverage of the computer system. This stage requires submission of test summaries and defect reports.

16.What are the tasks of testers in the software development process?

1. Look for bugs;
2. Avoid defects in the software development process;
3. Measure the quality of software; < a i=3> 4. Pay attention to user needs. The overall goal is: to ensure the quality of the software. In your previous work, what content did a software defect (or bug) record contain? How to submit high-quality software defect (Bug) records?

A bug record should basically include: number, module to which the bug belongs, bug description, bug level, discovery date, discoverer, modification date, modifier, modification method, regression results, etc.;

To effectively discover bugs, you need to design efficient test cases by referring to preliminary documents such as requirements and detailed design, then strictly implement the test cases, and fully confirm the problems found.

Confirm, and then publish it to the outside world. This can improve the quality of submitted bugs.
Black box testing and white box testing are two basic methods of software testing. Please explain their respective advantages and disadvantages!
The advantages of black box testing are:
It is relatively simple and does not require understanding of the code and implementation inside the program;
It is related to the software Internal implementation has nothing to do;
From the user's perspective, it is easy to know which functions users will use and what problems they will encounter;
Based on software development documents, Therefore, you can also know which functions in the document are implemented by the software;
It is more convenient when doing automated software testing.
The disadvantages of black box testing are:
It is impossible to cover all the code, and the coverage rate is low, probably only 30% of the total code; a>
Automated testing has low reusability.

The advantages of white box testing are:
Help software testers increase code coverage, improve code quality, and discover hidden problems in the code.
The disadvantages of white box testing are:
There are many different paths for program operation, and it is impossible to test all running paths;
Testing is based on code. It can only test whether the developer has done it correctly, but cannot know whether the design is correct or not. It may miss some functional requirements; When the system is large, the testing overhead will be very large.

17.How to test a paper cup?

Functionality: Check whether there are leaks when filling water in the cup; whether the water can be drunk
Safety: whether the cup has poison or bacteria
Reliability: The degree of damage to the cup when dropped from different heights
Portability: Whether the cup can be used normally in different places, temperatures, etc.
Compatibility : Whether the cup can hold juice, plain water, alcohol, gasoline, etc.
Ease of use: whether the cup is hot to the touch, has anti-slip measures, and is convenient for drinking
User documentation: Does the user manual have a detailed description of the usage, restrictions, conditions of use, etc. of the cup?
Fatigue test: Fill the cup with water (case 1) and leave it for 24 hours to check the leakage time and situation; fill it with gasoline (case 1) Case 2)
Leave it for 24 hours to check the leakage time and situation, etc.
Pressure test: Use a needle and keep adding weight to the needle to see how much pressure it will wear. Transparent

18.What is the purpose of test planning? What should the content of a test plan document include? Which of these are the most important?

Answer: The software test 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, etc. With the help of the software test plan, project members involved in testing, especially test managers, can clarify test tasks and test methods, maintain smooth communication during the test implementation process, track and control test progress, and respond to < /span> So the most important thing is to test the test strategy and test method (preferably can be reviewed first). Resource allocation, while test detailed specifications and test cases are specific tactics for completing testing tasks. There is a strategic and tactical relationship between the test plan, detailed test specifications, and test cases. The test plan mainly plans the scope, methods and testing activities from a macro perspective. Various changes during testing.

19.What are the common test case design methods for black box testing? Please use specific examples to illustrate the application of these methods in test case design work.

Equivalence class division
Equivalence class division: Equivalence class refers to a sub-set of a certain input domain. In this sub-set, each input data is important for revealing the program. Errors are all equivalent. It is reasonable to assume that testing a representative value of an equivalence class is equivalent to testing other values ​​of this class.

Therefore, all input data can be reasonably divided into several equivalence classes, and one data in each equivalence class is taken as the input condition of the test, so that a small amount of representative test data can be used to obtain better results. Test results. Equivalence class division can have two different situations: valid equivalence class and invalid equivalence class.
2) Boundary value analysis method
Boundary The value analysis method is a supplement to the equivalence class division method. Testing work experience tells me that a large number of errors occur at the boundaries of the input or output range, rather than within the input and output range. Therefore, designing test cases for various boundary conditions can detect more errors. The basic idea of ​​the error speculation method: list all possible errors and errors in the program Special situations where errors occur, and test cases are selected based on them. For example, many common errors in modules have been listed during unit testing. Errors that have been discovered in previous product testing, etc., these are the summary of experience. Also, input The data and output data are 0. The input form is blank or the input form has only one row. These are error-prone situations. Examples of these situations can be selected as test cases. Based on experience and Intuitively speculate on all possible errors in the program, thereby designing test cases in a targeted manner. 3) Error guessing method
Using the boundary value analysis method to design test cases, you should first determine the boundary conditions. Usually the boundaries of the input and output equivalence classes are the boundary conditions that should be focused on testing. You should choose exactly equal to, just greater than, or just less than Boundary values ​​are used as test data instead of selecting typical values ​​or arbitrary values ​​in the equivalence class as test data.

4) Cause-and-effect diagram method
The equivalence class division method and boundary value analysis method introduced earlier focus on considering the input conditions, but do not consider the connection between the input conditions. Mutual combinations, etc. Considering the mutual combination of input conditions, some new situations may arise. But it is not easy to check the combination of input conditions. Even if all input conditions are divided into equivalence classes, the differences between them There are quite a lot of combinations. Therefore, it is necessary to consider designing test cases in a form that is suitable for describing the combination of multiple conditions and correspondingly generating multiple actions. This requires the use of cause-and-effect diagrams (logical models). The cause-and-effect diagram method ultimately What is generated is a decision table. It is suitable for checking various combinations of program input conditions.
5) Orthogonal table analysis method
Sometimes, it may be due to a large number of The combination of parameters causes a surge in the number of test cases. At the same time, there is no obvious gap in priority between these test cases, and testers cannot complete such a large number of tests, so they can be reduced through orthogonal tables. Use cases to achieve the possibility of covering as large a range as possible with as few use cases as possible.
6) Scenario analysis method
refers to simulating the user's operation steps based on user scenarios. This is similar to a cause-and-effect diagram, but may have better depth and feasibility of execution. .
7) State chart method
Obtain all states of the system under test through input conditions and system requirement descriptions, and obtain output conditions through input conditions and states; through input Conditions, output conditions, and states lead to test cases for the system under test.
8) Outline method
The outline method is a method that focuses on requirements. In order to list various test conditions, the requirements are converted into an outline form. The outline is represented as a tree structure with a unique path between the root and each leaf node. Each path in the outline defines a specific set of input conditions that are used to define a test case. The number of leaves in the tree or paths in the outline gives an approximate number of test cases required to test all functionality.

20. Describe the complete process of a testing activity in detail.

Answer: (For reference, this answer is mainly based on the waterfall model)
The project manager completes the requirements document through communication with the customer, and the developers and testers jointly complete the requirements Document review includes: areas where the requirements are unclear and areas where there may be obvious conflicts or unachievable functions.
The project manager completes the project plan by integrating the opinions of developers, testers and customers. Then SQA enters the project and starts statistics and tracking
The developers complete the requirements analysis document based on the requirements document, and the testers conduct a review. The main content of the review includes whether there are any omissions or differences in understanding between the two parties. The tester completes the test plan document, and the content included in the test plan is described above.
Testers start writing test cases based on the modified requirements analysis document, while developers complete the outline design document and detailed design document. These two documents become supplementary materials for testers to write test cases.
After the test cases are completed, testing and development need to be reviewed.
Testers build environment
When developers submit the first version, there may be unfinished functions that need to be explained. Testers conduct testing and submit bugs to BugZilla after discovering them.
Develop and submit a second version, including bug fixes and added features, for testers to test. Repeat the above work, usually after 3-4 versions, the number of BUGs will be reduced and the requirements for shipment will be met. If there are problems reported by customers, testers are required to assist in reproducing and retesting.

21.In your previous work, what did a software defect (or bug) record contain? How to submit high-quality software defect (bug) records?

In traditional BugZilla, the BUG description should include the following information
and the software version and module corresponding to the BUG generation
Developed interface personnel< /span>. is large and accurate, which is good. It helps developers locate, so when submitting high-quality software defect records, you need to pay attention to the high quality and accurate description of BUG records High-quality BUG records refer to BUG records that are easy to understand. Therefore, the requirements for description are high and the information that can be provided BUG attachment can Provide relevant logs and screenshots. BUG description, need to try to give the steps to fix the bug BUG title, need to clearly describe the phenomenon Module to which the BUG may belong. If it cannot be confirmed, developers can judge it Severity of BUG
Priority of BUG

G BUG management tool tracking process
Using BugZilla as an example
The tester discovered the BUG and submitted it to Bugzilla, the status is new, BUG The recipient is the development interface personnel
The development interface assigns the BUG to the developer of the relevant module, changes the status to assigned, and the developer and tester confirm the BUG , if it is my own BUG, ​​set it to receive; if it is another developer's problem, it will be forwarded and the next developer will do this; if it is not a problem, then After everyone needs to discuss and confirm, reject this BUG, and then the tester will close this issue. If the developer accepts the BUG and fixes it, the developer will change the BUG status to fixed and inform in which version the test can be tested. Testers test in the new version. If they find that the problem still exists, verification will be refused; if it has been fixed, the BUG will be closed.

Answer: 1) After a tester or developer discovers a bug, they determine which module the problem belongs to. After filling in the bug report, the system will automatically notify the project team leader via email or directly notify the developer.
\2) After verification, the modification status is VERIFIED. After the entire product is released, it will be modified to CLOSED.
\3) There are still problems, REOPENED. The status changes to "New" again, and an email notification is sent.
\4) The project leader will reassign it to the developer to whom the bug belongs based on the specific situation.
\5) If so, process it, resolve it and give a solution. (You can create patch attachments and supplementary instructions)
\6) After the developer receives the email message, he will determine whether it is his own modification. Scope.
\7) If not, reassign it to the project leader or the developer that should be assigned.
\8) The tester queries the developer and it has been modified bug, retest.

22. **Do you think how to improve the efficiency and effectiveness of communication during the communication process between testers and developers? **What is the key to maintaining good interpersonal relationships between testers and other members of the development team?

Try to communicate face-to-face, and secondly, communicate directly by phone. If you can only communicate through email and other non-timely communication tools
, emphasize that you must have a deep understanding of the characteristics and be able to express them. clear.
It is also a more effective method to use some test management tools such as TestDirector for management. At the same time, attention should be paid to accurate descriptions of BUGs in
TestDirector.

Pay attention to the following points when establishing good communication between testers and developers in the team:
1Sincerity
The second oneis team spirit
The third one is having a common language inthe profession
Four It's about treating the issue rather than the person, and putting work first
Of course, you can also increase the other party's favor by pointing out some minor problems directly instead of entering the BUG Tracking System.

23.What is your greatest interest in testing? Why?

There is no fixed and unified answer to this interview question, but it may be asked by many companies. Provide the following answers for examination:
My greatest interest, I feel that this is a challenging job;
Testing is an experience industry, and the longer you work, the more you can feel it The difficulty and fun of testing well
Through your own work, you can make the software products more and more perfect, and experience the fun from it
When answering such questions, pay attention to the following points Aspects:
Express your interest as closely as possible to the technical route of the recruiting company. For example, if the company is a database application company, then
express your interest. Testing on databases, and hoping to improve their database mastery through testing.
Indicate that the purpose of your testing is to improve your ability and to do a better test; improving your ability is not for future transfer
development or other purposes, unless The employer has such an arrangement.
Do not express your interest too much outside the scope of the recruiting company. For example, the recruiting company is engaged in financial software, but you show interest in game software; or the recruiting company is engaged in JAVA development, but your interest is in C language programs. Development.

24.What do you think are the advantages of testing?

There is no fixed answer to this interview, but you can refer to the following points and combine them with your own characteristics:
Resilient
Patience< /span>Strong communication skills Have confidence to do everything well Like to face challenges
Organized in doing things

I have good reviews from previous managers that show I am doing a good job

25.What strategies do integration tests usually have?

1. Big bang integration
2. Top-down integration
3. Bottom-up integration
4. Sandwich integration is suitable for most software development projects
5. Backbone integration
6. Layered integration
7. Based on Functional integration
8. Message-based integration
9. Risk-based integration
10. Progress-based integration a>

26. Commonly used X UNIX commands x (common Linux commands) ) (at least 10); (Unix)

Answer: ls pwd mkdir rmdir rm cp mv cd ps ping tail more echo adduser passwd logout exit,
See the Linux textbook.

27. Briefly describe what you have done in your previous job and what you are familiar with.

This problem is different for everyone. The reference answer is as follows.
My main job in the past was system testing and automated testing. During the system test, the business logic functions of the BOSS system and the Class 5 features of the softswitching system were tested. The performance test is mainly a stress test to obtain the system response time and system resource consumption under different numbers of requests. Automated testing mainly tests softswitch feature testing by writing your own scripts and combining some third-party tools. In testing, I feel that a completely accurate understanding of user needs is very important. In addition, the management of BUG must be based on requirements, and not all BUG need to be modified. Testing requires patience and meticulousness, because in the new version, although most of the originally discovered BUGs have been fixed,

Correct functionality may also become incorrect. Therefore, focus on iterative testing and regression testing.

28,What is the use of c static in C/C++? (Please describe at least two types)

1) In the function body, a variable declared as static maintains its value while the function is called.
\2) Within the module (but outside the function body), a variable declared as static can be accessed by functions used in the module, but
cannot be accessed by the module accessed by other functions. It is a local global variable.
\3) Within a module, a function declared as static can only be called by other functions in this module. That is, this
function is restricted to the local scope of the module in which it is declared

29.What is the difference between a reference and a pointer?

\1) References must be initialized, not pointers.
\2) The reference cannot be changed after initialization, and the pointer can change the object pointed to.
\3) There is no reference to the null value, but there is a pointer to the null value.
t What network protocol does the Internet use? What are the main hierarchies of the protocol? t Internet physical address and P IP address translation
What protocol is used?

30,TCP/IP 协议

The main hierarchical structure is: application layer/transport layer/network layer/data link layer.
ARP (Address Resolution Protocol)

31.Tell me about your understanding of the two strategies of top-down integration and bottom-up integration in integration testing, and talk about their respective advantages**** Disadvantages and which types of tests it is mainly suitable for;

1. Top-down integration
Advantages: Verify the main control and judgment points earlier; according to depth priority, a complete software function can be implemented and verified first Disadvantages: Large amount of column development; low-level verification is delayed; low-level component testing is insufficient.
Function; functions are proven earlier, bringing confidence; only one driver is needed, reducing driver development costs; supports fault isolation.

It is suitable for product control structure that is relatively clear and stable; the high-level interface changes little; the bottom-level interface is undefined or may often be modified
; the production control component has relatively large technology Risks need to be verified as early as possible; we hope to see the system function
behavior of the product as soon as possible.
2. Bottom-up integration
Advantages: Early verification of underlying component behavior; work can initially be integrated in parallel, which is more efficient than top-down; reduces Stub's
workload; supports fault isolation.
Disadvantages: The driver development workload is heavy; high-level verification is delayed, and design errors cannot be discovered in time.
Adapt to the low-level interface which is relatively stable; the high-level interface changes more frequently; the low-level components are completed earlier.

软件验收测试包括 ___ 、 ___ 、 ____ 三种类型。
软件验收测试包括正式验收测试、alpha 测试、beta 测试三种测试。
2 2 ．系统测试的策略有 ____________________________等 等  15  种方法。（该题
5 15  个空）
系统测试的策略有很多种的，有性能测试、负载测试、强度测试、易用性测试、安全测试、
配置测试、安装测试、文档测试、故障恢复测试、用户界面测试、恢复测试、分布测试、可
用性测试。
3 3 ．设计系统测试计划需要参考的项目文档有 ___ 、 ___ 和 ____ 。
设计系统测试计划需要参考的项目文档有**软件测试计划、软件需求工件、和迭代计划。**
4 4 ．通过画因果图来写测试用例的步骤为 ___ 、 ___ 、 ___ 、 ___ 及把因果图转换为状态图共五
个步骤。 利用因果图生成测试用例的基本步骤是：
§ 分析软件规格说明描述中，哪些是原因（即输入条件或输入条件的等价类），哪些是结
果（即输出条件），并给每个原因和结果赋予一个标识符。
§ 分析软件规格说明描述中的语义，找出原因与结果之间，原因与原因之间对应的是什么
关系? 根据这些关系，画出因果图。
§ 由于语法或环境限制，有些原因与原因之间，原因与结果之间的组合情况不可能出现。
为表明这些特殊情况，在因果图上用一些记号标明约束或限制条件。 § 把因果图转换成判
定表。
§ 把判定表的每一列拿出来作为依据，设计测试用例。
一、 测试的种类很多，比如：
代码、函数级测试
模块、组件级测试
系统测试
请说出这些测试最好由那些人员完成，测试的是什么？
代码、函数级测试一般由白盒测试人员完成，他们针对每段代码或函数进行正确性检验，检
查其是否正确的实现了规定的功能。

模块、组件级测试主要依据是程序结构设计测试模块间的集成和调用关系，一般由测试人员
完成。
系统测试在于模块测试与单元测试的基础上进行测试。了解系统功能与性能，根据测试用例
进行全面的测试。

32. What aspects should be considered when designing test cases, that is, which aspects are tested by different test cases?

What you need to pay attention to when designing test cases is that in addition to the overall process and functions, you also need to pay attention to strength testing, performance testing
testing, stress testing, boundary value testing, stability sexual testing, safety testing and many other aspects. (The four basic elements that test cases need to consider are input, output, operation and test environment; in addition, test cases need to consider test type (function, Performance, security...), you can refer to TP to answer this part. In addition, you also need to consider the importance and priority of the use case)

33. When saving a text file under s windows, a save dialog box will pop up. If you create a test case for the file name,

How should equivalence classes be divided?
Single byte, such as A;
Double byte, AA, me;
Special character /‘. ';, =-, etc.;
reserved words, such as com;
file format is 8.3 format;
file name format It is in non-8.3 format;
/,, and other nine special characters.
Suppose there is a text box that requires the input of a 10-character postal code. How should the text box be divided into equivalence classes?
Special characters, such as 10 or ￥;
English letters, such as ABCDefghik;
Less than ten characters, such as 123;
More than ten characters, such as 11111111111;
Mixed numbers and others, such as 123AAAAAAA;
Null character;
Reserved character

34. When does the software testing project start? Why?

Software testing should be involved in the requirements analysis stage, because the object of testing is not just program coding, but all products produced during the software development process should be tested, and software defects tend to amplify. The later a defect is discovered, the more expensive it will be to fix it. The greater the cost.

35.What is white box testing? What is black box testing? ? What is regression testing? ?

Answer: White-box testing requires the tester to understand the program structure and processing process, test the program according to the internal logic of the program, and check whether each path in the program works correctly according to predetermined requirements. It mainly focuses on the program under test Source code, the tester does not need to consider the function of the program at all.
White box testing process: detailed design –> source program –> analysis of the internal logical structure of the program –> flow chart –> Develop test cases –>Program under test –>Execution path –>Coverage analysis.
Black-box testing: (Black-box Testing, also known as functional testing or data-driven testing) Treat the test object as a black box. When using the black box testing method for dynamic testing, the functions of the software product need to be tested, and the internal structure and processing process of the software product do not need to be tested.
Regression testing: (regression testing): There are two types of regression testing: use case regression and error regression; use case regression is to go back and re-test previously used use cases after a period of time. See You will find the problem again. Error regression is a method of re-verifying the defects that appeared and fixed in the previous version in the new version, and testing the relevant modified parts with the defects as the core.

36. What is the focus of unit testing, integration testing, and system testing?

Unit testing is aimed at the smallest unit of software design - program module (functions and procedures in process-oriented; classes in object-oriented). The test work of correctness verification is to discover the internal contents of each program module Possible errors. Generally there are two steps: manual static inspection\dynamic execution tracking
Integration testing is aimed at testing the components integrated by each module that has passed the unit test. Its main content It is the interface between each unit module and the functions implemented by each module after integration. System testing is aimed at the integrated software system, as an element of the entire computer system, together with computer hardware\peripherals\certain supporting software\ Data and other system elements such as personnel are combined together, and a series of integration tests and confirmation tests must be conducted on the computer system in the actual operating environment.

37. Methods of designing use cases:

Using different test methods at different stages of testing, the basis for designing test cases is different:
The following methods are used to design white-box test cases: logic coverage, loop coverage and basic path coverage< /span>

Black box test case design methods: equivalence class division, boundary value analysis, error guessing, cause-effect diagram, state chart, test outline, scenario method, orthogonal strategy table.

38. What qualities should a test engineer possess?

1. Responsibility
2. Communication skills
3. Teamwork spirit
4. Patience and carefulness , Confidence
5. Always maintain a skeptical attitude and have an awareness of defect prevention

6. Have certain programming experience

39. What strategies are usually used for integration testing?

Integration based on decomposition: big bang integration\top-down integration\bottom-up integration\sandwich integration\call graph-based
integration\path-based integration\layered Integration\Function-based integration\High-frequency integration\Progress-based integration\Risk set-based
Integration\Event-based integration\Usage-based integration\C/S integration
Question 2: What types of software testing do you know? Briefly introduce them.
Classified by testing strategy: 1. Static and dynamic testing 2. Black box and white box testing 3. Manual and automatic testing 4. Smoke testing
Test 5 , Regression testing;
Classification by testing stage: unit testing, integration testing, system testing;
Other common testing methods: 1. Functional testing 2, Performance testing 3 , Stress test 4, Load test 5, Usability test 6,
Installation test 7, Interface test 8, Configuration test 9, Document test 10, Compatibility test 11, Security test 12, Recovery test

40. What do you think is the key to good test planning?

Clarify the goals of the test and enhance the practicality of the test plan

The important purpose of writing a software test plan is to enable the testing process to discover more software defects. Therefore, the value of the software test plan depends on its help in managing the test project and identifying potential defects in the software. Therefore, the test scope in the software test plan must highly cover functional requirements, the test method must be practical and feasible, the test tool must be highly practical and easy to use, the generated test results must be intuitive and accurate, adhere to the "5W" rule, and clarify the content and The process “5W” rules refer to “What”, “Why”, “When”, “Where”, and “How”. Using the "5W" rule to create a software test plan can help the testing team understand the purpose of testing (Why), clarify the scope and content of testing (What), determine the start and end dates of testing (When), and indicate the testing methods and tools ( How), giving the storage location (Where) of the test documents and software.

Use a review and update mechanism to ensure that the test plan meets actual requirements. After the test plan is written, if it is sent directly to the test team without review, the content of the test plan may be inaccurate or the test content may be missed, or the test scope may increase due to changes in software requirements. reduction, and the content of the test plan was not updated in a timely manner, misleading the test execution personnel.

Create test plans and test detailed specifications and test cases respectively. Detailed test technical indicators should be included in independently created test detailed specification documents, and test cases used to guide the test team to execute the test process should be placed in independently created test case documents or test cases. Use case management database.

There is a strategic and tactical relationship between test plans, detailed test specifications, and test cases. Test plans mainly plan the scope, methods, and resource allocation of test activities from a macro perspective, while detailed test specifications and test cases are specific tactics for completing test tasks.

41. What do you think is the key to good test case design?

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 black-box test case design is also to use fewer use cases. Covers module output and input interfaces. It is impossible to completely measure

Try to find the most problems in a reasonable time with the fewest use cases

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

The purpose of performance testing is mainly to discover whether there will be any differences from requirements during concurrent multi-user and large data operations
. The key to performance testing is to do system analysis and functional analysis to determine the system bottleneck (see ATT
Chapter 10 LoadRunner PPT here).

43. What are your testing career development goals?

The more testing experience, the higher the testing ability. Therefore, my career development requires time and accumulation, and I will run towards a senior test engineer step by step. And I also have a preliminary career plan. I have accumulated testing experience in the first three years, constantly updating and correcting myself, and doing a good job in testing tasks.

44. How much do you know about our company?

It is recommended to get more information from job advertisements, and at the same time go to the website of the company you are applying for to learn as much about the company as possible
in order to answer these questions well.

45. What are the criteria for ending the test?

From a micro perspective, it is defined in the test plan. For example, if the system runs smoothly for 72 hours under certain performance, there are currently no serious bugs in this version of the Bug
Tracking System. , the number of common BUGs is less than 3, the BUG repair rate is more than 90%, and other parameters, and then the development manager, test manager, and project manager jointly sign and approve the version release. If we talk about it macroscopically, it means that when the software disappears completely, the test will end.

46. ​​Software testing is divided into black box and white box. Which situations are suitable for each? ?

Software testing methods are generally divided into two types: white box testing and black box testing. White box testing is also called structural testing, logic driven testing or testing based on the program itself. It focuses on the internal structure and algorithm of the program and usually does not care about the function and performance. Indicators; black box testing is also called functional testing, data-driven testing or specification-based testing. It actually stands from the standpoint of the end user to verify input and output information and Whether the system performance indicators meet the functional requirements and performance requirements specified in the specifications.

47. What stages should a complete set of tests consist of?

Feasibility analysis, requirements analysis, outline design, detailed design, coding, unit testing, integration testing, system testing, acceptance
Acceptance testing

48. What content do test cases usually include?

The use cases of different structures include different ones. (version, number, project, designer, design date, input, expected output...)
The basic elements of software test cases include test case number, test title, importance level, test input, operation Steps, expected results.
Test case number: The number of test cases has certain rules. For example, the number of system test cases is defined as follows:
PROJECT1 -ST-001, the naming rule is project name + test phase type (system test phase) + number. Define the test case number to facilitate the search of test cases and the tracking of test cases.
Test title: A description of the test case. The test case title should clearly express the purpose of the test case. For example, "Test the response of the software when the user enters an incorrect password when logging in."
Importance level: Define the priority level of test cases, which can be generally divided into two levels: "high" and "low". Generally speaking, if the priority of a software requirement is "high", then the priority of the test cases for that requirement is also "high"; vice versa, generally speaking, it is a 5-level division.
Test input: Provides various input conditions in test execution. Determine the input of the test case based on the input conditions in the requirements. The input of test cases has a great dependence on the input in the software requirements. If the input of the requirements is not well defined in the software requirements, then there will be great obstacles in the test case design.
Operation steps: Provides steps for the test execution process. For complex test cases, the input of the test case needs to be completed in several steps. This part is listed in detail in the operation steps.
Expected results: Provide the expected results of test execution. The expected results should be based on the output in the software requirements. If in

During the actual testing process, if the actual test results obtained do not match the expected results, then the test fails; otherwise, the test passes.

49. Do you understand the software development process of the companies you worked for in the past? If you understand, please describe what work needs to be completed in a complete development process? What are the different roles that perform these tasks? What specific tasks have you been engaged in in your previous testing work? Which part of the job are you best at?

Development process—requirements research (requirements personnel), requirements analysis (requirements personnel), outline design (designers), detailed design (designers), coding (developers) ) Testing process - requirements review, system test design, outline design review, integrated test design, detailed design review, single meta-test design, test execution a> The process determines the quality. The process improvement of software is precisely to improve the quality of the software and combine various past experiences. and lessons accumulated. I have done the entire process of testing work and am good at test design

50,Who were the participants in the testing activities you experienced? What is your role?

There are project managers, development managers, system analysts, designers, developers, quality managers, test managers, testers
test designers and testers a>
Served as test manager, test designer, tester
What are the principles of test case design? What are the current main test case design methods?
Representativeness: able to represent and cover a variety of reasonable and unreasonable, legal and illegal, boundary and transboundary, and extreme
inputs Data, operations and environment settings, etc.
Decidability: That is, the correctness of the test execution results is decidable, and each test case should have corresponding expected results.< a i=7> Reproducibility: That is, for the same test case, the execution results of the system should be the same. Methods include equivalence class, boundary value, cause and effect diagram, state diagram, orthogonal method, outline method How many methods are there for object-oriented test case design? How to achieve? Design a set of test cases for each constructor in the class Combine class variables and instance variables in the class Combination Various methods in the class Design test cases based on preconditions and postconditions Design test cases based on code LoadRunner What are the three modules? Please briefly describe the main functions of each module. Virtual User Generator: for recording footsteps Mercury LoadRunner Controller: for creating, running and monitoring scenarios

Mercury LoadRunner Analysis: used to analyze test results

51.What is your greatest interest in testing? Why?

The biggest interest is that the test is difficult and challenging! The longer I do testing, the more I realize how difficult it is to do it well. I once saw an article on the Wuyou test website about how to be a test engineer. A total of 11 and 12 points are listed, some of which are related to people's personality, and some of which require acquired efforts. But except for the character-related aspects 1 and 2, which I am not sure about, I am very confident in doing it well in other aspects. When I first entered the testing industry, my understanding of testing was from some information I learned from the Wuyou Test Network. At that time, I was aiming to do testing which requires many skills. Only by doing it well can I do it well. Although it is easy to get started, it is difficult to do it well. It is more difficult than development. Although I really wanted to do development at the time (I basically did not miss professional classes in school because I like my Professional), but seeing that testing is more difficult and challenging than development, I became more determined to do a good job in testing. I think there are 2 points in the whole test process that I find very difficult (for me, I am very interested in difficult things )

The first is the design of test cases, because the essence of testing lies in the design of test cases. Before the version is released
, the test cases must be written well and what tests should be used How to write? (i.e. test plan or test strategy), if you just test a
new task, you have to spend a certain amount of time to digest the business requirements and technical foundation. The business requirements are easy to understand (Duohe The goal can be achieved by communicating with product managers
and developers), but the technical foundation is not that simple, which requires your conscious learning ability. For example, take a website. For the most basic technical knowledge, you need to know how the website operates internally and how does the backend respond to user requests? How to set up a test environment? These need to be learned at the earliest. What difficulties might you encounter if you can at least make basic preparations before starting the test? Are the requirements details not determined yet? These problems can be discovered when designing use cases. The second time is to find BUGs. This should be the most basic task of the tester. Generally, you can find most of them by starting the test according to the test case Bugs, and some bugs need to be better understood during the testing process to obtain more information about the version being tested, supplement test cases, and test out bugs. And how to find bugs? This requires to find bugs through care and patience when the test cases are valid. Bugs may be found in every use case, and errors may occur everywhere, so How to describe a bug is also very particular. Under what circumstances will the bug occur? If the conditions change just a little bit, the bug will not exist. Think clearly during the testing process (you have to look carefully at the data flow and results of the testing process, and bugs are found there). For example

What are the minimum steps to reproduce this bug? What is the pattern of this bug? If you are good enough, you can help developers initially locate the problem.

52, Question 15: What are your testing career development goals?

The more testing experience, the higher the testing ability. Therefore, my career development requires accumulation of time, and I am running towards a senior testing engineer step by step. And I also have a preliminary career plan. After accumulating testing experience in the first three years, I will learn how to be a good test engineer

At 11 and 12 o'clock, ask yourself to constantly update and correct yourself, and do a good job in testing tasks.

**53. What types of software testing are you familiar with? Please try to compare the differences and connections between these different test types.

Test types include: functional testing, performance testing, and interface testing. Functional testing accounts for the largest proportion of testing work, and functional testing is also called black box testing. Treat the test object as a black box. When using the black box testing method for dynamic testing, the functions of the software product need to be tested, and the internal structure and processing process of the software product do not need to be tested. Methods for designing test cases using black box technology include: equivalence class division, boundary value analysis, error speculation, cause-and-effect diagrams and comprehensive strategies.
Performance testing is to test various performance indicators of the system through automated testing tools to simulate a variety of normal, peak and abnormal load conditions. Both load testing and stress testing are performance tests, and the two can be combined. Through load testing, the performance of the system under various workloads is determined. The goal is to test the changes in various performance indicators of the system when the load gradually increases. Stress testing is a test that determines the bottlenecks or unacceptable performance points of a system to obtain the maximum service level that the system can provide. Interface testing, the interface is the most direct layer of interaction between software and users. The quality of the interface determines the user's first impression of the software. Moreover, a well-designed interface can guide users to complete the corresponding operations themselves and act as a guide. At the same time, the interface is like a human face, which has the direct advantage of attracting users. A well-designed interface can bring users a sense of relaxation, pleasure and success. On the contrary, due to the failure of interface design, users will feel frustrated. No matter how practical and powerful functions are, they may be wasted in users' fear and abandonment.
The difference is that functional testing focuses on all functions of the product, taking into account every detailed function and every possible functional problem. Performance testing mainly focuses on the stability and robustness of the entire product under multi-user concurrency. Interface testing focuses more on user experience. When users use the product, whether it is easy to use, easy to understand, standardized (shortcut keys and the like), beautiful (can it attract the user’s attention), and safe (try to The front desk prevents users from unintentionally entering invalid data. Of course, considering the experience, a warning cannot be popped up too rudely)? When doing a certain performance test, first it may be a function point. First of all, you must ensure that its function is OK, and then consider the performance test of this function point

**54. Please try to compare black box testing, white box testing, unit testing, integration testing, system testing, and acceptance testing.

Differences and connections
Black box testing: Knowing the functional design specifications of the product, tests can be conducted to prove whether each implemented function meets the requirements
Ask.
White box testing: The internal working process of the product is known, and it can be tested to prove whether each internal operation meets the design specifications
and whether all internal components meet the requirements of the design. After inspection.
Black box testing of software means that testing is performed at the interface of the software. This method treats the test object as a black box. The tester does not consider the internal logical structure and internal characteristics of the program at all, and only relies on the program's requirements specifications. =7> Check whether the function of the program complies with its functional description. Therefore, black box testing is also called functional testing or data-driven testing. Black box testing is mainly to find the following types of errors: 1. Are there any incorrect or missing functions? 2. Can the input be accepted correctly on the interface? Can it output correct results? 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? White box testing of software is a detailed examination of the procedural details of the software. This method regards the test object as an opened box, which allows the tester to use the internal logical structure and related information of the program to design or select test cases, Test all logical paths of the program. Determine whether the actual state is consistent with the expected state by checking the program state at different points. Therefore, white-box testing is also called structural testing or logic-driven testing. White box testing mainly wants to perform the following checks on the program module: 1. Test all independent execution paths of the program module at least once. 2. For all logical judgments, both "true" and "false" situations can be tested at least once. 3. Execute the loop body within the boundary of the loop and the limit of the operation. 4. Test the validity of the internal data structure, etc. A unit test (module test) is a small piece of code written by the developer to verify whether a small, clear function of the code under test is correct. Generally speaking, a unit test is used to determine the behavior of a specific function under a specific condition (or scenario). Unit testing is completed by the programmers themselves, and the programmers themselves ultimately benefit. It can be said that programmers are responsible for writing functional code, and they are also responsible for writing unit tests for their own code. Executing unit tests is to prove that this code behaves as we expect. Integration testing (also called assembly testing, joint testing) is a logical extension of unit testing. In its simplest form, two already tested units are combined into a component and the interface between them is tested. In this sense, a component refers to an integrated aggregation of multiple units. In real-life scenarios, many units are combined into components, which are aggregated into larger parts of the program. The approach is to test combinations of fragments and eventually extend the process to test your module with other groups of modules. Finally, all the modules that make up the process are tested together. System testing is to assemble the tested subsystems into a complete system for testing. It is an effective method to verify whether the system can indeed provide the functions specified in the system solution specification. (Common joint debugging testing) The purpose of system testing is to comprehensively test the final software system to ensure that the final software system meets product requirements and follows the system design.

Acceptance testing is the last testing operation before deploying the software. The purpose of acceptance testing is to ensure that the software is ready and can be used by end users to perform the software's intended functions and tasks. Acceptance testing demonstrates to future users that the system will work as intended. After integration testing, all modules have been assembled into a complete software system according to the design, and interface errors have been basically eliminated. Then the effectiveness of the software should be further verified. This is the task of acceptance testing, that is, the function and function of the software. Performance is as users would reasonably expect.

55. How do you deal with it when the developer says it’s not a BUG?

The developer said it is not a bug. There are two situations. One is that the requirements are not determined, so I can do this. At this time, I can find the product manager to confirm whether changes are needed. The three parties will discuss and determine whether to make changes. Second, this situation cannot happen, so there is no need to modify it. At this time, I can first tell what is the basis for a BUG as much as possible? What adverse consequences will there be if it is discovered by users or something goes wrong? The programmer may give you many reasons and you can refute his explanation. If it still doesn't work, then I can raise this issue and confirm it with the development manager and test manager. If you want to modify it, change it. If you don't want to modify it, don't change it. In fact, some of them are really not bugs. I just wrote them into the TD in the way I suggested. If the developers don't modify them, there won't be a big problem. If it is determined to be a bug, you must stick to your position and let the problem be finally confirmed.

56. Why should software testing be carried out in a team?

Because it is difficult to know the quality of software that has not been tested before it is released. Just like ISO quality certification, testing
also requires quality assurance. At this time, The work of software testing needs to be carried out in the team. During the testing process, problems in the software are discovered
and the developers are informed and corrected in a timely manner. When the release is about to be released, the problems can be obtained from the test report
The quality of the software.

57. If you had the opportunity to become a developer, would you do development work?

If the company really needs me, I can engage in development, but I still like to do testing. I think I am more suitable for testing.

58. What should a test plan include?

Background, project introduction, purpose, test scope, test strategy, personnel division of labor, resource requirements, schedule, reference documents, common terms, submission documents, risk analysis.

59. Considering the software industry background, how do you understand the software business?

Read the user manual to understand the functions and operating procedures of the software; read some professional books on business to supplement business knowledge; if there is actual user data, you can refer to the actual data; refer to previous use cases and BUG reports; in the process of using the software Think more; communicate more with product managers.

60. What should the test cases include?

Number, module name, author, date, operation instructions, input data, expected results, etc.
How to position the role of test cases?
Organization: writing, organization, functional coverage, repeatability, tracking, test confirmation

61, What is the most important during the testing process?

Requirements Planning.

62, What is compatibility testing? Please provide an example of how to use the compatibility test list for testing.

Mainly verifies the compatibility of software products between different versions. Including backward compatibility and cross compatibility, backward compatibility is to test whether a new version of software retains the functionality of its earlier version, and cross compatibility is to verify the coexistence of two related but different products< Compatibility between /span>.

63, I tested a certain software and found that it ran very slowly on 8 WIN98. How to determine whether there is a problem with the software or with the software and hardware operating environment?

Look at the operating environment requirements of the software. If the requirements are met, there is a problem with the program; if the requirements are not met, there is a problem with the hardware system.