Answer to "software testing" exercise: Chapter 1

Chapter one

One 、 Completion

1. Software from “ born ” To “ Extinction ” The process is called _____. Software life cycle

2. The early linear development model is called _____ Development model . The waterfall

3. The development model of risk analysis is _____ Development model . screw

4. ISO/IEC 9126:1991 The quality models proposed in the standard include _____、_____、_____、_____、、_____6 Big characteristic .

Functionality 、 reliability 、 Usability 、 efficiency 、 Maintainability 、 Portability .

5. According to the severity of defects, defects can be divided into _____、_____、_____、_____.

serious 、 commonly 、 secondary 、 Suggest .

6. The test to verify whether the software unit meets the software requirements and design is called _____. unit testing

7. The logical structure of the program 、 The test of path and running process is called _____. White box testing

8. There is a test model , Testing and development are carried out in parallel , This test model is called _____ Model .W

Two 、 Judgment questions

1. Now the popular software development model is spiral model .（　）×  Agile model

2. Software defects are caused by the limited level of developers , A very good programmer can develop zero defect Software .（　）× 

3. Software defects exist in the program code .（　）×     

Software defects can exist in software requirements analysis 、 Architecture design 、 Programming development and other stages .

4. Software testing is to prove that the program is correct .（　）√    

5. software test H The model incorporates exploratory testing .（　）×    X The model incorporates the exploration model

6. Software testing should invest as much energy as possible to achieve 100% Coverage of .（　）×      

3、 ... and 、 Single topic selection

1. In the following options , Which is not a software development model ？（　）

A. V Model B. The model is fast C. Spiral model D. Agile model

2. In the following options , Which is not a factor affecting software quality ？（　）

A. Demand is vague B. Lack of standardized document guidance C. Use new technology D. Limited developer Technology

3. Which of the following is not the cause of software defects ？（　）

A. Unclear needs B. Poor test case design C. The software structure is complex D. The project cycle is short

4. About software defects , The mistake in the following statement is （　）.

A. Software defect is a kind of defect in software （ Including programs and documents ） Problems that affect the normal operation of the software .

B. According to the priority of defects, defects can be divided into immediate solutions 、 High priority 、 The normal line 、 Low priority

C. There is a unified template for defect reporting , The template is IEEE 729—1983 To formulate the

D. Each defect has a unique number , This is the identification of the defect

Defect report form every company has a set of templates

5. About software testing , The mistake in the following statement is （　）.

A. In early software development , Testing is equivalent to debugging

B. Software testing is the process of running or measuring a system by manual or automatic means

C. The purpose of the software is to find out whether it meets the requirements or the actual test results

D. Software testing and software development are two independent systems 、 The process of separation

6. Which of the following is not a principle of software testing ？（　）

A. Testing should be based on customer requirements B. The later the test, the better

C. Exhaustive testing is not allowed D. Software testing should follow GoodEnough principle

Four 、 Short answer

1. Please briefly describe the processing flow of software defects .

The software defect handling process is ： Submit → Distribute → confirm → Handle → Retest → close

(1） Submit : After the testers found the defect , Submit defects to test team leader .

(2） Distribute : After the test team leader receives the defects submitted by the test team members , Hand it over to the developers .

(3） confirm : After the developer receives the transferred defect , We will discuss with the team and even the tester , Determine whether the defect is a defect .

(4） Refuse : If after consultation , If the defect is not a real defect, it will be rejected , Close defects . If after consultation , Make sure it's a real flaw , It can be handled immediately or postponed according to the severity or priority of defects .

(5） Handle : Developers modify defects .

(6） Retest : After the developers fix the defect , The tester retested ( regression testing ), Check if the defect has actually been modified . If not properly modified , Then submit the defect again .

(7) close : After the tester performs the regression test , If the defect has been corrected correctly , Then close the defect , The whole defect treatment is completed .

2. Please briefly describe the basic process of software testing .

The basic process of software testing is :

Analyze test requirements → Make a test plan → Design test cases → Perform the test → Write test report .

(1） Analyze test requirements

Testers need to analyze software requirements before making test plans , In order to have a clear understanding of the software products to be developed , So as to clarify the test object, the scope and focus of the test work . Some test data can also be obtained when analyzing requirements , As the basic basis of test plan , Lay a good foundation for subsequent tests .

(2） Make a test plan

The test plan is the navigation chart of the whole test work , But it is not immutable , As the project progresses or needs change , Test plans are constantly changing , Therefore, the formulation of test plan is constantly adjusted with the development of the project 、 The process of gradual improvement .

The following work arrangements shall be made for the test plan .

Determine test scope : Identify which objects need to be tested , Which objects are not to be tested .

Develop test strategy : Test strategy is the most important part of test plan , It prioritizes the content to be tested , And determine the test focus . According to the characteristics and test types of test modules ( Such as function test 、 Performance testing ） Select test environment and test method （ Such as manual test 、 automated testing ）.

Schedule test resources : Pass the test 、 Time 、 Workload and other factors affect the reasonable arrangement of test resources , Including personnel allocation 、 Tool configuration, etc .

Schedule the test : According to the software development plan 、 Schedule the testing work according to the overall product plan , At the same time, we should also consider the changes of each part of the work . When scheduling work , It is better to reserve a buffer time between various test work to deal with plan changes .

Estimate the test risk : List the uncertainties that may occur during the test work , And formulate countermeasures .

(3） Design test cases

The test case (Test Case） It refers to a detailed test plan , Including test environment 、 testing procedure 、 Test data and expected results . The principle of test case writing is to achieve the maximum test coverage with the least test cases as far as possible . The common design methods of test cases include equivalence class division method 、 Boundary value analysis 、 Cause and effect diagram and decision table 、 Orthogonal experiment 、 Logical covering method, etc .

(4） Perform the test

Test execution is the process of executing tests according to test cases , This is the main activity stage of testers . The test shall be executed according to the priority of test cases .

Testers need to complete the execution of all test cases , Every test case may find many defects , The tester shall make test records and tracking , Measure the quality of defects and prepare defect reports .

When the submitted defect is modified by the developer , Testers need to do regression testing . If the system has defect immunity to the test case , Testers need to write new test cases .

(5) Write test report

The test report is a summary of test activities , Summarize the project testing process , Make statistics on the test data , Objectively evaluate the test quality of the project .

A complete test report must include the following points .

introduction : Describe the purpose of the test report 、 Explanation of professional terms and references in the report . Test summary : Introduce the background of the project 、 Test time 、 Information such as test location and tester .

Test content and implementation : Describe the version of this test module 、 Test type , The test case design method used and the test pass coverage , Provide the evaluation conclusion of the test execution process through the passing of the test , And give suggestions for improvement of test execution activities , It can be used for reference in subsequent test implementation activities .

Defect statistics and analysis : Count the number of defects found in this test 、 Type, etc , Analyze the causes of defects and give suggestions such as avoidance measures , At the same time, residual defects and unresolved problems shall be recorded .

Test conclusion and suggestion : From demand compliance 、 Functional correctness 、 The overall evaluation of version quality is carried out from multiple dimensions such as performance indicators , Give specific conclusions about whether they are available .

The data in the test report is true , Every conclusion is based on Evaluation , It can't be subjective .