Question 1
AdvancedChapter 8: Continuous Improvement · TAE-8.1.2 Analyze the technical aspects of a deployed test automation solution and provide recommendations for improvement
A mature Test Automation Solution (TAS) for a large-scale logistics platform is experiencing a high rate of false-positive results (tests that fail even though the SUT has no defect). Analysis reveals that many failures are due to test data inconsistencies across distributed microservices. For example, a test creating a shipment in the 'Orders' service fails because the corresponding product information is not yet propagated to the 'Inventory' service. Which approach provides the MOST robust and scalable solution to this data synchronization problem?
Answer and explanation
Correct answer: B
These failures are false-positive results in ISTQB terms: the test reports a failure although the SUT works, because it checks the data before the services have finished propagating it. CTAL-TAE v2.0 §8.1.2 says hard-coded waits 'can be a root cause for many test automation defects given the unpredictability of software response times', whereas dynamic waiting by polling lets the TAS wait only as long as needed, provided a timeout stops the test if a real defect means the expected state never arrives. Polling the dependent services' APIs until the expected data state is confirmed therefore removes the timing problem without slowing every test. A fixed sleep is either wasted time or still too short; inserting data directly into each service's database bypasses the services' business logic and APIs and couples the tests to internal schemas; retrying the whole suite only hides the problem and multiplies execution time.
