Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
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

Considerations for API mocking

Let us quickly review a few important considerations when mocking API calls:

  • A mock API server should mimic the real responses realistically. It should conform to the same set of contracts as the real service.
  • A mock API can be figured to simulate non-functional behavior such as slow response times, various error responses, and so on.
  • Mock APIs usually do not persist data like real APIs and the automation test frameworks should account for their unique behaviors.
  • Extra caution should be used when mocking external vendor APIs, as any uncommunicated changes on the vendor side might break the mock and bring the testing to halt.
  • The transition from a mock API to a real API should be planned in advance to ensure test continuity.
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 $19.99/month. Cancel anytime
Banner background image