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
Serverless computing in Azure with .NET

You're reading from   Serverless computing in Azure with .NET Build, test, and automate deployment

Arrow left icon
Product type Paperback
Published in Aug 2017
Publisher Packt
ISBN-13 9781787288393
Length 468 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Sasha Rosenbaum Sasha Rosenbaum
Author Profile Icon Sasha Rosenbaum
Sasha Rosenbaum
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Understanding Serverless Architecture FREE CHAPTER 2. Getting Started with the Azure Environment 3. Setting Up the Development Environment 4. Configuring Endpoints, Triggers, Bindings, and Scheduling 5. Integrations and Dependencies 6. Integrating Azure Functions with Cognitive Services API 7. Debugging Your Azure Functions 8. Testing Your Azure Functions 9. Configuring Continuous Delivery 10. Securing Your Application 11. Monitoring Your Application 12. Designing for High Availability, Disaster Recovery, and Scale 13. Designing Cost-Effective Services 14. C# Script-Based Functions 15. Azure Compute On-Demand Options

Software debugging


Software debugging is an iterative activity involving execution testing and code correction. It differs significantly from implementation testing, which will be covered in the next chapter. Implementation testing is aimed at demonstrating the application's correctness, and can be performed in various ways, some of which might not even involve code execution. Debugging, on the other hand, is aimed at locating and correcting code defects.

Debugging is a multi-step process, which can be outlined by the following process diagram:

As seen in the preceding diagram, the process starts with executing the code under a particular set of conditions, and with a specific end result in mind. The list of possible start conditions used in debugging typically covers the common success and error cases. During debugging, it is important to verify that the code handles errors gracefully in common scenarios, such as incorrect input or inaccessible data store. This means that the "success criteria...

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