Software Test interview FAQ (2)

1. What is the difference between the phase review and the peer review?
Reference answer:
Peer review Objective: To discover Small ScaleWorkProduct error, as long as it is an error;
Stage review Objective: To review the correctness, feasibility, and integrity of works in the module stage
Peer reviewers: 3-7 persons must be trained at peer review meetings, guided by SQA
Number of reviewers at the stage: About 5 reviewers must be experts with system review qualifications
Peer review content: small content general document <40 pages, Code <500 lines
Stage review content: the content is large, mainly focusing on
Peer review time: a small part of work products completed
Phase Review time: usually set at the time point of the Key Path
2. What isSoftware TestingAnd its purpose?
Reference answer:
Software testing is the process of running or measuring a system using manual or automated means. The purpose is to test whether it can meet the specified requirements or clarify the differences between the expected results and the actual results.
3. Briefly describe the integration test process?
Reference answer:
Integration test process:
After completing the software outline design, start to develop the integration test plan-design the integration test case and test process-implement the integration test, design the required driver and the pile-execute the integration test, record Test Results-evaluation integration test, evaluate the test based on the test results, and generate the evaluation report document. (Driver or pile function is doneUnit Test. A driver is the main program that tests the four functions. It receives test data, transmits the data to the tested unit, and then outputs the test result. When the units under test can complete related functions, do not drive the units. Is used to replace the sub-unit called by the tested unit .)
4,White box testingWhich methods are available?
Reference answer: Code Review, statement coverage, decision coverage, condition coverage, combination coverage, basic path, formal method, and symbolic execution
5. Briefly describe the types of test targets?
Reference answer:
Function Testing, Load testing,Performance Testing, Security testing, recovery testing, installation testing, compatibility testing, availability testing, reliability testing, international testing, and localization testing.
6. How can I perform a document test?
Reference answer:
The test of the document mainly adopts the static test, that is, the walk-through method, which can be based on the peer review, list a checklist, and then sit down together to read the tested document and troubleshoot it. The document is usually very long, and the general recommendation is that a peer review step can take no more than two hours. Therefore, when testing the document to be tested, you can list a plan and break down the overall document, perform multiple queries on the tested documents as planned.
7. What are the criteria for testing completion?
Reference answer:
From the perspective of project cycle:
1. the test time has been exceeded;
2. The allocated test resources are exhausted;
3. reached a fixed milestone (such as the delivery date specified in the contract ).
From the test perspective:
1. Test the requirement coverage rate;
2. Test the code coverage rate;
3. Test Case measurement;
4. Defect check measurement
8. What is the difference between alpha testing and beta testing?
Reference answer:
Alpha testing is a test performed by a user in the development environment, or a controlled test performed by the company's internal users in the simulated actual operating environment, alpha testing cannot be performed by programmers or testers. Errors Found during alpha testing can be immediately reported to developers at the testing site for timely analysis and handling. The purpose is to evaluate the functions, usability, reliability, performance, and support of software products. Pay special attention to the product interface and features. Alpha testing can start after the software product code is complete, or after the module (subsystem) test is complete, you can also start after the product reaches a certain degree of stability and reliability during the validation test. Relevant manuals (drafts) should be prepared before Alpha testing.
Beta testing is performed by multiple users of the software in the actual use environment of one or more users. Developers are usually not present at the test site, and beta testing cannot be completed by programmers or testers. Therefore, beta testing is a field application of software in an environment beyond the control of developers. During the beta test, the user records all problems encountered, including authentic and confirmed by the supervisor, and reports to the developer on a regular basis. The developer makes changes after comprehensive user reports, finally, deliver the software to all users. Beta testing focuses on product support, including documentation, customer training, and support product production capabilities. Beta testing can be started only when Alpha testing reaches a certain degree of reliability. Because the main purpose of the beta test is the test supportability, the beta test should be managed by the person who hosts the product release as much as possible.
9. Does the system test plan need to be approved by peers? Why?
Reference answer:
Required. The system test plan is a key document of the project phase and therefore needs to be reviewed.
10. What is the difference between load testing, capacity testing, and strength testing?
Reference answer:
Load Testing: The system load and response time under a certain workload.
Strength Testing: The Impact of continuous system operation over a long period of time on system performance under certain load conditions.

Capacity Test: the purpose of the capacity test is to analyze the limit values (such as the maximum number of concurrent users and number of database records) of a certain indicator that reflects the application characteristics of the software system in advance ), the system does not have any software faults or can maintain the normal operation of the main functions in its limit state. The Capacity Test also determines the maximum load or workload that can be continuously processed by the test object within a given period of time. The purpose of the capacity test is to enable the system to withstand excessive data capacity to detect whether the system can process the data correctly. Capacity Testing is data-oriented and aims to display the data capacity that can be determined by the system to process the target.

01. Why should I perform software testing in a team?
The last entry to ensure software quality.
02. Do you know the software testing process of the company you have previously worked on? If you understand this, please try to explain what work has to be done in this process? Which roles are used to complete these tasks?
Test Plan-> test design (test cases, test data)-> test execution (unit test, integration test, system test, regression test)
05. What types of software testing are familiar to you? Try to compare the differences and relationships between these different test types (such as function testing and performance testing ......)
Usability test-user-friendly interface and convenient operation.
Function Testing-meeting functional requirements in the system
Security Testing-whether the system has security risks and vulnerabilities
Performance testing-response speed and robustness of the system under high concurrency
06. Try to compare the differences and connections between black box testing, white box testing, unit testing, integration testing, system testing, and acceptance testing.
Black/white box: the main difference is whether you understand the internal structure and code of the system or program.
Unit test: Focus on the correctness of a unit, function, and module. Generally, you need to write relevant test code.
Integration Test: a module or module can be directly integrated with an interface for testing. A single module can be used for testing.
System test: A complete functional test.
07. What is the purpose of the test plan? What are the content of the test plan? Which of the following are the most important?
Select Test Tools, Test types, and personnel requirements in advance to ensure coordination with project development and smooth testing.
08. What do you think is the key to a good test plan?
Understand business needs of projects or systems
Coordinate with the project manager to understand the project schedule
09. What test case design methods are familiar to you? Use specific examples to describe the application of these methods in the test case design.
Border Value/equivalence class/business flow chart analysis and state conversion analysis/business logic analysis
10. What do you think is the key to designing test cases?
The business and software requirements are very clear. You can choose different test case designs based on different requirements.
12. Have you reviewed test cases in your previous work? If any, describe the test case review process and review content.
Review Plan-> preliminary review-> review;
The review mainly covers the software requirements of test cases, determines whether to consider related boundaries, whether to prepare multiple sets of test data for complex processes, and whether there are tests specifically designed for non-functional requirements.
13. Have you ever performed performance testing? If you have any, describe the complete process of your previous performance tests as much as possible.
Plan creation> test function> test tool> recording SCRIPT> Run test> analysis result
14. Have you used some testing tools when performing performance testing? If so, try to describe how the tool works and describe how the tool is applied in actual work with an example in the work.
Microsoft was, LoadRunner
15. What do you think is the purpose of Performance Testing? What is the key to a good performance test?
The key is to record the test script. The test environment is clean during testing.
16. In your past work, what content does a software defect (or bug) record contain? How can I submit high-quality software defect (Bug) records?
Defect terminology/description/defect level/Severity/discovery module/discovery steps and processes/can be reproduced
17. Have you used some tools to manage software defects (bugs) in your previous software testing work? If any, use this tool to describe the software defect (Bug) tracking management process.
You can also use free tools such as bugfree.
19. What do you think of software process improvement? Do you have any improvements in your company? What is the ideal working environment for testers?
Consolidate advanced experiences or ideas into the process and improve the software quality through process improvement and capability improvement.

1 white box, black box, static, dynamic, manual, automatic, smoke test, recycle test, beta test. 2 unit test, integration test, validation test, system test, acceptance test. 3 lr3 part: user action design, scenario design, test and analysis part steps: test and test. Design User Virtual scripts. Design scenario. Run the test. Monitoring scenario. Analyze the test results. 4 Black Box: function division, equivalence class division, Boundary Value Analysis, cause and effect, the testing methods for Error Prediction and white box testing include code check, static structure analysis, static quality measurement, logical coverage, basic path testing, domain testing, symbol testing, Z path coverage, program variation. The coverage standards of the white box test method include logical coverage, cyclic coverage, and basic path testing. Logical overwrites include statement overwrites, decision overwrites, condition overwrites, decision/condition overwrites, condition combination overwrites, and path overwrites. 5. To ensure the controllability of test activities, software test configuration management must be performed during the software test process. Generally, the most basic activities in Software Test configuration management include the configuration item identification, configuration item control, configuration status report, and configuration audit 6 Criteria for passing the Software acceptance test: 1. All functions defined in the Software Requirement Analysis specification have been fully implemented, and all performance indicators have met the requirements. 2. All test items have no residual errors of level 1, level 2, and level 3. 3. project approval form, requirement analysis document, design document, and code are consistent. 4. Complete Acceptance Test artifacts (test plan, test cases, test logs, test tickets, and test analysis reports) 7. Six quality features of the software include: ______ ① Function, reliability ② availability, efficiency ③ stability, portability 8/integration test plan how to write? Think about the following and write it down using the integration test plan template: 1. Determine integration test objects 2. Determine integration test policies 3. Determine integration test acceptance criteria 4. Determine integration test suspension and recovery conditions 5. Estimate Integration Test workload 6. Estimate Integration test requirements resource 7. Division of integrated test tasks (including Task Name, owner, input and output, risks and countermeasures, and Schedule) 9. List of artifacts produced by integration testing 1. Software integration test plan 2. Integration Test Case 3. Test process 4. Test script 5. Test log 6. Test Evaluation summary 10 static analysis the source code of the software is studied, you do not need to compile or execute code to locate errors or collect metric data. Dynamic analysis is to provide execution tracking, time analysis, and test coverage information by observing the actions of the software runtime. Insert: insert into Table1 (field1, field2) values (value1, value2) Delete: delete from Table1 where range updated: Update Table1 set field1 = value1 where range