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
Hands-On RESTful Web Services with ASP.NET Core 3

You're reading from   Hands-On RESTful Web Services with ASP.NET Core 3 Design production-ready, testable, and flexible RESTful APIs for web applications and microservices

Arrow left icon
Product type Paperback
Published in Dec 2019
Publisher Packt
ISBN-13 9781789537611
Length 510 pages
Edition 1st Edition
Languages
Concepts
Arrow right icon
Author (1):
Arrow left icon
Samuele Resca Samuele Resca
Author Profile Icon Samuele Resca
Samuele Resca
Arrow right icon
View More author details
Toc

Table of Contents (26) Chapters Close

Preface 1. Section 1: Getting Started FREE CHAPTER
2. REST 101 and Getting Started with ASP.NET Core 3. Section 2: Overview of ASP.NET Core
4. Overview of ASP.NET Core 5. Working with the Middleware Pipeline 6. Dependency Injection System 7. Web Service Stack in ASP.NET Core 8. Routing System 9. Filter Pipeline 10. Section 3: Building a Real-World RESTful API
11. Building the Data Access Layer 12. Implementing the Domain Logic 13. Implementing the RESTful HTTP Layer 14. Advanced Concepts of Building an API 15. The Containerization of Services 16. Service Ecosystem Patterns 17. Implementing Worker Services Using .NET Core 18. Securing Your Service 19. Section 4: Advanced Concepts for Building Services
20. Caching Web Service Responses 21. Logging and Health Checking 22. Deploying Services on Azure 23. Documenting Your API Using Swagger 24. Testing Services Using Postman 25. Other Books You May Enjoy

Implementing a custom log provider in tests

As we already have seen, the logging system of ASP.NET Core is designed for maximum extensibility. In this section, we will learn how to implement a custom logging provider that we can use in our tests. All the test classes that are present in the Catalog.API.Tests project use InMemoryApplicationFactory<T> to run a web server and provide HttpClient to call the API. As you may have noticed, the tests don't return an explicit error when one of the tests fails. For example, let's examine the following test method in the ItemControllerTests class:

public class ItemController : IClassFixture<InMemoryApplicationFactory<Startup>>
{
...

[Fact]
public async Task update_should_returns_not_found
_when_item_is_not_present
()
{
var client = _factory.CreateClient...
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