Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Test Automation Engineering Handbook
  • Table Of Contents Toc
  • Feedback & Rating feedback
Test Automation Engineering Handbook

Test Automation Engineering Handbook

By : Manikandan Sambamurthy
5 (6)
close
close
Test Automation Engineering Handbook

Test Automation Engineering Handbook

5 (6)
By: Manikandan Sambamurthy

Overview of this book

This book helps you build a better understanding of test automation and aids in bridging the gap between testing and test automation. The book has been divided into three sections with the first section focusing on preparing you for testing and test automation fundamentals. By the end of this section, you’ll have an understanding of some common automation terms, definitions, and roles. The second section covers the practical implementation of test automation for mobile, web, API and performance. The third section will help you understand how test automation works with CI/CD, and explore the common issues and pitfalls when executing test automation. By the end of this book, you’ll have a better understanding of automation, addressing the common pain points and best practices around test automation.
Table of Contents (18 chapters)
close
close
1
Part 1: The Basics
5
Part 2: Practical Affairs
11
Part 3: Continuous Learning

Chapter 9, CI/CD and Test Automation

  1. CI/CD stands for Continuous Integration and Continuous Delivery. These software engineering practices allow us to automate the building and testing of code to validate it meets the specifications. After all the tests have passed, they equip the teams with options to automate the delivery of code. Continuous Integration, Continuous Delivery, and Continuous Deployment together significantly reduce the time it takes to deliver application enhancements while the engineering team can solely focus on product and code enhancements.
  2. A CI process is triggered when an engineer pushes code changes to the version control repository. A new instance of the CI pipeline is triggered where build and tests are executed.
  3. A CI server typically keeps polling the version control repository every minute or so and runs a preconfigured build script by fetching the latest version of the source files.
  4. Some of the key aspects involved in the CD methodology...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY