Software Test Question 3

Question 3:

I. Answer questions (1 point, 12 points per question, correct √, incorrect answer)
1. The purpose of software testing is to identify as many Software defects as possible. ()
The purpose of software testing is to discover defects in the software. In this sense, the above conclusion is correct. Many people think that software testing can ensure the quality of software. In fact, this idea is wrong. Testing is only a role in software quality control, and its activities cannot achieve the effect of software quality assurance. Therefore, do not think that if a company has software testers, the product quality will be better.
2. Beta testing is a type of acceptance testing. (Bytes)
Beat test and acceptance test are two different tests. The purpose of the acceptance test is to find "unfulfilled requirements" and evaluate "suitable for use". This test is not intended to detect defects. Beta testing is a test that simulates real use environments to discover defects. Therefore, the relationship between the two is non-inclusive.
3. the acceptance test is implemented by the end user. ()
The purpose and goal of the acceptance test are described above, so the acceptance test is also implemented by internal personnel of the software production enterprise. For example, the product manager. When the software appears as a project, the acceptance test is implemented by the end user for a long time. However, there will be more internal acceptance tests for software in the form of products.

4. The tester does not need to submit any artifacts before project initiation. ()
It should be said that there is no clear answer to this question. before the project is established, whether the tester wants to record some preparation work in the form of a work piece is completely dependent on the requirements of the enterprise's software development process. At the same time, the necessary conditions for different enterprises to be achieved before project establishment are also quite different. It should be said that this question is not very good. If you are a testing engineer of this enterprise, you should have a clear answer.

5. About 80% of Software defects can be found in unit tests. ()
There is no standard answer to this question. Because of the data source and its statistical method, the sample does not have an industrial standard. Such data is not authoritative. Here I can say a simple example. There is no complicated unit test when developing web pages using scripting languages such as ASP and php. Whether such a digital application makes sense in website development is still debatable. Therefore, this question is difficult and there is no clear answer.

6. Code review is to check whether the source code meets the requirements of the module design. ()
Code review is a static technique. In this sense, code review must work with other dynamic testing techniques to check whether the Code meets the design requirements.

7. Bottom-up integration requires the tester to write the driver. ()
You can see the integration tests of top-down and down-top to get a clear answer to this question. Here we need to know what is a driver test program and what is a pile program. If there are a large number of integrated components and there are multiple link levels, no matter what type of integration test. Both drivers and piling programs need to be developed.

8. Server Load balancer is used to verify the maximum capacity of the system to be tested. ()
I have a detailed explanation of the load testing and stress testing posts in the forum. You can take a look and get the correct answer.

9. testers must adhere to the principle and will not pass the defect after it is repaired. ()
Likewise, there is no correct answer to this question. Whether the defect is repaired requires the tester's opinion, but the tester's opinion is not decisive. So it depends on how much power a company gives testers.

10. The Code reviewer is generally a tester. ()
If the tester has this level, you can certainly participate. However, most companies do not involve common Testers in code reviews.

11. We can manually prevent the software from being configured. ()
First, let's figure out what configuration management is and what software configuration is. From this question, we can't see whether configuration management in key projects is pure software configuration. However, it is certain that, in whatever circumstances, the answer is no.

12. The integration test plan is submitted at the end of the requirement analysis phase. ()
The integration test plan can be started after the developer completes the software integration plan. Therefore, it is unrealistic to submit requests after the demand analysis phase. It should be done before coding after the software design phase.
2. multiple choice questions (2 points per question, 10 points)

1. The criteria for passing the Software acceptance test are :()
A. All functions defined in the Software Requirement Analysis specification have been fully implemented, and all performance indicators have met the requirements.
B. No errors of level 1, level 2, or level 3 remain in all test items.
C. The project approval form, requirement analysis documents, design documents and codes are consistent.
D. Complete Acceptance Test artifacts.

To answer this question, you must be an employee of the company. The purpose and goal of the acceptance test are described above. One is that the requirements must be met, and the other is that the software is suitable for use. In this way, we can meet these two general standards. Of course, some software companies will make some adjustments to the acceptance test standards.

2. Who are required for the software test plan review? ()
A. Project Manager
B. SQA owner
C. Configuration owner
D. Test Group

All the above four roles must be involved.

3. Which of the following statements about alpha testing are true :()
A. the alpha test requires the participation of user representatives.
B. user representatives are not required for alpha testing.
C. alpha testing is a type of system testing.
D. alpha testing is a type of acceptance testing.

First, you need to know that alpha testing is a system-level test that is carried out in a controlled environment. Users must participate directly. So the answer should be AD.
4. Test the responsibilities of the designer :()
A. Develop A test plan
B. Design Test Cases
C. design the test process and script
D. Evaluate test activities
The reasonable answer is BC, which also depends on how software companies define their responsibilities for such personnel.
5. the entry criteria for software implementation activities are :()
A. Requirement artifacts have been baseline-based
B. Detailed design artifacts have been baseline-based
C. Architecture artifacts have been baseline-based
D. The results of the project phase have been baseline-based.

First, you need to know what a baseline is. This is an important concept in Software Configuration Management. Work products must be included in a baseline. So it is inevitable to select ABC. Whether to choose D depends on the enterprise's own standards.
Fill in blank questions (1 point for each blank question, 24 points)
1. Software acceptance tests include ___, ___, and.
Software acceptance testing includes formal acceptance testing, alpha testing, and beta testing.
2. system testing strategies include functional testing, usability testing ,,,,,,,,
, And so on.
There are many policies for system testing, I know performance testing, load testing, intensity testing, usability testing, security testing, configuration testing, installation testing, document testing, fault recovery testing, user interface testing, recovery testing, distribution test and availability test...
3. The project documents that need to be referenced to design the system test plan include, and the iteration plan.
Project documents to be referenced in the design of system test plans include software test plans, software requirement artifacts, and iteration plans.
4. process-oriented systems adopt two integration strategies: ___ and.
5. There are five steps to write test cases by drawing the causal diagram: ___, and converting the causal diagram into a state chart.
The basic steps to generate a test case using the causal indicator are as follows:
§ The reason (that is, the equivalence class of the input condition or the input condition) and result (that is, the output condition) in the description of the Analysis Software specification ), and assign an identifier to each reason and result.
§ Analyze the semantics in the description of the Software specification and find out the relationship between the cause and the result. What is the relationship between the cause and the cause? Based on these relationships, draw the causal coefficient.
§ The combination between the cause and the result may not be possible due to syntax or environmental restrictions. To indicate these special circumstances, use some marks to indicate constraints or restrictions on the reason.
§ Convert the cause into a discriminant table.
§ Use each column of the decision table as a basis to design test cases.