Foreword:
Why is there this article today? A few days ago, my friends in the Hapi group had suffered software test interviews in Waterloo. They all said they knew Selenium and learned all kinds of tests in school. As a result, the interviewer was speechless when asked. To help you understand some simple basic knowledge of software test interview.
Soon the New Year, next year's school enrollment as well as preparing for interviews, really can collect (back) down in your head, of course, we want the Happy group of friends and I chat software testing interview, technical problem analysis, direct Click here ✔
Please introduce unit testing, integration testing, system testing, acceptance testing, regression testing
unit test
Complete the verification of the smallest software design unit (module), the goal is to ensure that the module is correctly coded, use the process design description as a guide, test important control paths to find errors in the module, usually white box , Perform static tests on code styles and rules, program design and structure, business logic, etc., and find and resolve errors that are not easy to appear early.
Integration Testing
Problems related to the module interface are found through testing. The goal is to take the modules that have passed the unit test and construct a program structure described in the design. One-time integration should be avoided (unless the software scale is small), and incremental integration should be used.
Top-to-bottom integration: The order of module integration is to integrate the main module first, and then integrate down according to the control hierarchy. The modules belonging to the main module are integrated into the entire structure in a depth-first or breadth-first manner.
Bottom-up integration: start from the atomic module for construction and testing, because the module is integrated from the bottom up, it is required that all modules belonging to a given top level always exist, and there is no longer a stable test pile Necessary.
System test
It is a black box test based on the overall system requirements specification, which should cover all joint components of the system. System testing is a test for the entire product system. The purpose is to verify whether the system meets the definition of the requirement specification, and to find out what is inconsistent with or contradictory to the requirement specification. The object of system testing includes not only the software of the product system that needs to be tested, but also the hardware, peripherals and even some data, some supporting software and its interfaces on which the software depends. Therefore, the software in the system must be combined with various dependent resources and tested in the actual operating environment of the system.
Regression Testing
Regression testing refers to retesting the previous test cases after modification to ensure the correctness of the modification. Theoretically, when a new version of the software is generated, regression testing is required to verify whether the previously discovered and fixed errors appear again in the new software version. Re-test according to the repaired defects. The purpose of regression testing is to verify that defects that have appeared before but have been fixed no longer reappear. Generally refers to the re-testing of a known corrected defect around the steps when it originally appeared.
Acceptance Test
Acceptance testing refers to a phase of the system development life cycle methodology, when relevant users or independent testers test and accept the system according to the test plan and results. It allows system users to decide whether to accept the system. It is a test to determine whether the product can meet the requirements specified by the contract or the user. Acceptance testing includes Alpha testing and Beta testing.
Alpha test
It is carried out by the user at the developer's premises, in a controlled environment.
Beta testing
It is carried out by the end user of the software at one or more user sites. The developer is usually not on site. The user records the problems encountered in the test and reports it to the developer. The developer makes the final modification to the system and prepares to release the final Software.
Please answer again which is the most important step among unit testing, integration testing, system testing, acceptance testing, and regression testing.
These test steps are used to test the software in different stages of software development. I think the system test to test the complete function of the software is very important, because at this time the unit test and integration test have been completed, and all functions of the software can be tested. Covering all the combined components of the system is a test for the entire product system, which can verify whether the system meets the definition of requirements and specifications, so I think system testing is very important.
Please also answer the difference between integration testing and system testing, and what are their main application scenarios?
Differences:
1. The sequence of planning and use case preparation: From the perspective of the V model, system test plans and use cases must be formulated in the requirements phase. When HLD is used for integration test plans and use cases, some companies have different specific practices, but the sequence It must be the system test planning use case first, and then the integration.
2. Granularity of use cases: System test cases are relatively close to user acceptance test cases. Integration test cases are more detailed than system test cases, and the interface part should be written with emphasis. After all, each module or subsystem must be integrated.
3. The sequence of performing the test: first perform the integration test, and then do the system test after the problems found in the integration test are fixed.
Application scenarios:
Integration test: After the unit test is completed, the joint debugging test of each module; focus on whether the interface of each module is consistent, whether the data flow and control flow between each module realize its function according to the design, and verify the correctness of the result, etc.; can be The integration test of the entire product can also be the integration test of large modules; the integration test is mainly to test the internal structure of the program, especially the interface between the programs. Integration testing requires relatively high scripting ability of testers. The test method generally selects a combination of black box testing and white box testing.
System test: A comprehensive test of the entire product, including both the confirmatory test of each module (verify the correctness of the first two phases of testing) and functionality (the product is submitted to the user's function) test, as well as the robustness of the entire product , Safety, maintainability and various performance parameter tests. The system test tests whether the functions mentioned in the "Requirements Specification" of the software are omitted and whether they are implemented correctly. Do the system test strictly in accordance with the "Requirement Specification" and use it as the standard. The test method generally uses the black box test method.
Conclusion
Many people are fully prepared before going to the interview. From the interview, you can actually see that the current company has a certain reference value for the interviewer's knowledge system requirements. Interested friends can refer to it.
A copy of the information is prepared here, all organized into document notes.
Friends who want me to organize this complete set of "Python Software Test Automation Interview Questions + Resume Writing of Dachang" can click here to download and receive the secret code CSDN
Follow, don’t get lost, if it helps, remember to like and support!