Test 1

I. Right and wrong issues

1. The purpose of software testing is to find out as many software defects as possible. (Y)

2.Beta test is a kind of acceptance test. (Y)

3. The acceptance test shall be conducted by the end user. (noun)

4. Before the project is established, testers do not need to submit any artifacts. (Y)

5. Unit testing can find about 80% software defects. (Y)

6. Code review is to check whether the source code meets the requirements of module design. (noun)

7. Bottom-up integration requires testers to write drivers. (Y)

8. The load test is to verify the maximum capacity of the system under test. (noun)

9. Testers should stick to the principle and resolutely refuse to pass the defect until it is fixed. (noun)

10. Code reviewers are generally held by testers. (noun)

1 1. We can artificially keep the software from configuration problems. (noun)

12. The integration test plan is submitted at the end of the requirements analysis stage. (noun)

Second, multiple choices.

1. The passing standard of software acceptance test is: (ABCD)

A all the functions defined in the software requirements analysis specification have been realized and all the performance indicators meet the requirements.

B all the tested items have no residual 1 class, class 2 and class 3 errors.

C the project approval form, requirements analysis documents, design documents and codes are consistent.

D. the acceptance test workpiece has been completed.

2. Who needs to attend the software test plan review meeting? (ABCD)

A. Project manager

Director B.SQA

C. configuration owner

D. test group

3. The following description about alpha test is correct: (AD)

Alpha testing requires the participation of user representatives.

B.alpha testing does not require the participation of user representatives.

C.alpha test is a system test.

D.alpha test is a kind of acceptance test.

4. The responsibilities of the test designer are: (BC)

A. Make a test plan

B. Design test cases

C. Design test flow and script

D. evaluation and testing activities

5. The entry criteria for software implementation activities are: (ABC) A. Requirements artifacts have been baseline B. Detailed design artifacts have been baseline C. Architecture artifacts have been baseline D. Project phase results have been baseline.

Third, increase space.

1. Software acceptance test includes: formal acceptance test, alpha test and beta test.

2. System testing strategies include: functional testing, performance testing, reliability testing, load testing, usability testing, strength testing, safety testing, configuration testing, installation testing, uninstall testing, document testing, fault recovery testing, interface testing, capacity testing, compatibility testing, distribution testing and usability testing. (Some can be combined and written separately. Just write 15 to get full marks. )

3. The project documents that need to be referenced in designing the system test plan include: software test plan, software requirement artifacts and iteration plan. 4. There are two integration strategies for process-oriented systems: top-down and bottom-up.

Fourth, short answer.

1. Distinguish between stage review and peer review.

The purpose of peer review: to find errors in small-scale work products, as long as they are found;

Number of peer reviewers: 3-7, and they must be trained in peer review meetings. The content of peer review is guided by SQA: small documents.

The purpose of stage review: to review the correctness, feasibility and completeness of the stage work of the module. The number of stage reviewers is about 5, and the reviewers must be experts with system review qualifications. Stage review content: there are many contents, mainly focusing on the key points.

Stage review time: generally set at the time point of the critical path!

2. What is software testing?

The process of executing a program in order to find out the errors in the program.

3. Briefly describe the process of integration testing.

System integration testing mainly includes the following processes:

1. Construction confirmation process.

2. Patch confirmation process.

3. System integration test test group submission process.

4. Test case design process.

5. Test the coding process.

6. Error reporting process.

7. Weekly/biweekly construction process.

8. Peer-to-peer testing process.

9. Training process within the group.

4. How to test documents well

Read carefully, follow every step, check every number and try every example.

Check whether official document writing meets the purpose of official document writing.

Is the content complete and correct?

Is the content perfect?

Is the label correct?

5. There are several methods for white-box testing.

Generally speaking, it can be divided into static methods and dynamic methods.

Static: The key function is to check whether the representation and description of the software are consistent, without conflict and ambiguity.

Dynamic: statement coverage, decision coverage, condition coverage, decision condition coverage, condition combination coverage and path coverage.

6. Does the system test plan need peer approval? Why?

Yes, the system test plan is a key document in the project stage, so it needs to be reviewed.

The difference between 7.7. Alpha test and beta test

Alpha testing tests the application system when the system development is close to completion; There will still be some design changes after the test. This kind of testing is generally done by end users or other personnel, not by programs or testers.

Beta test: the test done when the development and testing are basically completed, and the final errors and problems need to be found before the final release. This kind of testing is generally done by end users or other people, not by programmers or testers.

8. Compare the differences among load test, capacity test and strength test.

Load test: the load and response time of the system under a certain workload. Strength test: under certain load conditions, the impact of continuous operation of the system for a long time span on the system performance.

Capacity test: the purpose of capacity test is to analyze the limit value of an indicator (such as the maximum number of concurrent users and the number of database records). By testing, the application characteristics of the software system can be reflected in advance, so that the system does not have any software faults or can maintain the normal operation of its main functions in its limit state. Capacity testing will also determine the maximum load or workload that the test object can continue to process in a given time. The purpose of capacity testing is to make the system bear excess data capacity to find out whether it can be handled correctly. Capacity test is data-oriented, and its purpose is to show that the system can handle the data capacity determined in the target.

9. What are the criteria for the end of the test?

Test all use cases.

The coverage rate is up to standard.

The defective rate reaches the standard.

Other indicators meet the quality standards.

10. Describe the life cycle of software testing activities?

The test cycle is divided into planning, design, implementation, execution and summary. These include:

Planning: Plan all activities in the whole test cycle, estimate workload and risk, arrange manpower and material resources, arrange progress, etc.

Design: complete the test plan and plan the test from the technical level;

Implementation: design test cases and test procedures;

Execution: execute the test cases according to the plans, schemes, use cases, procedures and other documents completed in the early stage.

Summary: Record the test results, conduct test analysis and complete the test report.

1 1. How to classify the defect level of software?

Grade a? Critical errors, including the following: 1. Illegal exit due to program crash; 2. Deadlock occurred in the database; 4. Misoperation leads to program interruption; 5. Functional error; 6. Wrong connection with the database; 7. Data communication error.

Class b? Critical errors, including the following: 1. Program error 2. Program interface error 3. Constraints such as incomplete database tables, business rules and default values.

Class c? General errors, including the following: 1. Error in operation interface (including whether the definition and meaning of column names in data window are consistent) 2. Error in printing content and format 3. Simple input restrictions are not placed in the foreground of control 4. Do not prompt to delete operation 5. There are too many empty fields in the database table.

Class d? Small error, including the following: 1. The interface is not standardized. 2. The description of the auxiliary instruction is unclear. 3. Input and output are not standardized. 4. Long-term operation will not prompt the user. 5. The text of the prompt window does not use industry terminology. 6. There is no obvious difference between the input area and the read-only area.

Class e? Test suggestion

Test 2

Right or wrong

1, software testing is to verify whether the software function is correctly realized and whether the activity of setting goals is completed, so the specific work of software testing begins in the later stage of software engineering. (elementary) (? )

2. Find a module with many errors, and there are still many errors in the module. ( ? ) (elementary)

3. Testers found a problem during the test. If the problem has little impact and can be modified by themselves, they should correct the problem immediately to speed up and improve the development process. ( ? ) (elementary)

4. Unit testing should usually be carried out first? Manual inspection? Then the white box method is the main method and the black box method is the auxiliary method for dynamic testing. ( ? ) (intermediate)

5. Functional testing is the main content of system testing. Check whether the function and performance of the system are the same as the requirement specification. ( ? ) (intermediate)

6. Software quality management means that QM consists of QA and QC, and software testing is the core work of QC. (? (advanced)

7. Software testing can only find errors, but it cannot guarantee that the tested software is error-free. (? )

8. Software is a program. (10)

9. As long as the test covers statements and branches, all errors in the program can be found. (10)

10, I 18N testing refers to making an international plan for the product, while L 10N testing refers to making changes to the software that meet local requirements. (? ) advanced

Multiple choice questions (2 points and 20 points for each question)

1, the importance of software quality management is: (ABCD) intermediate.

A, maintain and reduce costs B, legal requirements C, the needs of market competition

D, the trend of quality standardization E, the need of software engineering F, part of CMM process G, facilitating further communication with customers and laying a good foundation for later implementation.

2. According to the examination form, the examination can be divided into: (ABC) intermediate.

A, structural test B, system test C, special test D, unit test E, component test F and integration test

3. Select the option (ABC) that belongs to the black box test method.

A, test case coverage b, input coverage c, output coverage d, branch coverage e, sentence coverage f, and conditional coverage.

4. The purpose of writing the test plan is: (ABC) intermediate level.

A, make the test work smoothly; B, make the communication between project participants more comfortable; Make the test work more systematic; D, software engineering and software process requirements; E, the requirements of software process standardization; Control software quality.

5. There are four kinds of dependence: (ABCD) advanced.

A, start-end b, start-start c, end-start

D, End-End E, Start-Implement-End F, End-Review-Start

6. Software quality management (QM) should include quality assurance (QA) and quality control (QC). The following options belong to QC: (ABC) Advanced.

A, test B, track C, supervise

D, making plan E, requirement review F, and program code review

7. The purpose of defect tracking is: (ABCD) intermediate.

A, the software quality can't be controlled; B, the problem cannot be quantified; C, repeated problems occur one after another.

D, problem-solving knowledge can't be retained; E, defects can be solved; F, the problem can be completely closed-loop.

8. Purpose of using software testing tools: (ABC) Intermediate.

A, help the test find the problem b, help diagnose the problem c, and save the test time.

D, improve Bug detection rate e, better control defects, improve software quality f, and better assist developers.

9. The four stages of a typical waterfall model are: (ABCD) Advanced.

A, analysis B, design C, coding D, testing E, requirement research F, and implementation

10, PSP refers to personal software process, which is a self-improvement process and can be used in (a), (b) and (c) personal software working modes. elder

A, control B, management C, improvement D, high efficiency E, sufficiency F and suitability

essay question

1. What are the tasks of testers during software development? (Elementary) (5 points)

Answer: 1, ask for bugs.

2. Avoid defects in the software development process;

3. Measure the quality of software;

4. Pay attention to the needs of users.

The overall goal is to ensure the quality of the software.

2. What did the software defect (or Bug) record contain in your past work? How to submit high-quality software defect (Bug) records? (Elementary) (6 points)

A: A Bug record should basically include: number, module to which the Bug belongs, Bug description, Bug level, discovery date, discoverer, modification date, modifier, modification method, regression result, etc. In order to find bugs effectively, we need to design efficient test cases with reference to the preliminary documents such as requirements and detailed design, and then strictly implement the test cases, fully confirm and affirm the problems found, and then release them to the outside world, thus improving the quality of submitting bugs.

3. Interface testing problems and design problems. Please find out the problems in the following interface and list them separately; Use any black-box test method to design the test case of this login form. (Intermediate) (6 points)

Answer: 1. The title bar of the form is blank and no title is given.

2. The fonts of the user name and password control are inconsistent and not aligned.

3. The sizes of the text boxes are inconsistent.

4. The sizes of the Confirm and Cancel button controls are inconsistent.

4. Black box testing and white box testing are two basic methods of software testing. Please explain their advantages and disadvantages respectively! (Intermediate) (5 points)

A: The advantages of black box testing are:

1) is relatively simple and does not need to know the internal code and implementation of the program;

2) It has nothing to do with the internal implementation of the software;

3) From the user's point of view, it is easy to know which functions users will use and what problems they will encounter;

4) Based on the software development documents, we can also know what functions the software has realized in the documents;

5) It is more convenient to do software automated testing.

The disadvantages of black box testing are:

1) cannot cover all codes, and the coverage rate is low, which can only reach 30% of the total codes;

2) The reusability of automated testing is low.

The advantages of white box testing are:

Help software testers to increase code coverage, improve code quality and find hidden problems in the code.

The disadvantages of white box testing are:

1) There will be many different paths for the program to run, so it is impossible to test all the paths;

2) Testing is based on code, which can only test whether the developer has done it right, and it is impossible to know whether the design is correct, and some functional requirements may be missed;

3) When the system is huge, the test overhead will be very large.

5. According to your own understanding, answer what software testing is and what stages software testing is divided into. (Elementary) (5 points)

A: Software testing is the process of running software to find software errors. A successful test means that the test has found errors that have not been found so far.

Software testing is generally divided into unit testing, integration testing and system testing.

6. According to your own understanding of what a test case is and the test process, what aspects should be considered when designing a test case? (Intermediate) (10)

A: In a narrow sense, a test case is a set of data used by testers to test a certain feature or feature combination of the software under test. This set of data may be a set of actual data obtained from users, or a set of data specially designed by testers to test some functions of the software.

A test specification is a document that describes the design method, test method, test tool, test environment and test data in detail. It can also include a series of operation steps, which can apply a test case or a set of test cases to the software under test to complete a test.

The design of test cases should be considered from the following aspects: boundary value, equivalence class division, valid/invalid value, etc.

7. What is software quality assurance? What is the relationship between software quality assurance personnel and developers? (Advanced) (10)

A: Software quality assurance is to ensure the quality of software products by ensuring the quality of software processes. Software quality assurance personnel and developers have strict independence in management. Administrators of two groups cannot manage the other group beyond their authority, but they can report problems in software development to higher-level managers.

;