1. Which of the following combinations correctly describes a valid approach to component testing:
i) Functional testing of the component in isolation.
ii) Structure-based testing of the code without recording incidents.
iii) Automated tests that are run until the component passes.
iv) Functional testing of the interfaces between modules.
i) Functional testing of the component in isolation.
ii) Structure-based testing of the code without recording incidents.
iii) Automated tests that are run until the component passes.
iv) Functional testing of the interfaces between modules.
A. i and ii.
B. I, ii and iii
C. iii.
D. ii and iv
2. Which of the following is a purpose of the review planning phase?
A. Log defects.
B. Explain the documents to the participants.
C. Gather metrics.
D. Allocate the individual roles.
3. A defect arrival rate curve:
A. Shows the number of newly discovered defects per unit time
B. Shows the number of open defects per unit time.
C. Shows the cumulative total number of defects found up to this time.
D. Any of these, depending on the company.
4. Which is the best definition of complete testing:
A. You have discovered every bug in the program.
B. You have tested every statement, branch, and combination of branches in the program.
C. You have completed every test in the test plan.
D. You have reached the scheduled ship date.
5. Complete statement and branch coverage means:
A. That you have tested every statement in the program.
B. That you have tested every statement and every branch in the program.
C. That you have tested every IF statement in the program.
D. That you have tested every combination of values of IF statements in the program
6. There are several risks of managing your project's schedule with a statistical reliability model. These include (choose one or more of the following):
A. Testers spend more energy early in the product trying to find bugs than preparing to do the rest of the project's work more efficiently
B. Managers might not realize that the testing effort is ineffective, late in the project, because they expect a low rate of bug finding, so the low rate achieved doesn't alarm them.
C. It can increase the end-of-project pressure on testers to not find bugs, or to not report bugs.
D. All of the above
7. Typical defects that are easier to find in reviews than in dynamic testing are:
A. Deviations from standards,
B. Requirement defects,
C. Design defects,
D. Insufficient maintainability and incorrect interface specifications.
E. All of the above.
8. Reviews, static analysis and dynamic testing have the same objective
A. Identifying defects.
B. Fixing defects.
C. A. and B
D. None of the above
9. We can achieve complete statement coverage but still miss bugs because:
A. The failure occurs only if you reach a statement taking the TRUE branch of an IF statement, and you got to the statement with a test that passed through the FALSE branch.
B. The failure depends on the program's inability to handle specific data values, rather than on the program's flow of control.
C. We are not required to test code that customers are unlikely to execute.
D. All of the above
10. Measurement dysfunction is a problem because:
A. Even though the numbers you look at appear better, to achieve these numbers, people are doing other aspects of their work much less well.
B. We don't know how to measure a variable (our measurement is dysfunctional) and so we don't know how to interpret the result.
C. You are measuring the wrong thing and thus reaching the wrong conclusions.
D. All of the above.
11. Important consequences of the impossibility of complete testing are (Choose one or more answers):
A. We can never be certain that the program is bug free.
B. We have no definite stopping point for testing, which makes it easier for some managers to argue for very little testing.
C. We have no easy answer for what testing tasks should always be required, because every task takes time that could be spent on other high importance tasks.
D. All of the above.
12. Poor software characteristics are
A. Only Project risks
B. Only Product risks
C. Project risks and Product risks
D. Project risks or Product risks
13. System testing should investigate
A. Non-functional requirements only not Functional requirements
B. Functional requirements only not non-functional requirements
C. Non-functional requirements and Functional requirements
D. Non-functional requirements or Functional requirements
14. Contract and regulation testing is a part of
A. System testing
B. Acceptance testing
C. Integration testing
D. Smoke testing
15. Find the correct flow of the phases of a formal review
A. Planning, Review meeting, Rework, Kick off
B. Planning, Individual preparation, Kick off, Rework
C. Planning, Review meeting, Rework, Follow up
D. Planning, Individual preparation, Follow up, Kick off
16. Which is not the testing objectives
A. Finding defects
B. Gaining confidence about the level of quality and providing information
C. Preventing defects.
D. Debugging defects
17. Maintenance releases and technical assistance centers are examples of which of the following costs of quality?
A. External failure
B. Internal failure
C. Appraisal
D. Prevention
18. Which is not the project risks
A. Supplier issues
B. Organization factors
C. Technical issues
D. Error-prone software delivered
19. Bug life cycle
A. Open, Assigned, Fixed, Closed
B. Open, Fixed, Assigned, Closed
C. Assigned, Open, Closed, Fixed
D. Assigned, Open, Fixed, Closed
20. Who is responsible for document all the issues, problems and open point that were identified during the review meeting
A. Moderator
B. Scribe
C. Reviewers
D. Author
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| B | D | A | A | B | D | E | A | A,B | A |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| D | B | C | B | C | D | A | D | A | B |
No comments:
Post a Comment