There can be no definitive answer to this exercise but most of the following tasks should be considered. You may well have others in addition.

Test analysis

Tasks from the CTAL-TA syllabus:
• Understand the scope.
• Check on entry criteria for test basis (does it exist, has it been reviewed, is
there time and money).
• Analyse test basis to identify test conditions.
• Talk to users if there is insufficient detail in the test basis.
• Link test conditions to source (test basis / risks).

From the Foundation syllabus:
• Reviewing the test basis (such as requirements, software integrity level (risk
level), risk analysis reports, architecture, design, interface specifications).
• Evaluating testability of the test basis and test objects.
• Identifying and prioritising test conditions based on analysis of test items, the specification, behaviour and structure of the software.

Test design

Tasks from the CTAL-TA syllabus:
• Determine in which areas high and low level test cases are needed.
• Determine the test techniques that provide necessary coverage.
• Create test cases that cover the test conditions.

From the Foundation syllabus:
• Designing and prioritising high level test cases.
• Identifying necessary test data to support the test conditions and test cases.
• Designing the test environment set-up and identifying any required
infrastructure and tools.
• Creating bi-directional traceability between test basis and test cases.
Last modified: Tuesday, 2 July 2013, 1:47 PM