Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Test Automation Engineering Handbook

You're reading from   Test Automation Engineering Handbook Learn and implement techniques for building robust test automation frameworks

Arrow left icon
Product type Paperback
Published in Jan 2023
Publisher Packt
ISBN-13 9781804615492
Length 276 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Manikandan Sambamurthy Manikandan Sambamurthy
Author Profile Icon Manikandan Sambamurthy
Manikandan Sambamurthy
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Part 1: The Basics
2. Chapter 1: Introduction to Test Automation FREE CHAPTER 3. Chapter 2: Test Automation Strategy 4. Chapter 3: Common Tools and Frameworks 5. Part 2: Practical Affairs
6. Chapter 4: Getting Started with the Basics 7. Chapter 5: Test Automation for Web 8. Chapter 6: Test Automation for Mobile 9. Chapter 7: Test Automation for APIs 10. Chapter 8: Test Automation for Performance 11. Part 3: Continuous Learning
12. Chapter 9: CI/CD and Test Automation 13. Chapter 10: Common Issues and Pitfalls 14. Assessments 15. Index 16. Other Books You May Enjoy Appendix A:Mocking API Calls

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...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at £16.99/month. Cancel anytime