Software Test Question 1

I. Judging incorrect answers
1. testing is a part of debugging)
2. The purpose of software testing is to identify as many Software defects as possible. (√)
3. The probability of hiding errors in the program is proportional to the number of detected errors (√)
4. Beta testing is a type of acceptance testing. (√)
5. Testers should adhere to the principle and will not pass the defect after it is not repaired. (√)
6. The tester does not need to submit any artifacts before project initiation. (Bytes)
7. About 80% of Software defects can be found in unit tests. (√)
8. The purpose of the test is to find errors in the software. (√)
9. Code review is to check whether the source code meets the requirements of the module design. (√)
10. Bottom-up integration requires the tester to write the driver. (√)
Ii. multiple choice questions
1. The purpose of implementing defect tracking is: (ABCD)
A. Software quality cannot be controlled. B. problems cannot be quantified. C. repeated problems are generated in succession.
D. The problem-solving knowledge cannot be retained E. The defects can be solved.
F. Complete closed-loop handling of problems
2. Purpose of using software testing tools: (ABCDF)
A. Help test to find Problem B. Assist in problem diagnosis C. Save test time
D. Increase Bug discovery rate E. better control of defects and improve software quality
F. Better assistance to developers
3. The purpose of preparing the test plan is: (ABC)
A. Make the test work run smoothly. B. Make the communication between project participants more comfortable.
C. Make the test work more systematic D. Software Engineering and software process needs
E. software process standardization requirements F. Control Software Quality
4. select the option that belongs to the black box testing method (B)
A. Test Case coverage B. Input coverage C. Output coverage
D. Branch overwrite E. Statement overwrite F. Condition Overwrite
5. Test results can be divided into (ABC)
A. Construction Test B. System Test C. Special Test
D. Unit Test E. Component Test F. Integration Test
6. The importance of software quality management is as follows :()
A. Maintain cost reduction B. Legal requirements C. Market Competition needs
D. Quality standardization trend E. Software Engineering Requirements F. Part of the CMM process
G. Facilitate further communication with the customer to lay a solid foundation for future implementation
7. in GB/T17544, the software package quality requirements include three parts: product description requirements, (A), procedure and data requirements.
A. User Documentation requirements B. system functional requirements
C. design requirements D. Software Configuration Requirements
8. The four stages of a typical waterfall model are: (ABCD)
A. Analysis B. Design C. Coding
D. Test E. requirement survey F. Implementation
9. () can be used as a sign of the end of software testing.
A. A specific test case is used. B. The error intensity curve drops to A predetermined level.
C. Check the number of errors. D. test according to the time specified in the test plan.
10. There are many causes of Software defects, and A-D is the possible cause. The main causes include (ABCD ).
A. The software requirement specification is not comprehensive, incomplete, inaccurate, and often changed.
B. Software Design Specification
C. Software Operator level
D. Developers cannot understand the requirement specification and lack of communication.
Iii. Glossary
1. Beta testing: Beta testing is performed from the user's perspective and is performed by multiple users of the software in the actual use environment of one or more users. It is a field application of software in a software environment that cannot be controlled by developers.
2. Load Testing: load testing is a process that analyzes software applications and supporting architectures to simulate the use of real environments to determine acceptable performance.
3. Software Testing activity life cycle: refers to the several phases of introducing program errors, detecting errors through testing, and clearing program errors from the process of entering the test to exit the test.
4. Improved sandwich integration: uses a high degree of parallelism to make up for the disadvantages of sandwich integration that cannot fully test the middle layer. However, the selection of the intermediate layer may increase the workload of the driver module and the pile module design.
5. The driver module is equivalent to the main program of the tested module. It receives test data, transmits the data to the tested module, and then outputs the actual test results.
Iv. Short answer
How should we classify software defects?
Fatal: fatal errors that cause system or application crashes, crashes, system suspension, data loss, and complete loss of main functions.
Serious: a serious error indicates that the function or feature is not implemented, the main function is partially lost, the secondary function is completely lost, or a fatal error statement.
General: Not very serious errors. Although such software defects do not affect the basic use of the system, they do not implement functions well and fail to achieve the expected results. If secondary functions are lost, the prompt information is inaccurate, the user interface is poor, and the operation time is long.
Minor: some minor issues have almost no impact on functions, and products and attributes can still be used, such as some typos and unordered text.
Phase review and peer review.
Peer review is an important and effective engineering method. This method can be called in software product engineering by means of root review, structured lookup, or some other academic review methods. The goal is to remove defects in software work early and efficiently. The inevitable result is to enhance understanding of software work products and preventive defects.
The phase review is a formal review of the progress, quality of completion, and problems in each phase of the software engineering based on the standards, specifications, and plans selected and formulated during the demand analysis phase, ensure that the process plan is implemented in compliance with standards and specifications, and then generate a report. When a problem is discovered, it is necessary to seek the principle of gradual solution, notify the relevant personnel of the handling result, record the solution process and results for future improvement important reference materials.
Both of them are important content related to software quality management and assurance. They complement each other and are indispensable.
Which stage of software testing does security testing belong? The concept of security testing and the main indicators used to judge system security performance are also elaborated.
Is a type of system testing,
Security Testing is to verify whether the protection mechanism in the system can defend against intruders. Security Testing testers need to take different intrusion methods to attack the system's security mechanisms during the testing activities, and do their best to obtain confidential information in the system.
System security performance indicator: Effectiveness: percentage of the time that the strict security performance takes to start the entire system. Survivability: When an error occurs, the system's support for emergency operations, the ability to remedy the error and restore it to normal operations, that is, the system's ability to resist setbacks. Accuracy: it measures the accuracy of system security control and determines the number, frequency, and severity of errors. Response time: the speed at which the system responds when an error occurs. a secure system must have a fast response speed. Throughput: the peak value and average value of user and service requests.
What are the main unit test strategies? And try to describe these policies?
There are three main unit test strategies:
1. top-down unit test strategy: the module called from the top layer is made into a pile module. For the second layer test, the driver module is used for the units tested above, and so on, until all unit tests are completed.
2. bottom-up unit test policy: first, test the bottom-layer module called by the module, and simulate the module that calls the module as the driver module. Secondly, perform unit test on the previous module, use the tested modules as the pile module, and so on until all unit tests are completed.
3. Isolated unit test strategy: the relationship between each module and other modules is not required. The pile module and the driving module are designed separately for each module to test all unit modules one by one.
What are the criteria for the end of the test?