This is the chapter 2 of ISTQB Advance Test Automation Engineer certification. This presentation helps aspirants understand and prepare content of certification.
This is chapter 3 of ISTQB Advance Agile Technical Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 3 of ISTQB Advance Technical Test Analyst certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 2 of ISTQB Advance Agile Technical Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 5 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 4 of ISTQB Specialist Mobile Application Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 1 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 1 - The Technical Test Analyst Tasks in Risk Based TestingNeeraj Kumar Singh
This is chapter 1 of ISTQB Advance Technical Test Analyst certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 6 of ISTQB Advance Technical Test Analyst certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 1 of ISTQB Advance Agile Technical Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Tool Support for Testing as Chapter 6 of ISTQB Foundation 2018. Topics covered are Tool Benefits, Test Tool Classification, Benefits of Test Automation, Risk of Test Automation, Selecting a tool for Organization, Pilot Project, Success factor for using a tool
Chapter 4 - Quality Characteristics for Technical TestingNeeraj Kumar Singh
The document discusses quality characteristics for technical testing, focusing on reliability testing. It provides definitions and explanations of reliability sub-characteristics like maturity, fault tolerance, and recoverability. It describes approaches to measuring software maturity and reliability over time. Types of reliability tests discussed include fault tolerance testing, recoverability (failover and backup/restore) testing, and availability testing. General guidance is provided on planning and specifying reliability tests, noting the need for production-like environments and long test durations to obtain statistically significant results.
This is chapter 2 of ISTQB Advance Technical Test Analyst certification. This presentation helps aspirants understand and prepare the content of the certification.
This is a free module from my course ISTQB CTAL Technical Test Analyst revised to 2012 syllabus. If you need full training feel free to contact me by email (amraldo@hotmail.com) or by mobile (+201223600207).
This is chapter 6 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 5 of ISTQB Advance Technical Test Analyst certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 5 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
Test Management as Chapter 5 of ISTQB Foundation 2018. Topics covered are Test Organization, Test Planning and Estimation, Test Monitoring and Control, Test Execution Schedule, Test Strategy, Risk and Testing, Defect Management
This is chapter 3 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
This document discusses Agile testing tools. It covers task management tools, software build tools, configuration management tools, test design tools, communication tools, and cloud/virtualization tools. Task management tools help track user stories and tasks throughout sprints. Build tools enable daily builds. Configuration management tools store code and tests. Test design tools help automate testing. Communication tools like wikis and chat support collaboration. Cloud/virtualization tools provide flexible testing environments.
The document discusses software test automation. It defines software test automation as activities that aim to automate tasks in the software testing process using well-defined strategies. The objectives of test automation are to free engineers from manual testing, speed up testing, reduce costs and time, and improve quality. Test automation can be done at the enterprise, product, or project level. There are four levels of test automation maturity: initial, repeatable, automatic, and optimal. Essential needs for successful automation include commitment, resources, and skilled engineers. The scope of automation includes functional and performance testing. Functional testing is well-suited for automation of regression testing. Performance testing requires automation to effectively test load, stress, and other non-functional requirements
This is chapter 4 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This document discusses automation testing. It begins by defining automation testing and listing its benefits, which include saving time and money, improving accuracy, and increasing test coverage. It then covers levels of automation testing, frameworks, approaches like record and playback, modular scripting, and keyword-driven testing. The document also discusses the automation testing lifecycle, how to choose a testing tool, types of tools, when to automate and who should automate, supporting practices, and skills needed for automation testing.
This document discusses factors that can lead to automation failures and provides guidance on how to avoid them. It identifies issues like poor test case selection, script failures, lack of maintenance, and poor planning/estimation. It also provides tips for proper analysis when selecting test automation candidates and determining what to automate first. The document advises choosing the right automation tool and framework based on factors like project size. It categorizes common script failure areas and stresses the importance of maintenance and streamlined processes. Finally, it emphasizes estimating efforts based on test complexity, framework needs, and maintenance/execution times.
This document describes the testing plan and strategy for a project with ID 32. It discusses various types of testing conducted, including unit testing, integration testing, system testing, performance testing, and statistical testing. Test cases are provided for paying fees, new admission, and enrolment modules. The test cases specify test conditions, expected outputs, actual outputs, and whether each test passed or failed.
This document discusses best practices for developing an automated testing framework. It recommends using a hybrid keyword-driven and data-driven approach to reduce scripting efforts. Some key points covered include the benefits of automation like reduced costs and increased speed/accuracy over manual testing. It also discusses factors to consider when selecting an automation tool, common challenges, and provides an example case study showing the ROI achieved through automation. Best practices emphasized include loose coupling of framework components, reuse of generic libraries, and treating framework development as a distinct project.
Chapter 2 - Testing Throughout the Development LifeCycleNeeraj Kumar Singh
The document discusses testing throughout the software development life cycle. It describes different software development models including sequential, incremental, and iterative models. It also covers different test levels from component and integration testing to system and acceptance testing. The document discusses different types of testing including functional and non-functional testing. It also covers topics like maintenance testing and triggers for additional testing when changes are made.
Manual testing requires testers to cycle through the data continuously, utilize various input combinations, record observations, and compare outcomes to intended behavior. Automated testing leveraging test data automation accelerates all of these operations, and testing teams may execute automated tests across many operating systems and hardware setups using a single tool.
System testing evaluates a complete integrated system to determine if it meets specified requirements. It tests both functional and non-functional requirements. Functional requirements include business rules, transactions, authentication, and external interfaces. Non-functional requirements include performance, reliability, security, and usability. There are different types of system testing, including black box testing which tests functionality without knowledge of internal structure, white box testing which tests internal structures, and gray box testing which is a combination. Input, installation, graphical user interface, and regression testing are examples of different types of system testing.
This document discusses software test automation, including that it is used to automate test case execution and comparison of actual vs expected outcomes using specialized tools. It describes key aspects like test automation tools, frameworks, automated test scripts, regression testing, integration with CI/CD pipelines, and test data management. Benefits of automation include efficiency, accuracy, cost-effectiveness, and reusability. However, not all tests are suitable for automation. The software test automation market report provides regional analysis including countries in North America, Europe, Asia-Pacific, South America, and the Middle East and Africa. It also provides a link to purchase the full software test automation market report.
A Study Of Automated Software Testing Automation Tools And FrameworksTony Lisko
This document provides a summary of automated software testing, including categories of test automation tools, frameworks for test automation, and comparisons of popular automation tools. It discusses the growing demand for high-quality software delivered quickly and how test automation is important for meeting this demand. Automated testing can improve accuracy, save time and effort compared to manual testing. The document categorizes common automation tool types and discusses popular tools within each category. It also describes various test automation frameworks and their benefits. Finally, it briefly explains and compares some commonly used automation tools.
Software testing and introduction to qualityDhanashriAmbre
The document provides an overview of software testing and quality assurance. It defines software testing as a process to investigate quality and find defects between expected and actual results. Testing is necessary to ensure software is defect-free per customer specifications and increases reliability. The document then discusses types of errors like ambiguous specifications, misunderstood specifications, and logic/coding errors. It outlines the software development life cycle including phases like planning, analysis, design, coding, testing, implementation, and maintenance. Each phase is described in 1-2 sentences.
The summary provides an overview of the key elements of a software test plan template, including:
1. An introduction section that describes the testing strategy and objectives.
2. A section on test items that identifies the modules, procedures, and documentation to be tested.
3. A section on the testing approach that describes the types of testing to be performed like component, integration, and acceptance testing.
4. Sections on pass/fail criteria, the testing process, environmental requirements, change management, and plan approvals.
Integration testing is the phase in software testing in which individual software modules are combined and tested as a group. Read complete guide of integration testing types and tools here.
Challenges in automation which testers face often lead to subsequent failures. Learn how to respond to these common challenges by developing a solid business case for increased automation adoption by engaging manual testers in the testing organization, being technology agnostic, and stabilizing test scripts regardless of applications changes.
What are the Key drivers for automation? What are the Challenges in Agile automation and How to deal with them? How to automate? Who will automate? Which tool to select? Commercial or open source? What to automate? Which features? Here is what our experience says
This test plan outlines the strategy for testing the IIT official website. It will validate major system functions against customer requirements. Key areas to be tested include adding/modifying content like news, programs, courses and profiles. High priority will be given to functionality critical for users like logging in, downloading documents and maintaining attendance. The plan details the test items, approach, risks, and responsibilities to help ensure the website meets its objectives.
Tool Support for Testing as Chapter 6 of ISTQB Foundation 2018. Topics covered are Tool Benefits, Test Tool Classification, Benefits of Test Automation and Risk of Test Automation
Test Management as Chapter 5 of ISTQB Foundation. Topics covered are Test Organization, Test Planning and Estimation, Test Monitoring and Control, Test Execution Schedule, Test Strategy, Risk Management, Defect Management
Test Case Design Techniques as chapter 4 of ISTQB Foundation. Topics included are Equivalence Partition, Boundary Value Analysis, State Transition Testing, Decision Table Testing, Use Case Testing, Statement Coverage, Decision Coverage, Error Guessing, Exploratory Testing, Checklist Based Testing
Chapter 3 of ISTQB Foundation 2018 syllabus with sample questions. Answers about what is static testing, what is review, types of review, informal review, walkthrough, technical review, inspection.
The document discusses testing throughout the software development life cycle. It describes different software development models including sequential, incremental, and iterative models. It also covers different test levels from component and integration testing to system and acceptance testing. The document discusses different types of testing including functional and non-functional testing. It also covers topics like maintenance testing and triggers for additional testing when changes are made. Also covers concepts of Agile including DevOps, Shift Left Approach, TDD, BDD, ATDD, Retrospective and Process Improvement
The document discusses fundamentals of software testing including definitions of testing, why testing is necessary, seven testing principles, and the test process. It describes the test process as consisting of test planning, monitoring and control, analysis, design, implementation, execution, and completion. It also outlines the typical work products created during each phase of the test process.
Chapter 4 - Mobile Application Platforms, Tools and EnvironmentNeeraj Kumar Singh
This is chapter 4 of ISTQB Specialist Mobile Application Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 3 - Common Test Types and Test Process for Mobile ApplicationsNeeraj Kumar Singh
This is chapter 3 of ISTQB Specialist Mobile Application Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 2 of ISTQB Specialist Mobile Application Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 1 - Mobile World - Business and Technology DriversNeeraj Kumar Singh
This is chapter 1 of ISTQB Specialist Mobile Application Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is a Sample Question Paper of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is the answer to Sample Questions of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
ISTQB Performance Tester Certification Syllabus and Study MaterialNeeraj Kumar Singh
This is Syllabus of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 3 - Performance Testing in the Software LifecycleNeeraj Kumar Singh
The document discusses performance testing activities across different software development lifecycles. It describes how performance testing should be conducted iteratively throughout sequential development models, with testing at each stage from concept to acceptance. For iterative models, performance testing is also iterative and can be part of continuous integration. Specific activities discussed include test planning, monitoring, analysis, design, implementation, execution and completion. Performance risks are also discussed for different architectures.
This is chapter 2 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 7 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 4 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 2 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
The document summarizes the key activities in the software testing process according to ISTQB, including test planning, monitoring and control, analysis, design, implementation, execution, evaluating exit criteria and reporting, and test closure activities. It provides details on each activity, such as the objectives of test planning, factors to consider for test analysis, and outputs that should be captured during test closure.
ISTQB Technical Test Analyst Answers to Sample Question PaperNeeraj Kumar Singh
Here are the answers and justification for the sample question paper for ISTQB Advance Technical Test Analyst for certification preparation. This is a standard paper from ISTQB.
Intel Unveils Core Ultra 200V Lunar chip .pdfTech Guru
Intel has made a significant breakthrough in the world of processors with the introduction of its Core Ultra 200V mobile processor series, codenamed Lunar Lake. This innovative processor marks a fundamental shift in the way Intel creates processors, with a high degree of aggregation, including memory-on-package (MoP). The Core Ultra 300 MX series is designed to power thin-and-light devices that are capable of handling the latest AI applications, including Microsoft's Copilot+ experiences.
Smart mobility refers to the integration of advanced technologies and innovative solutions to create efficient, sustainable, and interconnected transportation systems. It encompasses various aspects of transportation, including public transit, shared mobility services, intelligent transportation systems, electric vehicles, and connected infrastructure. Smart mobility aims to improve the overall mobility experience by leveraging data, connectivity, and automation to enhance safety, reduce congestion, optimize transportation networks, and minimize environmental impacts.
Top 12 AI Technology Trends For 2024.pdfMarrie Morris
Technology has become an irreplaceable component of our daily lives. The role of AI in technology revolutionizes our lives for the betterment of the future. In this article, we will learn about the top 12 AI technology trends for 2024.
"Hands-on development experience using wasm Blazor", Furdak Vladyslav.pptxFwdays
I will share my personal experience of full-time development on wasm Blazor
What difficulties our team faced: life hacks with Blazor app routing, whether it is necessary to write JavaScript, which technology stack and architectural patterns we chose
What conclusions we made and what mistakes we committed
Connector Corner: Leveraging Snowflake Integration for Smarter Decision MakingDianaGray10
The power of Snowflake analytics enables CRM systems to improve operational efficiency, while gaining deeper insights into closed/won opportunities.
In this webinar, learn how infusing Snowflake into your CRM can quickly provide analysis for sales wins by region, product, customer segmentation, customer lifecycle—and more!
Using prebuilt connectors, we’ll show how workflows using Snowflake, Salesforce, and Zendesk tickets can significantly impact future sales.
Connector Corner: Leveraging Snowflake Integration for Smarter Decision Making
Chapter 2 - Preparing for Test Automation
1. Preparing for Test Automation
1 Introduction to
Test Automation
2 Preparing for
Test Automation
3 gTAA
Software Testing - ISTQB Advance
Test Automation Engineer Exam Preparation
Chapter 2
Neeraj Kumar Singh
5 Reporting
& Metrics
6 Transitioning
Manual to Automation
7 Verifying TAS
8 Continuous
Improvement
4 Risks &
Contingencies
2. Preparing for Test Automation
Contents
2.1 SUT Factors Influencing Test Automation
2.2 Tool Evaluation and Selection
2.3 Design for Testability and Automation
Neeraj Kumar Singh
3. Preparing for Test Automation
SUT Factors Influencing Test Automation
When evaluating the context of the SUT and its environment, factors that influence test automation
need to be identified to determine an appropriate solution. These may include the following:
SUT interfaces - The automated test cases invoke actions on the SUT. For this, the SUT must provide
interfaces via which the SUT can be controlled. This can be done via UI controls, but also via lower-
level software interfaces.
Third party software - Often the SUT not only consists of software written in the home organization
but may also include software provided by third parties.
Levels of intrusion - Different test automation approaches (using different tools) have different
levels of intrusion. The greater the number of changes that are required to be made to the SUT
specifically for automated testing, the higher the level of intrusion.
Different SUT architectures - Different SUT architectures may require different test automation
solutions.
Size and complexity of the SUT - Consider the size and complexity of the current SUT and plans for
future development.
Neeraj Kumar Singh
4. Preparing for Test Automation
SUT Factors Influencing Test Automation
Several factors described here are known (e.g., size and complexity, available software interfaces)
when the SUT is already available, but most of the time the development of the test automation
should start before the SUT is available. When this happens several things need to be estimated or
the TAE can specify the software interfaces that are needed.
Even when the SUT does not yet exist, test automation planning can start. For example:
When the requirements (functional or non-functional) are known, candidates for automation can be selected
from those requirements together with identifying the means to test them. Planning for automation can begin
for those candidates, including identifying the requirements for the automation and determining the test
automation strategy.
When the architecture and technical design is being developed, the design of software interfaces to support
testing can be undertaken.
Neeraj Kumar Singh
5. Preparing for Test Automation
1 Introduction to
Test Automation
2 Preparing for
Test Automation
3 gTAA
Software Testing - ISTQB Advance
Test Automation Engineer Exam Preparation
Chapter 2
Neeraj Kumar Singh
5 Reporting
& Metrics
6 Transitioning
Manual to Automation
7 Verifying TAS
8 Continuous
Improvement
4 Risks &
Contingencies
6. Preparing for Test Automation
Contents
2.1 SUT Factors Influencing Test Automation
2.2 Tool Evaluation and Selection
2.3 Design for Testability and Automation
Neeraj Kumar Singh
7. Preparing for Test Automation
Tool Evaluation and Selection
The primary responsibility for the tool selection and evaluation process belongs with the Test Automation
Manager (TAM). However the TAE will be involved in supplying information to the TAM and conducting
many of the evaluation and selection activities.
The TAE will be involved throughout the tool evaluation and selection process but will have particular
contributions to make to the following activities:
Assessing organizational maturity and identification of opportunities for test tool support
Assessing appropriate objectives for test tool support
Identifying and collecting information on potentially suitable tools
Analyzing tool information against objectives and project constraints
Estimating the cost-benefit ratio based on a solid business case
Making a recommendation on the appropriate tool
Identifying compatibility of the tool with SUT components
Neeraj Kumar Singh
8. Preparing for Test Automation
Tool Evaluation and Selection
Functional test automation tools frequently cannot meet all the expectations or the situations that are
encountered by an automation project. The following is a set of examples of these types of issues (but it
is definitely not a complete list):
Neeraj Kumar Singh
Findings Examples Possible Solutions
The tool’s interface does not work
with other tools that are already in
place
• The test management tool has
been updated and the connecting
interface has changed
• The information from pre-sales
support was wrong and not all
data can be transferred to the
reporting too
• Pay attention to the release notes
before any updates, and for big
migrations test before migrating to
production
• Try to gain an onsite demonstration
of the tool that uses the real SUT
• Seek support from the vendor
and/or user community forums
Object on GUI could not be captured • The object is visible but the test
automation tool cannot interact
with it
• Try to use only well-known
technologies or objects in
development
• Do a pilot project before buying a
test automation tool
• Have developers define standards
for objects
9. Preparing for Test Automation
Tool Evaluation and Selection
Neeraj Kumar Singh
Findings Examples Possible Solutions
Tool looks very complicated • The tool has a huge feature set but
only part of that will be used
• Try to find a way to limit the
feature set by removing unwanted
features from the tool bar
• Select a license to meet your needs.
• Try to find alternative tools that are
more focused on the required
functionality.
Conflict with other systems • After installation of other software
the test automation tool will not
work anymore or vice versa
• Read the release notes or technical
requirements before installing.
• Get confirmation from the supplier
that there will be no impact to
other tools.
• Question user community forums.
Impact on the SUT • During/after use of the test
automation tool the SUT is reacting
differently (e.g., longer response
time)
• Use a tool that will not need to
change the SUT (e.g., installation of
libraries, etc.)
Access to code • The test automation tool will
change parts of the source code
• Use a tool that will not need to
change the source code (e.g.,
installation of libraries, etc.)
10. Preparing for Test Automation
1 Introduction to
Test Automation
2 Preparing for
Test Automation
3 gTAA
Software Testing - ISTQB Advance
Test Automation Engineer Exam Preparation
Chapter 2
Neeraj Kumar Singh
5 Reporting
& Metrics
6 Transitioning
Manual to Automation
7 Verifying TAS
8 Continuous
Improvement
4 Risks &
Contingencies
11. Preparing for Test Automation
Contents
2.1 SUT Factors Influencing Test Automation
2.2 Tool Evaluation and Selection
2.3 Design for Testability and Automation
Neeraj Kumar Singh
12. Preparing for Test Automation
Design for Testability and Automation
SUT testability (availability of software interfaces that support testing e.g., to enable control and
observability of the SUT) should be designed and implemented in parallel with the design and
implementation of the other features of the SUT.
Design for testability consists of several parts:
Observability: The SUT needs to provide interfaces that give insight into the system. Test cases can
then use these interfaces to check, for example, whether the expected behavior equals the actual
behavior.
Control(ability): The SUT needs to provide interfaces that can be used to perform actions on the
SUT. This can be UI elements, function calls, communication elements (e.g., TCP/IP or USB
protocol), electronic signals (for physical switches), etc.
Clearly defined architecture: The third important part of design for testability is an architecture
that provides clear and understandable interfaces giving control and visibility on all test levels.
The TAE considers ways in which the SUT can be tested, including automated testing, in an effective
(testing the right areas and finding critical bugs) and efficient (without taking too much effort) way.
Neeraj Kumar Singh
13. Preparing for Test Automation
Design for Testability and Automation
Some examples of software interfaces that support testing include:
The powerful scripting capabilities of modern spreadsheets.
Applying stubs or mocks to simulate software and/or hardware (e.g., electronic financial
transactions, software service, dedicated server, electronic board, mechanical part) that is not yet
available or is too expensive to buy, allows testing of the software in the absence of that specific
interface.
Software interfaces (or stubs and drivers) can be used to test error conditions.
State transition testing is used to evaluate the state behavior of the SUT. A way to check whether the
SUT is in the correct state is by querying it via a customized software interface designed for this
purpose
Design for automation should consider that:
Compatibility with existing test tools should be established early on.
The issue of test tool compatibility is critical in that it may impact the ability to automate tests of
important functionality (e.g., incompatibility with a grid control prevents all tests using that control).
Solutions may require development of program code and calls to APIs
Neeraj Kumar Singh
14. Preparing for Test Automation
1 Introduction to
Test Automation
2 Preparing for
Test Automation
3 gTAA
Software Testing - ISTQB Advance
Test Automation Engineer Exam Preparation
Chapter 2
Neeraj Kumar Singh
5 Reporting
& Metrics
6 Transitioning
Manual to Automation
7 Verifying TAS
8 Continuous
Improvement
4 Risks &
Contingencies
15. Preparing for Test Automation
Sample Questions
1. 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?
Answer Set
a. Develop test automation for the entire system including the legacy and third party applications
b. Investigate if automation is possible via the APIs used to interface with the third party software
c. Develop new automation to test via the GUI of the third party software
d. Investigate if automation can be implemented using the CLI to replace the existing GUI automation
Neeraj Kumar Singh
16. Preparing for Test Automation
Sample Questions
2. 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?
Answer Set
a. Consider another tool that is more user friendly
b. Explore the possibility of configuring the tool to turn off unnecessary features
c. Plan to supplement selection of this tool with lengthy and comprehensive training sessions
d. Consider acquiring an additional tool that can provide a more user friendly interface to the
preferred tool
Neeraj Kumar Singh
17. Preparing for Test Automation
Sample Questions
3. 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?
Answer Set
a. Observability
b. Controllability
c. Maintainability
d. Interoperability
Neeraj Kumar Singh
Editor's Notes
Consider a device with an internal hard disk drive (HDD). The software controlling this HDD (called a driver) should be tested for failures or wear of the HDD. Doing this by waiting for a HDD to fail is not very efficient (or reliable). Implementing software interfaces that simulate defective or slow HDDs can verify that the driver software performs correctly (e.g., provides an error message, retries).
Alternative software interfaces can be used to test an SUT when no UI is available yet (and this is often considered to be a better approach anyway). Embedded software in technical systems often needs to monitor the temperature in the device and trigger a cooling function to start when the temperature rises above a certain level. This could be tested without the hardware using a software interface to specify the temperature.