Configuration management (CM) in the context of testing involves the process of managing changes to the software and its associated artifacts, such as test plans, test cases, test scripts, and test results. It ensures that all changes are systematically tracked and controlled throughout the software development lifecycle.
* Option A: Incorrect. While CM supports consistency in test environments, it is not specifically about comparing expected and actual results.
* Option B: Correct. CM allows tracking all changes to versions of testware, ensuring that the correct versions are used and any changes are documented and managed.
* Option C: Incorrect. This describes quality management, not configuration management.
* Option D: Incorrect. Configuration management does not focus on configuring static analysis tools.

The best example of a test case for this user story should cover the acceptance criteria comprehensively.
Option A addresses the critical aspects of the acceptance criteria:
* Verifying the discount for the first timeslot (8 AM GMT) - ensuring it provides a 10% discount.
* Verifying that changing the time slot removes the discount - ensuring the discount logic is correctly applied.
This test case effectively validates the functionality related to both the discount and the ability to change time slots, which are key parts of the user story's requirements.

Test automation allows you to produce tests that are less subject to human errors, as they can execute predefined test scripts or test cases with consistent inputs, outputs, and expected results. Test automation can also reduce the manual effort and time required to execute repetitive or tedious tests, such as regression tests, performance tests, or data-driven tests. Test automation does not demonstrate the absence of defects, as it can only verify the expected behavior of the system under test, not the unexpected or unknown behavior. Test automation does not avoid performing exploratory testing, as exploratory testing is a valuable technique to discover new information, risks, or defects that are not covered by automated tests. Test automation does not increase test process efficiency by facilitating management of defects, as defect management is a separate activity that involves reporting, tracking, analyzing, and resolving defects, which may or may not be related to automated tests. References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:
* ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 3.3.1, Test Automation1
* ISTQB Glossary of Testing Terms v4.0, Test Automation2

Effort estimate does not depend on the budget of the project, but rather on the scope, complexity, and quality of the software product and the testing activities1. Budget is a constraint that may affect the feasibility and accuracy of the effort estimate, but it is not a factor that determines the effort estimate. Effort estimate is the amount of work required to complete the testing activities, measured in terms of person-hours, person-days, or person-months2.
The other options are correct because:
A) Once the test effort is estimated, resources can be identified and a schedule can be drawn up, as they are interrelated aspects of the test planning process3. Resources are the people, tools, equipment, and facilities needed to perform the testing activities4. Schedule is the time frame and sequence of the testing activities, aligned with the project milestones and deadlines5.
B) Effort estimate can be inaccurate because the quality of the product under tests is not known, as it affects the number and severity of the defects that may be found and the rework that may be needed to fix them6. Quality is the degree to which the software product satisfies the specified requirements and meets the needs and expectations of the users and clients7.
D) Experience based estimation is one of the estimation techniques, which relies on the judgment and expertise of the testers and other project stakeholders to estimate the test effort based on similar projects or tasks done in the past. Experience based estimation can be useful when there is a lack of historical data, formal methods, or detailed information about the software product and the testing activities.
Reference =
1 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 154
2 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 155
3 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 156
4 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 157
5 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 158
6 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 159
7 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 16
[8] ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 160
[9] ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 161

* A product risk is a risk that affects the quality or timeliness of the software product being developed or tested1. Product risks are related to the requirements, design, implementation, verification, and maintenance of the software product2.
* The risk of the sub-contractor failing to meet his commitment is a product risk, as it could cause a delay in the completion of the testing required for the current cycle, which in turn could affect the release date of the product. The release date is an important aspect of the product quality, as it reflects the customer satisfaction and the market competitiveness of the product3.
* The other options are not correct because:
* A. It is not true that any risk associated with development timeline is a product risk. Some risks could be project risks, which are risks that affect the management or control of the software project, such as budget, resources, schedule, or communication1. For example, a risk of losing a key project stakeholder is a project risk, not a product risk.
* B. It is not true that the risk is no longer a risk for the Test Manager since an independent party is managing it. The Test Manager is still responsible for ensuring that the testing activities are completed according to the test plan and the quality objectives4. The Test Manager should monitor and control the sub-contractor's performance and communicate with him regularly to identify and mitigate any potential issues or deviations5.
* C. It is not clear what is meant by "object" in this option, but it could be interpreted as the software system under test or the test object6. In any case, the risk is not an object risk, as it does not affect the successful completion of the object, but rather the successful completion of the testing of the object. An object risk could be a risk that affects the functionality, reliability, usability, efficiency, maintainability, or portability of the software system under test2. For example, a risk of the software system having a high complexity or a low testability is an object risk, not a product risk.
References =
* 1 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 97
* 2 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 98
* 3 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 99
* 4 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 100
* 5 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 101
* 6 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 102