You're reading from Tools and Skills for .NET 8 Get the career you want with good practices and patterns to design, debug, and test your solutions 

Product type Paperback

Published in Jul 2024

Publisher Packt

ISBN-13 9781837635207

Length 778 pages

Edition 1st Edition

Languages

Tools

.NET

Concepts

Cloud Native

Author (1):

Mark J. Price

View More author details

Table of Contents (22) Chapters

Preface

1. Introducing Tools and Skills for .NET

2. Making the Most of the Tools in Your Code Editor FREE CHAPTER

3. Source Code Management Using Git

4. Debugging and Memory Troubleshooting

5. Logging, Tracing, and Metrics for Observability

6. Documenting Your Code, APIs, and Services

7. Observing and Modifying Code Execution Dynamically

8. Protecting Data and Apps Using Cryptography

9. Building an LLM-Based Chat Service

10. Dependency Injection, Containers, and Service Lifetime

11. Unit Testing and Mocking

12. Integration and Security Testing

13. Benchmarking Performance, Load, and Stress Testing

14. Functional and End-to-End Testing of Websites and Services

15. Containerization Using Docker

16. Cloud-Native Development Using .NET Aspire

17. Design Patterns and Principles

18. Software and Solution Architecture Foundations

19. Your Career, Teamwork, and Interviews

20. Epilogue

21. Index

Testing web services using xUnit

There are multiple ways to test web services:

Automated testing frameworks like xUnit, NUnit, and MSTest
HTTP request editors like REST Client for VS Code or HTTP Editor in Visual Studio
GUI tools like Postman, NSwag, or Swagger UI

Warning!

Swashbuckle package integration will be removed in .NET 9. You can learn more about this at the following link: https://github.com/dotnet/aspnetcore/issues/54599. The ASP.NET Core team will replace the OpenAPI document generation with a built-in feature, but they have no plans to replace the user interface for testing.

One of the trickier aspects of testing web services is how to host the web service during testing and how to simulate an HTTP context. Integration tests for ASP.NET Core projects require the following: