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

Key considerations for API automation

Automating API tests involves a thorough understanding of the underlying business logic as well as the architectural nuances. Data and performance aspects of the API always pose a tough challenge when trying to run multiple iterations of API tests.

Effective API test automation

Let us now look at some chief considerations when automating API tests:

  • Static data references must be eliminated wherever possible. These render the tests inextensible and isolated.
  • Do more than happy path testing since API tests are quick to run and can provide feedback early in the product life cycle. Applicable product use cases should be tested to a greater extent via APIs. Consider mocking and stubbing to fill in gaps to complete the application flow.
  • Since there is no frontend to check the test results, it is imperative to keep API tests clear with sufficient documentation. This helps especially in debugging when there are new failures in the...

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