Which of the following statements refers to a good testing practice that applies to all software development lifecycles?

1. A. Each test level should have its own specific test objectives that should be consistent with the software development lifecycle phase or type of activities it addresses.
2. B. Test analysis and design for any test levels should begin as soon as coding is complete, and all system components are available for testing
3. C. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
4. D. All the tests should be automated and run as part of the continuous integration process with every software change

Correct Answer: A
Good testing practice dictates that each test level (e.g., unit testing, integration testing, system testing) should have distinct test objectives aligned with the phase of the software development lifecycle it addresses. This ensures that testing is effective and relevant at each stage. According to the ISTQB CTFL Syllabus v4.0, establishing clear test objectives that are consistent with the development phase helps in achieving specific goals and improving the overall quality of the software product.

Which of the following are the phases of the ISTQB fundamental test process?

1. A. Test planning and control, Test analysis and design, Test implementation and execution, Evaluating ex t criteria and reportin
2. B. Test closure activities
3. C. Test planning, Test analysis and desig
4. D. Test implementation and contro
5. E. Checking test coverage and reporting, Test closure activities
6. F. Test planning and control, Test specification and desig
7. G. Test implementation and execution, Evaluating test coverage and reporting, Retesting and regression testing, Test closure activities
8. H. Test plannin
9. I. Test specification and desig
10. J. Test implementation and executio
11. K. Evaluating exit criteria and reportin
12. L. Retesting and test closure activities

Correct Answer: A
The ISTQB fundamental test process consists of five main phases, as described in the ISTQB Foundation Level Syllabus, Version 4.0, 2018, Section 2.2, page 15:
✑ Test planning and control: This phase involves defining the test objectives, scope, strategy, resources, schedule, risks, and metrics, as well as monitoring and controlling the test activities and results throughout the test process.
✑ Test analysis and design: This phase involves analyzing the test basis (such as requirements, specifications, or user stories) to identify test conditions (such as features, functions, or scenarios) that need to be tested, and designing test cases
and test procedures (such as inputs, expected outcomes, and execution steps) to cover the test conditions. This phase also involves evaluating the testability of the test basis and the test items (such as software or system components), and selecting and implementing test techniques (such as equivalence partitioning, boundary value analysis, or state transition testing) to achieve the test objectives and optimize the test coverage and efficiency.
✑ Test implementation and execution: This phase involves preparing the test
environment (such as hardware, software, data, or tools) and testware (such as test cases, test procedures, test data, or test scripts) for test execution, and executing the test procedures or scripts according to the test plan and schedule. This phase also involves logging the outcome of test execution, comparing the actual results with the expected results, and reporting any discrepancies as incidents (such as defects, errors, or failures).
✑ Evaluating exit criteria and reporting: This phase involves checking if the planned test activities have been completed and the exit criteria (such as quality, coverage, or risk levels) have been met, and reporting the test results and outcomes to the stakeholders. This phase also involves making recommendations for the release or acceptance decision based on the test results and outcomes, and identifying any residual risks (such as known defects or untested areas) that need to be addressed or mitigated.
✑ Test closure activities: This phase involves finalizing and archiving the testware
and test environment for future reuse, and evaluating the test process and the test project against the test objectives and the test plan. This phase also involves identifying any lessons learned and best practices, and communicating the findings and suggestions for improvement to the relevant parties.
References = ISTQB Certified Tester Foundation Level Syllabus, Version 4.0, 2018, Section 2.2, page 15; ISTQB Glossary of Testing Terms, Version 4.0, 2018, pages 37-38;
ISTQB CTFL 4.0 - Sample Exam - Answers, Version 1.1, 2023, Question 88, page 32.

A possible risk of introducing test automation is:

1. A. the tool may not be fit-for-purpose.
2. B. the tool may create additional development dependencies.
3. C. the tool may not be compatible with the development platform.
4. D. the tool will be owned and maintained by developers and replace testers.

Correct Answer: A
One possible risk of introducing test automation is that the selected tool may not be fit-for- purpose. This means that the tool might not meet the specific needs and requirements of the project, leading to inefficiencies and possibly failing to provide the expected benefits. It is crucial to evaluate and select the appropriate tool based on the project's context and objectives. The ISTQB CTFL syllabus highlights the importance of careful tool evaluation and selection to ensure it aligns with the testing goals and the development environment. References:ISTQB CTFL Syllabus, Section 6.2, "Potential Benefits and Risks of Test Automation."

Which of the following statements about retrospectives is TRUE?

1. A. Only developers and testers should be involved in retrospectives, as involving people in other roles is very likely to prevent developers and testers from having open and constructive discussions that really help identify process improvements.
2. B. Retrospectives can be very effective in identifying process improvements and can also be very efficient and cost-effective especially since, unlike reviews, they do not require any follow-up activities
3. C. On Agile projects, well-conducted retrospectives at the end of each iteration can help the team reduce and sometimes even eliminate the need for dairy stand-up meetings.
4. D. During retrospectives, in addition to identifying relevant process improvements, participants should also consider how to implement these improvements and retain them based on the context of the project, such as the software development lifecycle.

Correct Answer: D
Retrospectives are a crucial part of Agile practices, aiming to identify process improvements and determine how to implement them effectively. They should involve participants discussing not only what improvements could be made but also how to integrate and sustain those improvements within the project context, including the software development lifecycle. This makes statement D accurate according to the ISTQB CTFL syllabus.

Exploratory testing is an experience-based test technique

1. A. Where a developer and a tester work together on the same workstation while the developer actively writes code, the tester explores the code to find defects.
2. B. That can be organised into sessions guided by test charters outlining test objectives that will guide the testers' exploration
3. C. Where a team of testers explores all possible test techniques in order to determine the most suitable combination of these techniques to apply for a test project.
4. D. That aims at finding defects by designing tests that exercise all possible combinations ofinput values and preconditions

Correct Answer: B
Exploratory testing is an experience-based test technique where testers actively engage with the software, learning about its behavior while simultaneously designing and executing tests. According to the ISTQB CTFL syllabus, exploratory testing can be structured into sessions guided by test charters, which outline the test objectives and provide direction for the testers' exploration. This method is particularly useful in situations where test documentation is limited or where rapid feedback is needed. Thus, option B correctly describes how exploratory testing can be organized.