Here you have the best ISTQB CT-TAE practice exam questions
You are working as a TAE for a company who have been using a web test execution tool for a number of years. The tool has been used successfully on ten web applications in the past.
The company are developing a new web application which has a friendly User Interface, but the developers have used an object throughout the application which the tool is unable to recognise. As a result, you have no way of capturing the object or verifying the contents using the automation tool.
What is the first thing you should do about this problem?
The first thing to do when the current test execution tool cannot recognize an object is to consult with the developers to see if they can change the object to something that the tool can recognize. This is a direct approach that seeks to make the existing tool work with the new application without immediately jumping to alternative tools or significant changes in the application's design.
A major component of your organisation's Test Automaton Solution (TAS) is a popular open-source third-party capture-replay tool for automated functional testing.
Which two of the following must the Test Automation Engineer (TAE) ensure happens for this TAS? a) The third party tool is placed under configuration management control. b) The annual support and maintenance costs are agreed with the tool's vendor. c) It is Important to obtain information about updates and new versions of the tool so that the third party tool is kept up to date. d) Ensure that the TAS test scripts are integrated into the tool's framework. e) Ensure that no changes are made to the tool, because modifications are not allowed for third party products.
The Test Automation Engineer (TAE) needs to ensure proper configuration management control for any third-party tools used, to maintain their integrity and manage updates efficiently. It is also crucial to stay informed about updates and new versions to keep the tool current and avoid potential compatibility or security issues. While annual support and maintenance costs might be relevant for commercial tools, they are less applicable to open-source tools, and ensuring test scripts are integrated is a broader task that may not directly relate to handling the third-party capture-replay tool.
If model-based testing has been selected for the overall test automation approach for a project, how does that influence the layers of the TAA?
If model-based testing has been selected for the overall test automation approach for a project, all layers of the Test Automation Architecture (TAA) are still used. However, the test generation layer will be automated based on the defined model. This allows for efficient and systematic creation of test cases that are derived directly from the model, ensuring that all necessary layers are addressed through automation.
Your functional regression test automation suite ran successfully for the first two sprints and no failures were encountered during the runs. The automation suite records the status of each test case as either 'pass' or 'fail' and has excellent recovery capability built in.
For the third sprint, the TAS log reported several test cases with a status of 'fail'. You investigated each test case and found that most failures were due to a defect in one of the keyword scripts, rather than in the SUT. For those where the failure was in the SUT, defect reports were raised but several were returned by the developers asking for more information to enable them to reproduce the problem.
Which additional log items SHOULD you add to the TAS that would BEST improve failure analysis and defect reporting for future sprints? a) Dynamic measurement information about the SUT. b) A status of TAS error’, in additional to pass' and 'fail', for each test case. c) Use of a colour coding scheme so that 'pass’ is in red and fail' is in green. d) A counter to determine how many times each test case has been executed. e) System configuration information including software/firmware and operating system versions. f) A copy of the source code for all Keyword scripts executed.
Adding both a status of 'TAS error' and system configuration information including software/firmware and operating system versions would best improve failure analysis and defect reporting. The status of 'TAS error' helps differentiate between issues caused by the test automation suite itself and those caused by the system under test, facilitating quicker identification of the root cause. System configuration details are crucial for reproducing defects, as they provide context about the environment in which the tests were executed.
Your TAS has been running successfully on a Windows/GUI based SUT for some years. The SUT has undergone minimal change over the years to maintain business as usual, deploying six-monthly releases for minor enhancements and bug fixes using a waterfall lifecycle.
The TAS has not changed at all during this period. The current project for the SUT will be using the Scrum methodology to deliver a more modern, competitive, user interface. It is in the release planning stage with an agreed release backlog and set of sprints outlined.
The move from lengthy waterfall releases to shorter sprints has led you to conduct a review of the current TAS to make sure it is robust and fully optimised for the timescale challenges of the new project.
What two steps would be BEST to undertake during the review?
a) Ensure that new automation code is using the same naming conventions as existing code. b) Perform a full regression run in Sprint 1 to identify what improvements could be made to the TAS for future sprints. c) Ensure that the TAS is using the latest libraries for the operating system. d) Review the functions that act upon the controls for the GUI for possible consolidation. e) Involve the test team to see what ease-of-use improvements they would like to see made to the TAS.
To ensure the TAS is robust and optimized for the new Scrum project, it is important to review and modernize the existing framework. Ensuring that the TAS is using the latest libraries for the operating system ensures compatibility and maximizes performance with updated dependencies. Additionally, reviewing the functions that act upon the controls for the GUI for possible consolidation can streamline the automation code, making it more maintainable and efficient for shorter sprint cycles. These steps align well with transitioning to a more modern, competitive user interface and the iterative nature of Scrum.