Exam CT-TAE All QuestionsBrowse all questions from this exam
Go to Exam
Question 40

You have been asked to automate a set of functional tests at system test level via the CLI of the SUT for the first release of a new software system. Such automated tests, which will be delivered to the team in charge of maintenance testing, will be used as part of the regression testing and thus they must be as fast and cheap to maintain as possible. Since the regression test suite is expected to grow significantly over time, also the cost of adding new automated tests must be as low as possible. In particular, the number of scripts should be dependent on the size of the SUT rather than the number of tests. Moreover, there is high risk that the test automation tool will change several times during the operational life of the system, and thus the automated tests should be implemented to assure high level of independence from such tool.

Based only on the given information, which of the following scripting techniques would you expect to be most suitable in this scenario?

    Correct Answer: B

    Keyword-driven scripting is most suitable in this scenario because it abstracts the test logic from the test scripts, making it easier and cheaper to maintain and modify the tests. This method aligns well with the requirement for minimizing the number of scripts based on the size of the SUT rather than the number of tests. Additionally, keyword-driven scripting promotes reusability of test components, facilitating low-cost addition of new tests and providing independence from the automation tool, which is important given the high risk of the automation tool changing during the system's operational life.

Discussion
issoChanOption: B

Based on the provided information, the most suitable scripting technique for this scenario would likely be B. Keyword-driven scripting. Keyword-driven scripting allows for creating tests by using keywords that represent actions or operations to be performed on the system under test (SUT). This approach abstracts the test logic from the test scripts themselves, making it easier to maintain and modify tests. It also facilitates reuse of test components, which aligns well with the requirement of minimizing the number of scripts and focusing on the size of the SUT. Moreover, keyword-driven scripting provides a higher level of abstraction, which can make the tests more resilient to changes in the underlying automation tool. This is important given the high risk mentioned of the test automation tool changing during the operational life of the system.