Software testing and quality control knowledge point examination
Length of examination: 120 minutes full: 100 minutes
I. Single-choice topics (10 total, 2 points each, 20 points)
1. Which of the following is not part of the black box test method in the software test
A. Equivalent classification
B. Decision sheet testing
C. Code coverage analysis
Analysis of boundary values
2. What type of model is cmi (capacity maturity model integration) in the software quality model
A. Product quality model
B. Modelling organizational process maturity
C. Modelling for test case design
D. Methodology for software development
3. Which of the following test types are non-functional tests
Module testing
Integrated testing
C. Performance testing
D. System testing
4. In the course of the testing, a programme was found to collapse when entering a particular data, and what is the extent of the defect
A. Minor deficiencies
General shortcomings
C. Serious deficiencies
D. Critical deficiencies
5. Which of the following tests applies to verify whether the software meets user needs
A. White box tests
B. Black box testing
C. Grey box test
D. Return testing
6. What tools are used primarily for automated testing in software tests
A. Jmeter
B. Selenium
C. Loadrunner
D. Postman
7. Which stage of the software development life cycle was the first to test intervention
A. Needs analysis
Design phase
C. Encoding phase
D. Test phase
8. Which of the following test methods is static
Module testing
Integrated testing
C. Code review
D. System testing
9. What stages are usually included in the life cycle of software deficiencies
A. Discovery, reporting, repair, validation
B. Discovery, analysis, repair, closure
C. Submission, distribution, repair, validation
Discovery, tracking, repair, closure
10. In the design of test cases, which methods are used primarily to reduce the number of test cases
A. Equivalent classification
B. Decision sheet testing
C. Causes and consequences
D. Scenario approach
Ii. Filling in blanks (10 total, 2 points each, 20 points total)
The purpose of software testing is to ensure that the software is and 。
The core idea of black box testing is 。
The classification of software deficiencies typically includes , and 。
The design principles for testing examples include , and 。
In the software quality model, iso/iec25000 is 。
The main advantages of automated testing are and 。
The five basic principles for software testing include: , , and 。
Elements of the test examples usually include , , and 。
The software deficiencies report should include , , and 。
The main indicators for performance testing are , and 。
Iii. Judicial questions (10 total, 2 points per issue, 20 points in total)
1. The black box test does not require an understanding of the internal structure of the procedure. (grunts)
The white box test applies to verify whether the software meets user needs. (x)
3. The life cycle of software deficiencies typically includes four stages of detection, reporting, repair and validation. (grunts)
4. The design of the test case need not consider user scenarios. (x)
Cmmi is a product assessment model in the software quality model. (x)
Automation testing can increase the efficiency of testing but cannot be a complete substitute for manual testing. (grunts)
The purpose of the software tests is to detect as many deficiencies as possible. (x)
8. Static tests detect logical errors in the code. (grunts)
9. The design of test examples needs to take into account equivalent categories and boundary values. (grunts)
Performance testing only focuses on software response times. (x)
Iv. Brief answers (total of 3 4 points each, total 12 points)
1. Briefly describe the difference between black and white box tests。
2. Explain the life cycle of software deficiencies and the main work of their phases。
3. List three common test case design methods and outline their characteristics。
V. Application questions (total of 2 9 points each, total 18 points)
1. Assuming that a software system requires user login, design a test example that includes test purposes, test steps, expected results and actual results。
In the course of testing, a software system found a flaw, described as " when special characters are entered, the system collapses". Please analyse the extent of this deficiency and give recommendations for repair and validation methods。
[standard answer and resolution]
I. Single topics
1. C
Parsing: the black box test method includes equal price classing, decision sheet testing, boundary value analysis, etc., while the code coverage analysis is the white box test method。
2. B
Analysis: cmmi (capacity maturity model integration) is an organizational process maturity model used to assess and improve the quality of the software development process。
3. C
Parsing: non-functional tests include performance tests, safety tests, serviceability tests, etc., while unit tests, integration tests and system tests are functional tests。
4. C
Parsing: the program crash is a serious defect that affects the proper running of the software。
5. B
Parsing: blackbox testing is primarily used to verify whether the software meets user needs and does not require an understanding of the internal structure of the program。
6. B
Parsing: selenium is a commonly used automated testing tool, mainly for web applications。
7. A
Parsing: the first stage of test intervention is the needs analysis phase, where testing can be done, for example, through a needs assessment。
8. C
Parsing: code review is a static test, a manual examination of the code identifies defects, while unit testing, integration testing and system testing are dynamic tests。
9. C
Analysis: the life cycle of software defects usually includes four stages of submission, distribution, repair and validation。
10. A
Parsing: equivalent classification methods reduce the number of test cases and cover the entire equivalent category by selecting representative examples。
Ii. Filling in the question
Correctness, reliability
2. No need to understand the internal structure of the procedure
3. Minor, general, serious defects
4. Feasibility, readability, viability
5. Software quality standards
6. Increasing efficiency and reducing human costs
7. Tests should cover all needs, test cases should be as simple as possible, test cases should be repeated, test cases should be automated and test cases should be validated
8. Test case numbers, test steps, expected results, actual results
9. Description of deficiencies, severity of deficiencies, environment where deficiencies occurred, recommendations for repairs
Response time, throughput, resource utilization
Iii. Questions of judgement
1. √
2. X
3. √
4. X
5. ×
6. √
7. ×
8. √
9. Phew
X
Iv. Brief answers
1. Distinction between black and white box tests:
- the black box test does not require an understanding of the internal structure of the program, the functionality of the verification software by entering and exporting; the white box test requires an understanding of the internal structure of the program, which is tested by means of code coverage, etc。
- black box tests are applied to verify whether the software meets user needs, and white box tests are used to detect logical errors in the code。
2. The life cycle of software deficiencies and their main stages:
- submitted: the tester identifies the deficiencies and submits them to the development team。
- distribution: development teams are assigned to the respective developers according to the severity and priority of the deficiencies。
- rehabilitation: rehabilitated by developers based on deficiencies reports。
- validation: testers verify whether the restored defects have been addressed。
Three commonly used test models and their characteristics:
- equivalent classification: by classifying input data into equivalent categories, selecting representative examples for testing and reducing the number of test cases。
- boundary value analysis: potential defects are detected by testing the boundary values of the input data。
- decision sheet testing: the relationship between input and output is described in the decision sheet, and examples of tests are designed。
V. Applications
1. Test case design:
- purpose of the test: verify the validity of the user login function。
- test steps:
1. Enter the correct user name and password to verify successful login。
Enter the wrong user name and password to verify whether or not to send the wrong information。
Enter an empty user name or password to verify whether or not to send the wrong message。
Enter a special character as a user name or password to verify whether the system has crashed or to signal error information。
- expected results:
1. Enter the correct user name and password and login is successful。
Enter the wrong user name and password and hint the wrong information。
3. Enter an empty user name or password to signal the error。
4. Enter a special character, the system should not collapse and hint for the wrong information。
- actual results: to be completed after testing。
2. Recommendations for gap analysis and repair:
- severity: serious defects affecting the proper functioning of the software。
- recommendations for rehabilitation:
1. Developers check input validation logic to ensure that special characters are correctly processed。
2. Increase irregular capture mechanisms to prevent system collapse。
- validation methods:
Re-entry of special characters to verify whether the system has collapsed。
2. Whether or not the certification system is sending false information。
3. Validation system functioning。
