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
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Programming APIs with C# and .NET

You're reading from   Programming APIs with C# and .NET Develop high-performance APIs that ensure seamless application communication and enhanced security

Arrow left icon
Product type Paperback
Published in Nov 2024
Publisher Packt
ISBN-13 9781835468852
Length 166 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Jesse Liberty Jesse Liberty
Author Profile Icon Jesse Liberty
Jesse Liberty
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Chapter 1: Getting Started 2. Chapter 2: What We’ll Build FREE CHAPTER 3. Chapter 3: Implementing with REST 4. Chapter 4: Documentation with Swagger 5. Chapter 5: Data Validation 6. Chapter 6: Azure Functions 7. Chapter 7: Azure Durable Functions 8. Chapter 8: Advanced Topics 9. Chapter 9: Authentication and Authorization 10. Chapter 10: Deploying to Azure 11. Chapter 11: What’s Next? 12. Index 13. Other Books You May Enjoy

Getting started

At the end of Chapter 6, you saw how easy it is to deploy to Azure directly from Visual Studio. This is fine for testing scenarios and one-off experiments or proofs of concept, but in a production scenario, this one project may be part of a much larger system.

Setting up a series of “gates” (checks) before publishing to production can be advantageous for many reasons. Note that there are many types of release gates. The most common (and important) are Pull Requests (PRs), unit tests, integration tests, and end-to-end tests.

Using tests to ensure code quality

There are many kinds of tests that you might run against your code. Among the most important are the following:

  • Unit tests
  • Integration tests
  • Automated tests

Unit tests cover one section of your code that does one thing. For example, many unit tests have a 1:1 correspondence with methods, but not always. Think functionality rather than code. However, they must run extremely...

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