Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Modern API Development with Spring 6 and Spring Boot 3 - Second Edition

You're reading from  Modern API Development with Spring 6 and Spring Boot 3 - Second Edition

Product type Book
Published in Sep 2023
Publisher Packt
ISBN-13 9781804613276
Pages 494 pages
Edition 2nd Edition
Languages
Author (1):
Sourabh Sharma Sourabh Sharma
Profile icon Sourabh Sharma

Table of Contents (21) Chapters

Preface 1. Part 1 – RESTful Web Services
2. Chapter 1: RESTful Web Service Fundamentals 3. Chapter 2: Spring Concepts and REST APIs 4. Chapter 3: API Specifications and Implementation 5. Chapter 4: Writing Business Logic for APIs 6. Chapter 5: Asynchronous API Design 7. Part 2 – Security, UI, Testing, and Deployment
8. Chapter 6: Securing REST Endpoints Using Authorization and Authentication 9. Chapter 7: Designing a User Interface 10. Chapter 8: Testing APIs 11. Chapter 9: Deployment of Web Services 12. Part 3 – gRPC, Logging, and Monitoring
13. Chapter 10: Getting Started with gRPC 14. Chapter 11: gRPC API Development and Testing 15. Chapter 12: Adding Logging and Tracing to Services 16. Part 4 – GraphQL
17. Chapter 13: Getting Started with GraphQL 18. Chapter 14: GraphQL API Development and Testing 19. Index 20. Other Books You May Enjoy

Testing APIs and code manually

Testing is a continuous process in software development and maintenance cycles. You need to do full testing that covers all possible use cases and the respective code for each change. Different types of testing can be performed for APIs, including the following:

  • Unit testing: Unit testing is performed by developers to test the smallest unit (such as a class method) of code.
  • Integration testing: Integration testing is performed by developers to test the integration of different layers of components.
  • Contract testing: Contract testing is performed by developers to make sure any changes that are made to the API won’t break the consumer code. The consumer code should always comply with the producer’s contract (API). It is primarily required in microservices-based development.
  • End-to-end (E2E) testing: E2E testing is performed by the quality assurance (QA) team to test end-to-end scenarios, such as from the UI (consumer) to...
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 €14.99/month. Cancel anytime}