Automation Testing Fundamentals
33 Questions
7 Views

Choose a study mode

Play Quiz
Study Flashcards
Spaced Repetition
Chat to lesson

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

Which of the following is an important technical success factor for any significant automation project?

  • The SUT must be self-documenting.
  • The GUI interaction and data must be coupled with the graphical interface.
  • The TAA must be designed for learnability. (correct)
  • The TAA must support the ability to automate all manual tests.
  • Which of the following is considered to be an advantage of test automation over manual testing?

  • The time required for test execution is lengthened and the coverage is reduced.
  • The time required for test execution is shortened and the coverage is reduced.
  • The time required for test execution is shortened and the coverage is increased. (correct)
  • The time required for test execution is lengthened and the coverage is increased.
  • You are working on a test automation project that will automate business scenarios for the user acceptance testers to use when conducting UAT. The business scenarios are well-defined and frequently repeated during UAT. The goal is to also be able to test these same scenarios as part of regression testing by executing the test automation. Structured scripting has already been used to develop the library of functions that can be used by the test automation. What scripting technique should be used to build upon the structured scripting that has already been done and to implement this test automation to meet the business goals?

  • Keyword-driven scripting
  • Process-driven scripting (correct)
  • Linear scripting
  • Scenario-driven scripting
  • When is the best time, for test automation, to consider legal and/or standards requirements of an SUT?

    <p>When designing a TAA</p> Signup and view all the answers

    When designing the test adaptation layer, which of the following should occur?

    <p>Selecting tools that will be used to stimulate and observe test interfaces</p> Signup and view all the answers

    Why is it important for the TAA to separate the test definition from the test execution?

    <p>The test definition can be completed without knowledge of the tool that will be used for execution</p> Signup and view all the answers

    You are working on the design of a test automation project. The gTAA was set up by a consulting company prior to your being hired. You are now looking to create the TAA from the gTAA. You have the following requirements that must be addressed by your TAA:

    1. The TAA must support independence across technologies. It is likely that this same test suite will be used in different test environments and on different target technologies
    2. The test artifacts need to be portable
    3. Vendor-neutrality is preferable
    4. It is vitally important that the TAA be maintainable and maintenance costs be minimized
    5. It is preferred that less technical people be able to maintain the system even though highly technical people have built it
    6. There is a large project budget for this effort for the next two years, but the budget will decrease after that time Given these requirements, which one of the following should the TAE consider during the implementation of the TAA?

    <p>The use of abstraction in the implementation</p> Signup and view all the answers

    Which of the following is an important testability consideration when designing a SUT?

    <p>Controllability</p> Signup and view all the answers

    When a system is designed for testability, one of the characteristics is that the test cases can access interfaces into the system that can be used to verify the expected behavior actually occurred as a result of the test. What is this characteristic called?

    <p>Observability</p> Signup and view all the answers

    You are evaluating functional test automation tools. The tool that you prefer can provide your organization with a favorable cost-benefit ratio, which appeals to senior management. Additionally, you feel the tool is superior in meeting your other technical criteria. However, the tool has many features most of which will never be used. As a result, you feel this makes the tool overly complex and confusing. What should your next steps be regarding selection of this tool?

    <p>Explore the possibility of configuring the tool to turn off unnecessary features</p> Signup and view all the answers

    You have been automating a legacy application that provides critical functionality to the business. An update to the legacy system has been approved and the developers plan to use third party software to provide the new functionality. The third party software has already been tested but the interface between the existing software and the new software is problematic. Your existing test automation needs to be extended to test the interface between these two products. How should you approach implementing the best automation solution?

    <p>Investigate if automation is possible via the APIs used to interface with the third party software</p> Signup and view all the answers

    You are deciding on the functional test automation approach for a highly complex system which is expected to be used in production for many years. You have already conducted a survey with the major tool vendors and you have determined that you will not be able to use any of their tools to create your test automation due to the non-standard interfaces that were required for the software. You and the developers have decided that your best automation approach will be through custom interfaces implemented specifically for testing. What are two concerns you should have with this approach? (Pick 2)

    <p>Because there is a high level of intrusion, there may be false alarms generated</p> Signup and view all the answers

    What layer of the gTAA structure provides tool support for designing manual test cases and creating automated test cases?

    <p>Test Generation Layer</p> Signup and view all the answers

    When publishing a test execution report which key attribute must the report contain?

    <p>Test environment</p> Signup and view all the answers

    What is a stated goal for automated regression test coverage if it is to ascertain the overall quality of the SUT?

    <p>Broad and deep</p> Signup and view all the answers

    Who should provide feedback to the TAE when implementing new features to an existing TAS?

    <p>Test Designers with domain expertise</p> Signup and view all the answers

    Which of the following is the best reason for automating the confirmation testing of a defect?

    <p>To ensure that the fix works and continues to work</p> Signup and view all the answers

    You are having problems with the reliability of the automated test environment and setup. You have decided to create a test suite you can execute to verify the environment before you run the actual test scripts. Which of the following would provide the best quick test of the environment?

    <p>Run a set of tests containing both passes and fails and verify that the results are consistent</p> Signup and view all the answers

    You are testing a system that is updated by monthly service packs. You are testing multiple versions of the SUT simultaneously. Your TAS is complex and you need to ensure it remains consistent across the different SUT environments. How will you ensure that the same version of the TAS is used to test each SUT?

    <p>Install the TAS into the SUT environments from a central repository</p> Signup and view all the answers

    You have executed an automated test suite for a product that was released to production. Although your tests passed, there was a major failure in production in an area that is well covered by your automated tests. You have verified that your tests did pass and that the reporting of the results was correct. What should you do now to verify the validity of your tests?

    <p>Check that the post conditions of each test case are being verified correctly</p> Signup and view all the answers

    You are preparing to execute a test automation suite for a safety critical healthcare application. Which approach should you take to verify the accuracy of the test results?

    <p>Execute test cases with known failures and verify that they continue to fail</p> Signup and view all the answers

    You have been reviewing the test cases in your TAS and have discovered that there is a wide variety of methods the TAES have used to handle system errors. How should you handle this?

    <p>Establish an error recovery process in the TAS and ensure all test cases are using that process</p> Signup and view all the answers

    Up until now you have provided automated testing for a stable SUT. Because of changing business demands, the SUT will be updated to include several new features and plug-ins that communicate via APIs. In what way should you update the TAS?

    <p>Modify the adaptation layer in the TAA to enable the TAS to test via the APIs</p> Signup and view all the answers

    You have been working with a test automation suite that provides good test coverage. The suite contains 500 scripts and has previously run without any problems. Recently, a number of the tests late in the test run have been failing. You have done some analysis and it appears that the test failures are being caused by a SUT failure that is not being detected by one or more tests earlier in the test run. You need more information to pinpoint the test or tests with a false-negative result What type of logging do you need in order to complete your analysis and get the information to help identify the problem?

    1. The status of execution for each test case (pass/fail)
    2. Timing information for each step in each test case
    3. Dynamic information about the SUT
    4. All actions of each test case to allow replaying each test
    5. Failure information for any step in a test case that encounters an error

    <p>1, 4, 5</p> Signup and view all the answers

    You have been asked to distribute the results of your test automation daily. The preferred method for distribution of these results is via e-mail. What is an important characteristic of your test automation reporting that will allow you to provide this information?

    <p>It should integrate with a common third party tool</p> Signup and view all the answers

    When implementing results reporting for test automation, what is a good way to allow the reader to make a quick assessment of the progress of the test execution?

    <p>Traffic lights</p> Signup and view all the answers

    You normally start execution of an automated regression test suite at the end of the workday as it is a lengthy test. Occasionally the test does not complete by the start of the next workday even though it should complete within five hours of starting. What is the most efficient approach you could take to determine the cause of the problem?

    <p>Automate collection of the test execution results</p> Signup and view all the answers

    Your manager is concerned that it will be difficult to assess the success of the test automation implementation unless it is possible to show that the quality of the tested software steadily improves. You have explained that pass/fail numbers are reported at the end of each execution, but your manager wants to see this information provided automatically to a dashboard that will allow drilling down to the details. How can you automatically provide this information from the test automation software?

    <p>The automated testware can be used to report this information to a database and a dashboard can be created from the data in the database that will show the trends in passed/failed test cases</p> Signup and view all the answers

    Why is it important to have standard naming conventions for a TAS?

    <p>A TAS that uses standard names will be easier for a new person to learn</p> Signup and view all the answers

    You have just updated your TAS to include new features. What steps should you take to ensure that the changes have not adversely affected any existing functionality?

    <p>Compare the new and old TAS versions and assess the impact of any differences</p> Signup and view all the answers

    Your team has been working on creating a strong and maintainable TAS. The TAS is expected to be used for at least five years, so good maintainability is critical. The team has done the following: 1. Created an impact analysis process for all proposed changes to the system 2. Documented the usage for the TAS 3. Documented the third party dependencies, including contacts within the third party organization 4. Verified that the TAS runs in an environment separate from the SUT environment Given this information, what is a major factor of maintainability that has not been addressed?

    <p>The TAS must be modular, so key components can be replaced as needed</p> Signup and view all the answers

    You have been asked to conduct a pilot for the test automation tool. You have identified a suitable target project (average size and cost), planned the pilot (treating it as a development effort), and conducted the pilot. What should be your next step?

    <p>Evaluate the results engaging the stakeholders to gather their viewpoints</p> Signup and view all the answers

    Senior management wants to implement test automation into your organization and has asked you to lead this initiative. The organization has a number of systems of varying criticality, some of which may benefit from automation once a TAA is mature. You have been given direction to start with a pilot. How do you select a suitable project for the TAS?

    <p>A non-critical project in order to mitigate any delays the TAS may cause</p> Signup and view all the answers

    Study Notes

    • Document details
      • Number: 000-000
      • Passing Score: 800
      • Time Limit: 120 min
      • File Version: 1.0
      • Note: Title is missing

    Technical Success Factor for Automation

    • Question 1: An important factor for automation projects is learnability.
    • Explanation: Automation should be designed for ease of learning, maintainability, and high performance.

    Test Automation Advantages

    • Question 2: Test automation shortens test execution time while increasing coverage.
    • Explanation: Compared to manual testing, test automation leads to faster test execution with more comprehensive testing coverage.

    Scripting Techniques for Business Scenarios

    • Question 3: Use process-driven scripting to build upon structured scripting for user acceptance testing (UAT) and regression testing.
    • Explanation: Process-driven scripting excels at utilizing existing structured scripts while focusing on specific business scenarios required for user acceptance testing and regression testing. This approach is adaptable for different testing contexts and testing phases.

    Considerations for Test Adaptation Layer

    • Question 5: When designing a test adaptation layer, choose tools that will be used to stimulate and observe test interfaces.
    • Explanation: Selecting the tools for stimulus and observation of test interfaces is a key consideration in test adaptation layer design.

    Separating Test Definition and Execution

    • Question 6: Separating test definition from test execution improves the speed of the test, which also allows testing with diverse tools and interfaces.
    • Explanation: Decoupling definition from execution benefits from increased adaptability, allowing tests to work effectively with different testing tools.

    Testability Considerations for SUT Design

    • Question 8: An important design consideration for System Under Test (SUT) is controllability.
    • Explanation: Controllability is a key factor in system design from a testability perspective.

    Observability as a Testability Factor

    • Question 9: Systems designed for testability should have observable characteristics; this means test cases can access interfaces that verify expected behaviors.
    • Explanation: Observability is the characteristic of testable systems that allows test cases to check whether the expected behavior is accomplished via system interactions, or access to the system results.

    Simplifying Test Automation Tools

    • Question 10: If a test automation tool has many unused features, consider configuring it to disable unnecessary features.
    • Explanation: Simplify the tool's interface to gain higher efficiency and effectiveness by disabling the unnecessary tool features.

    Implementing Automation for New Third-Party Software Interfaces

    • Question 7: To implement test automation for a legacy system that interacts with new third-party software, investigate if API automation is possible first.
    • Explanation: In cases like this, identifying and leveraging APIs to connect to the new software could significantly simplify the integration of automation.

    Concerns about Custom Testing Interfaces

    • Question 12: Two primary concerns about a custom interface approach for testing include security risks if the interfaces are not disabled and there is a potential discrepancy in testing versus actual system performance.
    • Explanation: These concerns emphasize the importance of assessing and mitigating potential risks associated with custom interfaces for testing.

    Testing a Stable Production System

    • Question 13: Use the Test Generation Layer to support the design of both manual and automated test cases when performing test automation on a stable production system.
    • Explanation: Using the Test Generation Layer (gTAA structure) for test automation on a stable production system effectively uses a structured and well-defined approach.

    Essential Attributes of a Test Execution Report

    • Question 14: Test environment information is mandatory for test execution reports.
    • Explanation: Test environment data is important to determine the test coverage and validity. It allows replicating the execution in cases where the outcome is needed again.

    Testing for Test Automation Stability

    • Question 15: The biggest issue in testing a two-year-old production system using automation is the constantly changing test data.
    • Explanation: Frequent updates to test data can make maintaining automated test cases complex for a stable production setup.

    Automation Script Basis

    • Question 16: Manual test cases are the typical foundation for automated test scripts.
    • Explanation: Manual test cases provide details on test steps and expected outcomes facilitating the translation to more automated test scripts.

    Comprehensive Regression Test Coverage

    • Question 17: The goal for automated regression testing to ascertain overall quality is comprehensive test coverage.
    • Explanation: Comprehensive coverage emphasizes finding faults (both widely spread and detailed) in the software to improve the quality of the SUT.

    Stakeholder Feedback for TAS Feature Enhancement

    • Question 18: Test designers with domain expertise should provide feedback on TAS feature enhancement.
    • Explanation: Test designers with specialized knowledge are the best choice for providing in-depth insights about the TAS.

    Automating Defect Confirmation

    • Question 19: The primary use case for automating defect confirmation is to ensure the fix works and maintains functionality.
    • Explanation: This focus verifies the integrity of the fix without further error introduction.

    Effective Environment Verification Testing

    • Question 20: Running tests that include both successful and failed test cases provides quick and effective ways to accurately verify that the environment is consistent.
    • Explanation: It's a more comprehensive approach for environment verification.

    Ensuring Consistent TAS Version

    • Question 21: Install the TAS from a central repository across multiple SUT environments to ensure consistency in testing version.
    • Explanation: Using a central repository for TAS installation ensures that testing environments utilize the same version; this is a crucial design aspect.

    Verification of Test Accuracy for Safety-Critical Systems

    • Question 23: To verify the accuracy of test results for a safety-critical application (SUT), execute test cases with known failures; verify that the failures recur correctly.
    • Explanation: This method ensures reliable identification of failures, crucial for safety applications where accuracy is paramount.

    Standardized Error Recovery Processes in TAS

    • Question 24: Create and enforce an error recovery process in the automation system to ensure uniform and consistent handling of errors in test cases.
    • Explanation: Standardization in error handling processes is crucial for maintaining consistent behavior and integrity across testing scenarios.

    Updating Test Automation for API Functionality Changes

    • Question 25: Update the TAS's adaptation layer to integrate with APIs when the SUT changes to include external API communication and functionalities.
    • Explanation: The most effective approach updates/adapts the TAS core (the Test Automation Framework) to directly support the APIs in the System Under Test.

    Efficiency Improvements for a Multi-Year TAS

    • Question 26: Utilize the latest libraries in your Test Automation System (TAS) to improve performance and efficiency.
    • Explanation: The latest libraries often include optimized versions with improved functionalities and performance. This approach helps improve system efficiency and stability by ensuring the latest technology is incorporated.

    Logging for Identifying Unexpected Test Failures

    • Question 27: To pinpoint false negatives or discrepancies in test results, record detailed test case statuses, timing information, and dynamic information related to the SUT. Logging should include the step-by-step execution of test cases and record failed steps.
    • Explanation: These types of logging features help identify inconsistencies and areas of failure and allow tracing results.

    Daily Report Distribution for Test Automation

    • Question 28: The key characteristic for daily distribution of test automation reports is integration with a common third-party tool.
    • Explanation: This centralized method facilitates automated report generation and distribution to stakeholders.

    Rapid Progress Assessment for Test Execution

    • Question 29: Traffic light indicators offer a quick assessment of test execution progress, demonstrating success or failure at a glance.
    • Explanation: Simple visual indicators like traffic lights efficiently convey progress, making assessment quick and direct.

    Determining the Cause of Delayed Regression Test Execution

    • Question 30: Automate the collection of test execution results to identify the causes of delayed regression testing.
    • Explanation: This structured approach is efficient for pinpointing issues during lengthy tests.

    Dashboards for Trend Tracking in Test Automation

    • Question 31: Test automation tools should export test execution results to a database enabling the creation of a dashboard for tracking trends in successful/unsuccessful test runs.
    • Explanation: A dashboard with trends is better than simply recording pass/fail results; it effectively visualizes issues over time, making it easier to assess trends.

    Importance of Standard Naming Conventions in TAS

    • Question 32: Use of standard naming conventions in a Test Automation System (TAS) makes the system more understandable to new team members.
    • Explanation: Consistent naming significantly improves readability and comprehension within the TAS.

    Verifying Existing Functionality After TAS Updates

    • Question 33: Compare the new and old versions of the Test Automation System (TAS) to evaluate the impact of any changes on existing functionality after new features are introduced. This is a crucial step in maintaining the integrity of existing functionalities.
    • Explanation: This approach proactively prevents regressions caused by new features and helps identify possible issues early in the process.

    Maintaining Maintainability in Test Automation Systems (TAS)

    • Question 34: A critical factor for TAS maintainability is making the TAS modular, enabling replacing individual components when needed.
    • Explanation: Modular design allows for easier updates and maintenance over time.

    Using a Non-Critical Project for Pilot TAS Implementation

    • Question 35: Choose a non-critical project to conduct a pilot for the test automation system, which ensures there is no risk to other critical projects during the initial evaluation.
    • Explanation: This is a crucial practice when introducing new testing systems.

    Studying That Suits You

    Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

    Quiz Team

    Description

    This quiz assesses your understanding of key concepts in automation testing, including the importance of learnability and the advantages of test automation. It also explores scripting techniques applicable to various business scenarios. Test your knowledge and improve your skills in this essential area of software development.

    More Like This

    Use Quizgecko on...
    Browser
    Browser