CTAL-TAE · Question #159
A SUT (SUT1) is a client-server system based on a "thin client". The client is primarily a display and input interface, while the server provides almost all the resources and functionality of the…
The correct answer is D. The TAS should support mainly server-side automation for SUT1 and client-side automation for. In a thin client system (SUT1), most functionality resides on the server, so automation should focus on server-side testing. In a fat client system (SUT2), most functionality is handled on the client, so automation should focus on client-side testing. This approach ensures…
Question
A SUT (SUT1) is a client-server system based on a “thin client”. The client is primarily a display and input interface, while the server provides almost all the resources and functionality of the system. Another SUT (SUT2) is a client-server system based on a “fat client” that relies little on the server and provides most of the resources and functionality of the system. A given TAS is used to implement automated tests on both SUT1 and SUT2. The main objective of the TAS is to cover as many system functionalities as possible through automated tests executed as fast as possible. Which of the following statements about the automation solution is BEST in this scenario?
Options
- AThe TAS should support mainly client-side automation for both SUT1 and SUT2
- BThe TAS should support mainly client-side automation for SUT1 and server-side automation for
- CThe TAS should support mainly server-side automation for both SUT1 and SUT2
- DThe TAS should support mainly server-side automation for SUT1 and client-side automation for
How the community answered
(31 responses)- A10% (3)
- B23% (7)
- C3% (1)
- D65% (20)
Explanation
In a thin client system (SUT1), most functionality resides on the server, so automation should focus on server-side testing. In a fat client system (SUT2), most functionality is handled on the client, so automation should focus on client-side testing. This approach ensures maximum coverage and faster execution by targeting the layers where the core logic resides.
Topics
Community Discussion
No community discussion yet for this question.