Designing the System Under Test (SUT) for testability is important for a good test automation approach and can also benefit manual test execution.
Which of the following is NOT a consideration when designing for testability?

• A.Control: the SUT needs to provide interfaces that can be used to perform actions on SUT.
• B.Observability: The SUT needs to provide interface that give insight into the system.
• C.Clearly defined architecture: The SUT Architecture needs to provide clear and understandable interfaces giving control and visibility on all test levels.
• D.Re-useability: The code written for the SUT must be re-useable for other similar system.

Comment: *

Name: *

Email: *

Verification: *

You identified a suitable project to pilot an automation tool and planned and conduced a pilot. The pilot has been successful and tool Is being deployed within your organization, with a plan to increase tool use by the one project at a time. During this rollout some test processes will be changed slightly to gain additional benefits from using the tool.
In the pilot project, a small set of manual tests were automated for the first time. You are currently monitoring the test automation efficiency and this reveals that the automation regime for the tests is not yet mature.
Which of the following statements is TRUE?

• A.The pilot project should have been critical so that maximum benefits were delivered
• B.The test process should be radically changed to gain additional benefits from using the tool.
• C.The approach used for deployed this tool is aligned to the standard success factor for deployment
• D.The target defined for the project was inappropriate, because the automation regime for the automated tests at the end of the pilot is not yet mature.

Comment: *

Name: *

Email: *

Verification: *

You have been asked to determine a TAS for a new release of a SUT,test should be automated wherever. The new release will consist of 5 new interfaces and an amendment to 3 existing interfaces. The new and amended interface will be deliver incrementally in 3 sprints, each lasting 2 weeks.
What would be the BEST Test Automation Solution (TAS) design in this scenario?

• A.Automate tests at both Component and System Level. Only do this automation once every interface has been fully developed or amended and manual testing has completed successfully.
• B.Automate the tests at two levels, Component and System level. Create customized hooks at Component level for interface not yet developed or amended. Only use the newly developed or amended interfaces to test at System level.
• C.Automate tests at one level only, System level. Use only the newly developed interfaces and do not create any customized interfaces/test hooks.
• D.Automate a test at once level, component level, Create customized interface/test hooks for this level where the interface has not yet been developed or amended.

Comment: *

Name: *

Email: *

Verification: *

Consider the following layers of the gTAA structure:
a.Test generation layer
b.Test definition layer
c.Test execution layer
d.Test execution layer
Consider the following capabilities associated with these layers.
Acquire all the necessary resources before each test and release all after run, in order to avoid interdependences between test Allow the automated test scripts on an abstract level to interact with components, configurations and interfaces of the SUT.
Design test directives that allow configuring the algorithms used to automatically produce the test cases a given model of the SUT.
Allow the definition and implementation of test cases and data by means of templates and/or guidelines.
Which of the following BEST matches each layer with the appropriate capability?

• A.a-3, b-4, c-1, d-2
• B.a-4, b-3, c-2, d-1
• C.a-3, b-4, c-2, d-1
• D.a-4, b-3, c-1, d-2

Comment: *

Name: *

Email: *

Verification: *

A project consists of distributed teams working in a 24-hour environment, where activities happen at all hours of the day. This project adopts a CI (Continuous Integration) process when developer check-in code and consists of automated activities that include generating a build and deploying it to a test environment.
Automated integration tests are run multiple times a day. The project have asked for a report containing the automation test results for every build, which must be available 24/7 to the project team.
Which of the following would be the BEST way to automatically provides this report?

• A.Store the code coverage results of the integration tests for the last build to a database (without overwriting the results from the previous builds). And automatically create a chart showing the trend in code coverage and send via email to the project team.
• B.Store the execution results of the integration tests for the last build to a database (without overwriting the results from the previous builds). Automatically create a test execution report for this build and send it via e-mail to the project team
• C.Store the execution result of the integration tests for the last build to a database (overwriting the results from the previous build), automatically create atest execution report for this build send It via e-mail to the project team
• D.Store the execution results of the integration tests for the last build to a database (without overwriting the results from the previous builds), use this database to automatically update a dashboard containing the build history and test results accessible to the project team.

Comment: *

Name: *

Email: *

Verification: *