CTAL-TAE Exam Dumps - iSQI Other Certification Questions and Answers

The TAS must run in the development environment because development and programming knowledge are required for its maintainability

The TAS must be under configuration management, along with the test suite, the testware artefacts and the test environment in which it runs

The TAS must separate the test scripts from the environment in which it runs and from the associated harnesses and artefacts

The TAS must consist of components that can be easily replaced without affecting the overall behavior of the TAS itself

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.

Store the execution result of the integration tests for the last build to a database (overwriting the results from the previous build), automatically create a test execution report for this build send It via e-mail to the project team

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

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.

Outliers in test execution times

Security vulnerabilities in automated test cases

Unstable automated test cases

Maintainability issues in automated test cases

The specified root cause is a race condition that can be identified by also analyzing the log files of the test case, the SUT, and the TAF

Determining the specified root cause may require, in addition to the TAE, the support of others such as developers and system engineers

The specified root cause must be in the instability of the test environment, since no code has been changed

Determining the specified root cause is certainly easier than if the automated test always fails (deterministic behavior)

Use error codes in test automation code instead of exceptions (if exceptions are supported by the programming language) for error handling

Avoid producing test automation code containing methods with too many levels of nesting, as deeply nested code is more difficult to understand

Avoid adopting design patterns that introduce high levels of abstraction in test automation code, such as the flow model pattern

Avoid using static analyzers on test automation code and other development tools, as they are designed to improve the maintainability of SUT code

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.

Automate tests at one level only, System level. Use only the newly developed interfaces and do not create any customized interfaces/test hooks.

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.

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.

Automated tests are not affected by the introduction of a new feature and running them against the new SUT is a waste of effort

The introduction of a new feature could require updates or additions to the testware components

The test automation engineer should work with the business analysts to ensure the new feature is testable

It is generally more difficult to automate test cases for a new feature as the development has not yet started

The duration of the pilot project was too short –it should last unit the success factors are achieved

The target defined for the business case is too accurate –it should not be measureable

The project selected for the pilot is too critical –if should not be too critical or too trivial

The target defined for the business case seems difficult to hit – it should be realistic

A and B are both internal TAS metrics

A is an internal TAS metric and B is an external TAS metric

A and b are both external TAS metric

A is and external TAS metric and b is an internal TAS metric

The keyword-driven framework is not suitable, it would be better to adopt a structured-scripting approach

False positive errors are likely to occur when running the automated tests on the new releases without modifying the test

The total execution time of the automated regression test suite will decrease for each planned release.

The keyword-driven framework introduces a level abstraction that is too high and makes it difficult what really happens