CTAL-TAE · Question #66
Consider a TAS aimed at implementing and running automated test scripts at the UI level on web apps. The TAS must support cross-browser compatibility for a variety of supported browsers, by ensuring…
The correct answer is A. Dependency inversion principle. By introducing abstractions in the TAA to handle interactions with different browsers, the TAS depends on abstractions rather than concrete browser implementations. This aligns directly with the Dependency Inversion Principle, which ensures that high-level modules (test…
Question
Consider a TAS aimed at implementing and running automated test scripts at the UI level on web apps. The TAS must support cross-browser compatibility for a variety of supported browsers, by ensuring that the same test script will run on such browsers in the same way without making any changes to it. This is achieved by introducing appropriate abstractions into the TAA for connection and interaction with different browsers. Because of this, the TAS will be able to make direct calls to the supported browsers using each different browser’s native support for automation. Which of the following SOLID principles was adopted?
Options
- ADependency inversion principle
- BOpen-closed principle
- CLiskov substitution principle
- DInterface segregation principle
How the community answered
(47 responses)- A55% (26)
- B13% (6)
- C26% (12)
- D6% (3)
Explanation
By introducing abstractions in the TAA to handle interactions with different browsers, the TAS depends on abstractions rather than concrete browser implementations. This aligns directly with the Dependency Inversion Principle, which ensures that high-level modules (test scripts) do not depend on low-level modules (specific browsers), but both depend on shared abstractions.
Topics
Community Discussion
No community discussion yet for this question.