Crucial

Question 1

System Test Planning in the V-Model

Answer 1

System test planning occurs concurrently with project planning, and test monitoring and control continues until test completion. This will influence the schedule inputs provided by the Test Analyst for project management purposes.

Question 2

System Test Analysis in the V-Model

Answer 2

System test analysis and design aligns with documents such as the system requirements specification, system and architectural (high- level) design specification, and component (lowlevel) design specification.

Question 3

System Test Implementation in the V-Model

Answer 3

Implementation of the system test environment might start during system design, though the bulk of it typically would occur concurrently with coding and component testing, with work on
system test implementation activities stretching often until just days before the start of system test execution.

Question 4

System Test Execution in the V-Model

Answer 4

System test execution begins when the entry criteria are met or, if necessary, waived, which typically means that at least component testing and often also component integration testing have met their exit criteria. System test execution continues until the system test exit criteria are met.

Question 5

Test Analysis Activities

Answer 5

• Analyze the test basis
• Identify defects of various types in the test basis
• Identify and prioritize test conditions and features to be tested
• Capture bi-directional traceability between each element of the test basis and the associated test conditions
• Perform tasks associated with risk-based testing

Question 6

Test Analysis Entry Criteria

Answer 6

• There is a body of knowledge (e.g., requirements, user stories) describing the test object that can serve as its test basis (see [ISTQB_FL_SYL] Sections 1.4.2 and 2.2 or a list of other possible sources of test basis).
• This test basis has passed review with reasonable results and has been updated as needed after the review. Note that if high-level test cases are to be defined (see Section 1.4.1), the test basis may not yet need to be fully defined. In Agile software development, this review cycle will be iterative as the user stories are refined at the beginning of each iteration.
• There is an approved budget and schedule available to accomplish the remaining testing tasks for this test object.

Question 7

Application of Test Techniques in Test Implementation

Answer 7

• Identifying test conditions
• Reducing the likelihood of omitting important test conditions
• Defining more precise and accurate test conditions

Question 8

Test Design Activities

Answer 8

• Determining in which test areas low-level or high-level test cases are appropriate
• Determining the test technique(s) that will enable the necessary coverage to be achieved. The techniques that may be used are established during test planning.
• Using test techniques to design test cases and sets of test cases that cover the identified test conditions
• Identifying necessary test data to support test conditions and test cases
• Designing the test environment and identifying any required infrastructure including tools
• Capturing bi-directional traceability (e.g., between the test basis, test conditions and test cases)