Online Access Free CT-TAE Practice Test

You are reviewing the testability of your SUT.
Which of the following BEST refers to the characteristic of OBSERVABILITY?

• A.The ability to identify states, outputs, intermediate result and error messages in the SUT
• B.The ability to exercise the SUT by entering inputs, triggering events and invoking methods
• C.The ability of the SUT to prevent unauthorized access to its components or data.
• D.The ability of the SUT to perform its intended function for a specified period of time

Consider A TAS for testing a desktop application via its GUI. All the test cases of the automated test suite contain the same identical sequences of steps at the beginning (to create the necessary objects when doing a preliminary configuration of the test environment and at the end (to remove everything created -specifically for the test itself during the preliminary configuration of the test environment). All automated test cases use the same set of assertion functions from a shared library, for verifying the values in the GUI fields ( e.g text boxes).
What is the BEST recommendation for improving the TAS?

• A.Adopting a set of standard verification methods for use by all automated tests
• B.Implementing keywords with higher level of granularity
• C.Improving the architecture of the application in order to improve its testability
• D.Implementing standard setup and teardown functions at test case level

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?

• A.The automated test cases will not contain the expected result
• B.The process of configuring the TAS will be error-phone due to manual intervention
• C.The connectivity from the TAS to the dedicated test interfaces will not work
• D.False alarms, that are unlikely to occur in the real world, will be observed during testing

You have implemented a keyword-driven scripting framework, which uses a test execution tool to run the tests. This has been in use for the past year and all of the teams now use this framework as the standard approach for test execution.
The teams all work on different aspects of the SUT and they have all experienced significant benefits in the use of this scripting framework. However, on closer examination, you have discovered that there are numerous instances where the teams have the same functionality to test but are using different keywords.
One of your objectives for improvement is to create consistency among the teams.
What is the BEST way to handle this situation?

• A.Do nothing, each team are working in isolation and they are all experiencing significant benefits in the way they are currently working.
• B.Create a central library of keywords and associated definitions for each team to use.
• C.Provide each team with a set of guidelines and naming conventions for keywords.
• D.Move to a model-based approach to scripting where the models include the keywords.

As a TAE you are evaluating a functional test automation tool that will be for several projects within your organization. The projects require that tool to work effectively and efficiently with SUT's in distributed environments. The test automated tool also needs to interface with other existing test tools (test management tool and defect tracking tool.) The existing test tools subject to planned updates and their interface to the test automated tool may not work property after these updates.
Which of the following are the two LEAST important concerns related to the evaluation of the test automation in this scenario?
* Is the test automation tool able to launch processors and execute test cases on multiple machines in different environments?
* Does the test automation tool support a licensing scheme that allows accessing different sets?
* Does the test automation tool have a large feature set, but only part of the features will be sets?
* Do the release notes for the planned updates on existing specify the impacts on their interfaces to other tools?
Does the test automation tool need to install specific libraries that could impact the SUT?

• A.C and D
• B.A and E
• C.A and C
• D.B and E