In which of the following circumstances is the transition from a high-level test case to a low-level test case MOST LIKELY to be deferred from test design to test implementation?

• A. When product risk analysis has not been completed
• B. When the person who runs the test will not be its author
• C. When specific test data are needed for the test case
• D. When the details required depend on the test execution schedule

A system will be developed to support the administration of table-tennis tournaments. The following requirements for the enrolment of entrants have been provided:
R1. High. The administrator shall be able to enter the entrant's name, address, phone number/s (mobile and/or home), email and social media handles. Validation rules for these data items are provided separately.
R2. High. The administrator shall be able to enter the entrant's current world ranking (up to 250) and their relationship with the tournament sponsors (i.e. clothing / equipment / endorsement).
R3. High. The administrator shall be able to enter the entrant's attendance history at previous events (i.e.
finalist / played / withdrew during event / withdrew before event).
R4. Medium. From the entrant's address the system shall derive whether or not the entrant lives locally and, on the basis of that combined with other rules that are provided separately, shall suggest how much of the tournament's overall prize fund should be offered to the entrant as their individual attendance fee.
R5. Low. The administrator should be able to change the suggested attendance fee and the system should then deduct this from the remaining prize fund balance accordingly.
You have been asked to review the requirements using perspective-based reading, from your viewpoint as the TA who will be writing functional correctness system test cases. Assume that the other rules referred to by requirements R1 and R4 have been reviewed and are satisfactorily testable. Which conclusion would you reach?

• A. One of the requirements is not fully testable
• B. Two of the requirements are not fully testable
• C. Three of the requirements are not fully testable
• D. All of the requirements are fully testable

You are working on a project to build a purchasing system. The main requirements for the system are that it shall:
* Allow users to enter details of items that they wish to have purchased and, from these details, create a purchase request.
* Take each purchase request through a workflow that will allow the requestor's line manager to approve the request, reject it or return it for clarification / modification.
* Forward approved requests to the Purchasing Department.
* Allow purchasers to find the best available supplier for each approved request and place the request on that supplier as a purchase order.
The solution is being developed according to the company's traditional V-model methodology. The requirements are clearly documented and include a business process model. Operational profiles have been created to guide performance testing.
Initial item entry will involve a check that each item entered exists on the master stock file and that the user is entitled to request it; this depends on user role and grade. Line manager authorization will be assisted by a recommendation made by the system according to relevant business rules, although the manager can override this recommendation. For approved requests, the workflow will continue to support the process through to placing of the purchase order.
Planning has begun for system testing and the Test Manager has asked you, the senior TA, to help with it.
What would be the MOST effective techniques for functional testing of this project?
a) Combinatorial testing
b) Random testing
c) CRUD testing
d) State transition testing
e) Scenario-based testing
f) Decision table testing
g) Exploratory testing

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

Your project is developing an application to process claims against insurance policies. Which of the following is a good example of CRUD completeness testing?

• A. A set of test cases that, when executed, verify the application's ability to independently create, read, update and delete a claim
• B. A review of the requirements to check that all user needs for CRUD operations on a claim record have been elicited
• C. A set of test cases that verify the sequence of creating, reading, updating, reading and deleting a claim, and then check that it can no longer be read
• D. A review of the technical specifications to check that the abilities to create, read, update and delete a claim have been included in the application architecture