40 Question quiz 23 (921-960)

A. To verify the success of corrective actions.

B. To prevent a task from being incorrectly considered completed.

C. To ensure that defects have not been introduced by a modification.

D. To motivate better unit testing by the programmers.

A. 2, 3 and 4

B. 2 and 4

C. 3 and 4

D. 1, 2 and 3

A. Formal inspection

B. Dynamic testing

C. Code walkthrough

D. Execution testing

A. to know when a specific test has finished its execution

B. to ensure that the test case specification is complete

C. to set the criteria used in generating test inputs

D. to determine when to stop testing

A. updating tests when the software has changed

b. testing a released system that has been changed

C. testing by users to ensure that the system meets a business need

D. testing to maintain business advantage

A. after more formal techniques have been applied

B. as the first approach to deriving test cases

C. by inexperienced testers

D. after the system has gone live

A. The ones that cover the most important quality risk

B. The ones that cover the requirements

C. The ones that cover conditions

D. The ones that cover the functions

A. Test the three types of item to post and three different weights [Req 24.3]

B. Test 1: letter, 10 grams, postage $0.25. Test 2: book, 500 grams, postage $1.00. Test 3: package, 999 gram, postage $2.53 [Req 24.3]

C. Test 1: letter, 10 grams to Belgium. Test 2: book 500 grams to USA. Test 3: package, 999 grams to South Africa [Req 24.3]

D. Test 1: letter 10 grams, Belgium, postage $0.25. Test 2: package 999 grams to South Africa, postage $2.53

A. A COTS software product may be acceptance tested when it is installed or integrated.

B. Acceptance testing of the usability of a component may be done during component testing.

C. Acceptance testing after a change has been released to the user community.

D. Acceptance testing of a new functional enhancement may come before system testing.

A. The testing of pseudo code

B. Performance testing

C. Alpha testing

D.The final phase of testing prior to deployment

A. Deciding on the execution of reviews

B. Documenting all the issues and problems

C. Leading the review of the documents

D. Identifying and describing the findings

A. Develop and prioritizing test cases, creating test data, writing test procedures and optionally, preparing test harness and writing automated test scripts.

B. Logging the outcome of test execution and recording the identities and versions of the software under test, test tools and testware.

C. Checking test logs against the exit criteria specified in test planning.

D. Verifying that the test environment has been set up correctly.

A. Path that people are particularly likely to follow

B. Choices at one menu level or data entry screen can affect the presentation of choices elsewhere

C. Test reaction to all combinations of valid and invalid inputs

D. Randomly select different paths in each test cycle

A. to ensure that all of the small components are tested

B. to ensure that the system interfaces to other systems and networks

C. to ensure that the integration testing can be performed by a small team

D. to specify how the software should be divided into components

E. to specify which components to combine when, and how many at once

A. Both inspections and walkthroughs are led by the author.

B. An inspection is led by a moderator and a walkthrough is led by the author.

C. Both inspections and walkthroughs are led by a trained moderator.

D. A walkthrough is led by the author. The author is not present during inspections.

A. At system and acceptance testing levels only.

B. At all test levels.

C. At all levels above integration testing.

D. At the acceptance testing level only.

A. To identify potential application failures by use of a test specification.

B. To identify defects in any software work product.

C. To identify spelling mistakes in a requirements specification.

D. To identify standards inconsistencies in the code.

A. Test planning.

B. Evaluating exit criteria and reporting.

C. Test closure.

D. Test control.

A. Measuring and analyzing results.

B. Reporting discrepancies as incidents.

C. Identifying test conditions or test requirements.

D. Assessing if more tests are needed.

A. 15,19 and 25.

B. 17,18 and19.

C. 18, 20 and22.

D. 16, 26 and 32.

A. 5, 6, 20

B. 4, 5, 80

C. 4, 5, 99

D. 1, 20, 100

A. Preventative tests and reactive tests are designed as early as possible.

B. Preventative tests are designed early; reactive tests are designed after the software has been produced.

C. Preventative testing is always analytical; reactive testing is always heuristic.

D. Preventative tests are designed after the software has been produced; reactive tests are designed early in response to review comments.

A. The cost of dealing with an adverse event if it occurs.

B. The probability that an adverse event will occur.

C. The amount of testing planned before release of a system.

D. The likelihood of an adverse event and the impact of the event.

A. ii, iii.

B. i, iii.

C. iii, iv.

D. i, ii

A. Availability of tools to support the proposed techniques.

B. The budget allowed for training in proposed techniques.

C. Available skills and experience in the proposed techniques.

D. The willingness of the test team to learn new techniques.

A. Log defects.

B. Explain the documents to the participants.

C. Gather metrics.

D. Allocate the individual roles.

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.

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

A. External failure

B. Internal failure

C. Appraisal

D. Prevention

A. Open, Assigned, Fixed, Closed

B. Open, Fixed, Assigned, Closed

C. Assigned, Open, Closed, Fixed

D. Assigned, Open, Fixed, Closed

A. Moderator

B. Scribe

C. Reviewers

D. Author

A. Eliminate some of the requirements that have not yet been implemented.

B. Add more engineers to the project to make up for lost work.

C. Ask the current developers to work overtime until the lost work is recovered.

D. Hire more software quality assurance personnel.

A. Performance testing

B. Unit testing

C. Business scenarios

D. Static testing

A. Boundary value analysis

B. Equivalence partitioning

C. Decision table testing

D. State transition testing

A. Unit testing

B. Regression testing

C. Alpha testing

D. Integration testing

A. To identify, evaluate, and rank tools, and recommend tools to management

B. To determine what kind of tool is needed, then find it and buy it

C. To initiate the tool search and present a case to management

D. To identify, evaluate and select the tools

A. Reliability

B. Usability

C. Scalability

D. Maintainability

A. i,ii,iii are true and iv is false

B. i,iii,iv are true and ii is false

C. ii,iii are true and i and iv are false

D. i,ii are false and iii , iv are true

A. Checking test logs against the exit criteria specified in test planning.

B. Logging the outcome of test execution.

C. Assessing if more tests are needed.

D. Writing a test summary report for stakeholders.