Q: 7
Consider a TAS that exclusively uses the APIs of a SUT. To make this work, significant changes have
been required to the SUT by adding a set of dedicated test interfaces to the APIs. All the automated
tests will use these test interfaces when interacting with the SUT. Assume that you are currently
verifying the correctness of the automated test environment and test tool setup.
Which of the following would you expect to be the MOST specific risk associated with this scenario?
Options
Discussion
D . False alarms are tied directly to testing through non-prod test interfaces like here. Not every API approach has that risk.
D . The main thing is those dedicated test interfaces can make the automation report problems that wouldn't really show up with the real-world APIs, so you get false alarms. A seems tempting but isn't as linked to this scenario. Similar question popped up in practice materials.
A is wrong, D is definitely the most specific risk here. Making special test interfaces means the tests might catch things that wouldn't show up in real usage, so you get false positives. A (connectivity) could be a problem, but that's always a generic risk. Pretty sure about D here, unless I'm missing something.
A for me. Connectivity to the new test interfaces could easily break with all the changes done, that feels more concrete. I get why some pick D, but not convinced that's the biggest issue upfront.
Option A
Its D, since connectivity (A) is always a risk but not unique to test-only APIs in this context.
I don’t think it’s A, since connectivity is always a generic risk with any integration. Here, the changes add test-only interfaces, which makes D (false alarms from differences in test vs real environments) much more unique to this setup. Trap is thinking setup hassle (A/B) but that’s less specific. Open to other views if I missed something subtle.
D , the false alarms are a direct risk from using those test-only interfaces.
Had something like this in a mock, picked A.
Definitely D. Adding test-only interfaces to the SUT can lead to false alarms that wouldn't actually happen in real-world use cases.
Be respectful. No spam.
