Refer to SCENARIO 2 Project 2 is to be delivered using a RAD software development model. There will be two increments, the first will deliver a simple prototype user interface to facilitatetesting of the sound system delivered by 'Silver Sound Ltd', the second will deliver the full user interface required for the production system.
Development of the business requirements and project plan are underway, detailed system analysis will follow for each increment.
You have studied the test policy and risk register and must plan the next set of test activities. Which one of the following is the MOST effective approach for this project?
SELECT ONE OPTION

• A. Conduct exploratory testing only for the first increment as it is a prototype solution, commence test charter planning for increment 2
• B. Develop a master lest plan for each increment as soon as systems analysis is complete, then proceed with test analysis.
• C. Conduct high-level test planning and test analysis now, followed by more detailed test planning and test analysis for each increment considering use of automation where appropriate.
• D. Finalize detailed test planning now for both increments, conduct exploratory testing for the first increment, then use automated tests only for increment 2.

You are Test Manager for a project which is in the Test Implementation stage for the first planned iteration, creation of the initial Test Cases and required test data is progressing well.
The Test Strategy documents the Stakeholders view that small teams should collaborate together to create and test functionality which is to be released in iterations, with each release building on the success of the last.
Stakeholders are willing to accept the risks of a partly working system in the early stages. Delivery of working functionality (particularly around interfaces to third party systems and performance of back end databases) is the priority for the early releases.
Which of the following test types would you select for this first planned iteration, in order to meet Stakeholders expectations?
a) Usability testing
b) Structural testing
c) Functional testing of process flows
d) Performance testing
e) Business process testing
f) Component integration testing
You are Test Manager for a project which is in the Test Implementation stage for the first planned iteration, creation of the initial Test Cases and required test data is progressing well.
The Test Strategy documents the Stakeholders view that small teams should collaborate together to create and test functionality which is to be released in iterations, with each release building on the success of the last.
Stakeholders are willing to accept the risks of a partly working system in the early stages. Delivery of working functionality (particularly around interfaces to third party systems and performance of back end databases) is the priority for the early releases.
Which of the following test types would you select for this first planned iteration, in order to meet Stakeholders expectations?
a) Usability testing
b) Structural testing
c) Functional testing of process flows
d) Performance testing
e) Business process testing
f) Component integration testing

• A. b, c, d and f.
• B. b, d, e and f.
• C. a, c, d and e.
• D. a. b, d and f.

You are performing a risk assessment for a financial application using quantitative risk analysis. The following is a table describing the analysis undertaken so far:

Which of the following statements correctly describes the outcome of the risk assessment using the "Cost of Exposure" technique in this scenario? SELECT ONE OPTION

• A. PR2 should be tested while PR1. PR3 and PR4 should not be tested
• B. PR1, PR3 and PR4 should be tested while PR2 should not be tested
• C. PR3 and PR4 should be tested while PR! and PR2 should not be tested.
• D. Testing for failures associated to PR4 should happen first.

Which TWO of the following metrics will be MOST useful in helping the stakeholders to decide whether to allow the system into acceptance testing?
* Breakdown of all risks by status (closed / not fully tested / one or more tests failed)
* Breakdown by test priority of test execution status (passed / failed / not run)
* Breakdown of outstanding risks by risk level and status (not fully tested / one or more tests failed / both)
* Breakdown of unresolved defects by severity and status
* Breakdown of unresolved defects by Risk Id/s that is/are affected by them

• A. 1 &4
• B. 1 &2
• C. 2&5
• D. 3&4