C

A 30-60-90-Day Plan for QA Leaders

Implement software test automation

eBook
Introduction
Quality assurance (QA) in software testing is pivotal in today’s
world, where the demand for rapid and reliable software solutions
is ever-increasing. New software releases, updates, and features
launch daily, and end-users expect these offerings to be bug-free,
user-friendly, and dependable. In the competitive landscape of the
software industry, testing is not just a phase; it is a mission-critical
function.

The role of a software tester has evolved over the years. Testers
are no longer solely responsible for manual testing; they are
now instrumental in championing automation, which is the key
to accelerating testing processes, increasing test coverage, and
ensuring high-quality software.

This eBook presents a comprehensive 30-60-90-day automation

plan for QA leaders looking to champion an automation strategy for
their teams. The following chapters outline the steps a QA manager
should take to successfully implement automation in today’s
software development landscape.

A 30-60-90-Day Plan for QA Leaders | 2

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

Contents

CHAPTER 1 CHAPTER 2 CHAPTER 3

The Role of a QA Leader in Today’s Implementing a 90-day Plan for Day 91 and Beyond – Scaling and
Software Landscape Automation Success Optimizing Automation

GO TO CHAPTER 1 > GO TO CHAPTER 2 > GO TO CHAPTER 3 >

CHAPTER 4 CHAPTER 5 CHAPTER 6

Adopting Today’s Automation Trends The Ongoing Journey of Automation Embracing the Future of Automation
Implementation

GO TO CHAPTER 4 > GO TO CHAPTER 5 > GO TO CHAPTER 6 >

A 30-60-90-Day Plan for QA Leaders | 3

CHAPTER 1

The Role of
a QA Leader
in Today’s
Software
Landscape

A 30-60-90-Day Plan for QA Leaders | 4

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

CHAPTER 1

The Role of a QA Leader in

Today's Software Landscape
Before we dive into the intricacies of a 30-60-90-day automation plan, it
is necessary to underscore the pivotal role of a QA leader.

With the rise of agile methodologies, continuous integration, and

DevOps practices, the demand for rapid and high-quality software
development has reached unprecedented levels. As such, QA
leaders are responsible for maintaining traditional testing practices
and spearheading automation initiatives that align with the agile
development philosophy.

QA leaders ensure software meets its functional and non-functional

requirements while keeping pace with rapid development cycles. They
must strike a balance between thorough testing and the need for quick
releases. This dynamic environment is ideal for automation, which offers
a solution to the challenges of speed and quality.

A 30-60-90-Day Plan for QA Leaders | 5

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

QA leaders are today's automation
champions

Automation is the cornerstone of efficient testing in modern

software development. Manual testing alone is insufficient to meet
the demands of agile development and continuous delivery. QA
teams can significantly expedite testing by automating repetitive
and time-consuming tasks. Automation lends itself to improved test
coverage as it executes many test cases in a fraction of the time it
would take manually.

In addition, automation ensures consistent testing, reducing the

potential for human error. It allows for continuous testing throughout
the software development life cycle (SDLC), making it an integral
part of DevOps pipelines. Integrating new code at the same time as
automated tests deploy enables you to offer immediate feedback
to development teams. By doing so, you can catch defects early,
reducing the cost and effort required to fix them.

A 30-60-90-Day Plan for QA Leaders | 6

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

Of course, while automation enhances efficiency, it does not replace the critical role of human QA professionals. Testers’ unique ability to think
creatively, design complex test scenarios, and apply domain knowledge ensures that QA professionals will always play a key role in maintaining the
overall quality and user satisfaction of software products. Moreover, the use of automation empowers testers to focus on higher-value tasks, enabling
them to engage in strategic test planning, exploratory testing, and continuous improvement initiatives.

The Automation Advantage

Automation in software testing is not just a trend but a necessity. In a world where software development is moving at breakneck speed, automation
is the key to keeping up with the pace while maintaining the highest quality standards. Here are some reasons why automation is so important for
software testing:

1. Speed and efficiency: Automated tests can execute quickly 5. Early detection of defects: Automated tests can identify defects
and repeatedly, enabling rapid feedback to developers. Speed early in development, making them cheaper and easier to fix.
is essential in agile and continuous integration / continuous 6. Resource savings: Automated testing can reduce the time and effort
deployment (CI / CD) environments. required for testing, enabling QA teams to focus on more complex
2. Consistency: Automation ensures consistent test performance, and exploratory testing tasks.
reducing the risk of human error and providing reliable results. 7. Parallel testing: Automation enables the execution of tests in
3. Reusability: Automation enables the reuse of automated test parallel across different environments and configurations,
scripts for regression testing, reducing the effort required for improving efficiency.
each new release. 8. Continuous testing: Automation seamlessly integrates with CI / CD
4. Improved test coverage: Automation allows you to cover many pipelines, ensuring that tests run automatically with every
test scenarios, including edge cases and large data sets, which code change.
might be impractical to test manually.

As a QA manager, understanding these benefits and advocating for automation within your organization is crucial to your role. Now, let’s delve into a
30-60-90-day automation plan to help you successfully implement automation in your software testing processes.

A 30-60-90-Day Plan for QA Leaders | 7

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

CHAPTER 2

Implementing
a 90-day Plan
for Automation
Success

A 30-60-90-Day Plan for QA Leaders | 8

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

CHAPTER 2

Implementing a 90-day Plan for Automation Success

The First 30 Days

Day 1 – 10: Assess the current state of testing Day 11 – 20: Define your automation strategy

Take the time upfront to understand your existing test cases so you can Decide what percentage of your test cases you want to automate. They
identify which are the best candidates for automation. Prioritize test will not all be candidates. Many organizations start in the 20 - 30% range
cases based on their importance and frequency of execution. for functional testing. The percentage will increase as teams become more
comfortable with automation tools and processes.

Tasks:
Tasks:
√ List the operating systems and device families you need to
test. Depending on the application and your user base, this can √ Consider your software environment. Agile and DevOps
determine what types of tests you want to automate. environments often aim for 70 to 85% of functional test
√ Identify the tests most critical to your application and those automation. More high-risk environments will aim for 40 to 60%
that require the most manual effort. For example, highly of functional test automation.
complex tests such as visual verification can be the most time- √ Define specific automation objectives, such as reducing testing
consuming. cycle time, improving test coverage, and enhancing test
√ Examine which tests are most sensitive to risk. Any manually reliability. Each objective should contribute to improving overall
performed tasks are vulnerable to human error. Pinpoint the operational efficiency.
tests that are so critical that even a minor defect could result in √ Determine which types of tests you want to automate first — for
substantial business loss. example, regression, smoke, new feature / exploratory testing,
and functional testing. Many organizations start with regression
testing because that is where they spend the most time.

A 30-60-90-Day Plan for QA Leaders | 9

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

Day 21 – 30: Select the right automation tool or
tools

Choosing the right software test automation tool (or tools) is critical.
The selection should align with your applications’ technology stack and
your team's skills.

Tasks:

√ Determine what features are essential to the organization. For

example, if security is a top concern, try to find a non-invasive
testing tool that does not require access to the source code.
√ Consider tools that integrate your existing testing
environment, development frameworks, and CI / CD
pipelines.
√ Revisit your automation strategy and develop a shortlist of
tools that align with the priorities of your specific application
and business needs. For example, if automating user
experience testing is crucial, seek tools specializing in visual
verification testing.

Resource: Buyer's Guide to Evaluating Test Automation Solutions |

Keysight

A 30-60-90-Day Plan for QA Leaders | 10

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

The First 60 Days

Day 31 – 40: Establish a budget and build a Day 41 – 50: Build your test automation framework
business case
An automation framework is essential for maintaining a structured,
Implementing automation requires financial resources, but securing scalable, and maintainable automation process. Invest time in building a
those resources is easier said than done. The next step is determining solid foundation.
the budget for automation initiatives and building a business case to get
management buy-in.
Tasks:

Tasks: √ Choose a suitable automation framework that aligns with your

application's architecture and technology stack. Frameworks
like Data-Driven, Keyword-Driven, or Behavior-Driven
√ Quantify the return on investment (ROI) for deploying a test Development provide structures for organizing and executing
automation solution, such as cost savings or cost avoidance automated tests.
due to fewer software defects and decreased re-testing due to √ Establish scripting and coding standards to ensure consistency.
re-releases and bug fixes. These standards include naming conventions, code structure,
√ Identify the ROI value to the business, such as improved and guidelines for creating reusable components within the
software quality, better user experiences, faster release cycles, framework.
improved productivity, and happier customers. Develop √ Emphasize maintainability and scalability. Create modular and
models that translate increased team productivity into cost easily maintainable automation scripts that will accommodate
savings. changes in the application over time. Consider the ability to
√ Secure budget for automation by taking your ROI pitch to scale automation efforts as the application grows.
your management team, department lead, or even a C-Suite
executive, depending on your organization’s size and scope.

Resource: How to Sell the Value of Test Automation to the C-Suite |

Keysight

A 30-60-90-Day Plan for QA Leaders | 11

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

Day 51 – 60: Provide training and skill development

Automation is only as effective as your team's expertise. Invest in training and skill development programs to ensure your team is prepared
for automation.

Tasks:

√ Arrange training sessions for your team on the selected √ Encourage team members to obtain relevant certifications or
automation tools. attend workshops like the Learn courses from Keysight.
√ Consider a low code / no code test automation solution if coding
experience is a concern.

A 30-60-90-Day Plan for QA Leaders | 12

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

The First 90 Days

Day 61 – 70: Automate build and deployment processes

Automating build, test, and deployment processes streamlines the software delivery pipeline, enabling shorter release cycles. Automation enables
organizations to release new features, enhancements, or bug fixes more frequently.

Tasks:

√ Use a version control system like Git to manage and track √ Implement containerization with technologies like Docker
changes to the source code. Having a centralized repository and orchestration with Kubernetes to ensure consistent and
enables collaboration among developers. scalable deployment across various environments.
√ Set up an automated build process to compile the code, run
unit tests, and generate executable artifacts. Tools like Jenkins,
Travis CI, or GitLab CI can automate this process.

A 30-60-90-Day Plan for QA Leaders | 13

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

Day 71 – 80: Integrate continuous testing

To ensure your automated tests are a seamless part of your

development process, integrate them into your CI / CD pipeline.
An integration accelerates the delivery of high-quality software,
enhances collaboration, reduces manual effort, and promotes a
culture of continuous improvement within the development and
operations teams.

Tasks:

√ Develop a suite of automated tests, including unit,

integration, and end-to-end tests. Integrate these tests into
the CI / CD pipeline to ensure they run automatically with
each code commit.
√ Optimize test execution time by running tests in parallel to
reduce the overall testing time, providing faster feedback
to the development team.
√ Automate the deployment process to move code
seamlessly from development to staging and production
environments, which reduces the risk of human error and
ensures consistency in deployment.

A 30-60-90-Day Plan for QA Leaders | 14

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

Day 81 – 90: Monitor progress and report metrics

As your automation efforts progress, it is essential to implement

processes to track and report on the effectiveness of your automation
initiatives. Regularly review and adapt these metrics to ensure they align
with the evolving needs of your development and testing processes.

Tasks:

√ Define key performance indicators (KPIs) like test execution

time, test coverage, deployment success rate, defect
identification rate, and overall improvement in release quality.
√ Use the feedback obtained from monitoring to inform
decisions and address issues promptly. For example,
addressing low test coverage can reduce the likelihood of
defects going into production.
√ Track application performance and user experience by
gathering user feedback to measure their satisfaction with the
application.

Resource: Maximize Software Test Coverage with Advanced Reporting |

Keysight Blogs

A 30-60-90-Day Plan for QA Leaders | 15

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

CHAPTER 3

Day 91 and
Beyond —
Scaling and
Optimizing
Automation

A 30-60-90-Day Plan for QA Leaders | 16

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

CHAPTER 3

Day 91 and Beyond — Scaling and Optimizing

Automation
Promote a testing culture Work towards continuous improvement

A testing culture goes beyond just performing tests; it encourages Continuous improvement ensures that your automation efforts remain
everyone involved in the software development process to take ownership effective and efficient. For best results, regularly review your automation
of quality. During this phase, gather feedback from your team and processes and frameworks to identify areas for improvement. Effective
stakeholders to refine and enhance your automation strategy. Document communication and collaboration between teams are essential for
the knowledge and experience gained in your automation journey and successful automation. Strengthen these connections as you conduct
share insights within your team to ensure continuity and scalability. regular reviews of automation processes.

Ideas: Ideas:

√ Engage with developers, product managers, and other √ Conduct periodic code reviews for your automation scripts and
stakeholders to understand their expectations and areas for framework.
improvement. √ Attend regular meetings or forums for QA professionals to discuss
√ Promote collaboration between the QA team, developers, and automation challenges and successes.
other departments to ensure a shared responsibility for quality. √ Recognize and celebrate achievements in testing and automation.
√ Create a knowledge repository or share documents through a
centralized knowledge-sharing platform.

A 30-60-90-Day Plan for QA Leaders | 17

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

Review and adjust your strategy Inspire innovation

Regularly revisit your automation strategy and adjust it based on The final step is to inspire innovation within your QA team and
evolving project requirements, technology changes, and lessons organization. Take opportunities to create a culture of experimentation
learned. Foster a culture of collaboration between the QA and and learning. Keep an eye on emerging automation trends and
development teams to resolve issues efficiently. technologies and assess their applicability to your organization.

Ideas: Ideas:

√ Review your initial automation strategy and update it to reflect √ Encourage your QA team to experiment with new tools,
the changing needs of your organization. techniques, and methodologies.
√ Be open to adjusting priorities and resource allocation based √ Allocate time for team members to work on personal or team
on project demands. projects that explore new testing approaches, tools, or ideas.
√ Seek feedback from your team and stakeholders to ensure √ Organize regular knowledge-sharing sessions where
your automation strategy aligns with organizational goals. team members can present innovative ideas, discuss new
technologies, or share their experiences.

A 30-60-90-Day Plan for QA Leaders | 18

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

CHAPTER 4

Adopting
Today’s
Automation
Trends

A 30-60-90-Day Plan for QA Leaders | 19

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

CHAPTER 4

Adopting Today's Automation Trends

As QA leaders, it is critical to be aware of the latest trends and technologies in automation that are shaping the software testing landscape. By staying
informed and adopting these trends, you can lead your team to a more efficient and productive future in software testing.

Artificial intelligence in testing Continuous testing

Artificial intelligence (AI) and machine learning (ML) are making Continuous testing aligns closely with DevOps and CI / CD pipelines,
significant inroads in software testing. AI-driven testing tools can which involves automated testing at every stage of the software
automate test case generation, predict defect-prone areas, and assist in development process, ensuring rapid and frequent feedback. Embracing
test data creation. ML algorithms can adapt to changing test scenarios, continuous testing helps catch defects early, reducing the cost and effort
improving test efficiency and accuracy. of fixing issues and accelerating the release of high-quality software.

The use of AI / ML has led to a monumental shift in the role of testing Automation software for continuous testing should encompass a
in the software development life cycle. It has empowered testers with combination of functional and non-functional testing as part of the
a more accurate, efficient, and flexible solution to the ever-changing continuous testing process. In addition, the results from test sequences
requirements of modern software development. QA leaders should require integration into the CI / CD framework for analysis and reporting.
explore these technologies to augment their automation efforts.

A 30-60-90-Day Plan for QA Leaders | 20

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

Any platform testing Non-invasive testing

Users expect seamless access to apps and websites across multiple Testing mission-critical systems in a DevOps environment is uniquely
devices and platforms. Meeting their expectations requires continuous challenging due to heightened security and strict regulations. Non-
maintenance of test cases, scripts, and snippet inventory for invasive software testing ensures that software gets a rigorous external
implementations across many platforms. evaluation to address user needs, security concerns, and integration
requirements without relying on detailed knowledge of the software's
internal architecture.
With the proliferation of mobile applications and the importance of cross-
browser compatibility, QA teams need to embrace testing across any
platform or device. Automation tools are evolving to support testing on Testing non-invasively means evaluating the external behavior of a
various browsers, operating systems, and devices, and they help teams system, enabling testers to assess its functionality without having
ensure their applications work seamlessly across different platforms. explicit knowledge of the internal workings. The non-invasive testing
approach is particularly valuable for validating user experience and
ensuring the software meets specified requirements.

Performance engineering

Performance testing is no longer a standalone phase but is evolving into

performance engineering. A performance engineering approach involves
an ongoing and integrated approach to maintaining and improving
software quality throughout the life cycle rather than addressing quality
as a one-time event.

The performance engineering approach advocates for comprehensive

testing, where performance requirements are central to shaping
product design, development, and delivery within a continuous quality
strategy. QA leaders should understand the importance of performance
engineering and adopt relevant tools and practices.

A 30-60-90-Day Plan for QA Leaders | 21

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

Model-based testing

In today's software development landscape, where Agile and rapid

development methodologies are prevalent, model-based testing
provides a flexible and adaptable approach. Model-based testing
enables testers to create abstract representations of the software's
behavior, functionality, and requirements. The models serve as a basis
for generating test cases automatically.

By using models to generate test cases, model-based testing helps

ensure comprehensive coverage of the software's functionality.
Testers can capture various scenarios and edge cases within the
models, addressing different paths and conditions that might be
challenging to cover thoroughly through manual testing. Model-based
testing contributes to a more robust and reliable testing process.

A 30-60-90-Day Plan for QA Leaders | 22

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

CHAPTER 5

The Ongoing
Journey of
Automation
Implementation

A 30-60-90-Day Plan for QA Leaders | 23

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

CHAPTER 5

The Ongoing Journey of Automation Implementation

Implementing automation is not a one-time endeavor but an ongoing journey. After the initial 30-60-90-day plan, continuously improving, adapting,
and expanding your automation efforts is essential. Here are some key considerations to keep in mind as you embark on this journey:

Collaboration and communication Test data management

Maintain effective communication and collaboration between QA teams, Implement strategies to manage and provision test data efficiently,
development teams, and other stakeholders. It is paramount to ensure ensuring your automated tests can access the correct data when needed.
that everyone aligns on automation goals and priorities. Encourage open Effective test data management is critical for automation success.
dialogue and feedback to refine your automation strategy.

Scalability and parallel testing

Test maintenance
Consider the scalability of your test infrastructure as your automation
Update automation scripts and frameworks through regular coverage expands. Parallel testing, the ability to run multiple tests
maintenance. As your application evolves, tests may need updates concurrently, can significantly reduce execution time. Explore options for
to remain relevant. Establish a process for identifying and addressing scaling your testing infrastructure as needed.
maintenance needs to keep your automated tests running smoothly.

A 30-60-90-Day Plan for QA Leaders | 24

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

Performance optimization Training and skill development

Optimize your automation scripts and frameworks for performance Invest in ongoing training and skill development for your team.
continuously. Efficient tests run faster and provide quicker feedback. Automation tools and technologies evolve, and team members must
Regularly review and refine your automation code to ensure it is efficient stay updated to remain effective in their roles. Encourage team members
and effective. to obtain certifications and pursue continuous learning opportunities.

Integration with new technologies Continuous evaluation and improvement

Stay current with emerging technologies and tools that can enhance Evaluate the effectiveness of your automation efforts continuously. Use
your automation efforts. Embrace new technologies and integrate them metrics and KPIs to measure the impact of automation on test coverage,
into your automation strategy as they become relevant. defect identification, and overall product quality. Gather feedback from
your team and stakeholders to identify areas for improvement.

A 30-60-90-Day Plan for QA Leaders | 25

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

CHAPTER 6

Embracing
the Future of
Automation

A 30-60-90-Day Plan for QA Leaders | 26

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

CHAPTER 6

Embracing the Future of Automation

In the ever-evolving world of software development, automation has The importance of automation extends beyond the initial 90 days of your
become the linchpin for success. QA leaders in software testing must plan; it is an ongoing journey. QA leaders must remain agile, adaptable,
recognize the critical role automation plays in accelerating testing and informed about the latest trends and technologies shaping the
processes, enhancing test coverage, and ultimately improving the testing landscape. Collaboration, communication, and a commitment to
quality of software products. learning are essential to this journey.

Automation is a powerful tool representing a strategic shift in In conclusion, automation is not just a means to an end but the future
how companies develop, test, and deliver software. By efficiently of software testing. Embracing automation enables QA leaders to
implementing automation in the first 30-60-90 days of their tenure, QA deliver high-quality software products quickly and efficiently, ensuring
leaders can set the stage for a culture of continuous improvement and they meet the ever-increasing demands of today's high-tech world. By
excellence in testing. adhering to the principles and steps outlined in this automation plan, QA
leaders can navigate the complex software testing landscape and steer
their teams toward a future filled with possibilities.

A 30-60-90-Day Plan for QA Leaders | 27

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

Get Started in Just 90 Days

At Keysight, we have assisted numerous organizations in achieving Keysight offers a low-risk approach to prove that automation is right for
their automation goals. We understand the unique challenges of each your organization. For just $10K in 90 days, we will connect our experts
industry and can tailor solutions to meet your specific needs. with members of your team and build the best automation integration
plan for your organization.

Quick start today

Tailored setup

Platform training

Best practices

Kick-off workshop

Status reviews

A 30-60-90-Day Plan for QA Leaders | 28

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

 Keysight enables innovators to push the boundaries of engineering by quickly solving design, emulation, and
test challenges to create the best product experiences. Start your innovation journey at www.keysight.com.

This information is subject to change without notice. © Keysight Technologies, 2024, Published in USA, January 23, 2024, 7124-1001.EN