You're reading from Software Architecture with C# 12 and .NET 8 Build enterprise applications using microservices, DevOps, EF Core, and design patterns for Azure

Product type Paperback

Published in Feb 2024

Publisher Packt

ISBN-13 9781805127659

Length 756 pages

Edition 4th Edition

Languages

Tools

.NET

Concepts

Design Patterns

Authors (2):

Gabriel Baptista

Francesco Abbruzzese

View More author details

Table of Contents (26) Chapters

Preface

1. Understanding the Importance of Software Architecture FREE CHAPTER

2. Non-Functional Requirements

3. Managing Requirements

4. Best Practices in Coding C# 12

5. Implementing Code Reusability in C# 12

6. Design Patterns and .NET 8 Implementation

7. Understanding the Different Domains in Software Solutions

8. Understanding DevOps Principles and CI/CD

9. Testing Your Enterprise Application

10. Deciding on the Best Cloud-Based Solution

11. Applying a Microservice Architecture to Your Enterprise Application

12. Choosing Your Data Storage in the Cloud

13. Interacting with Data in C# – Entity Framework Core

14. Implementing Microservices with .NET

15. Applying Service-Oriented Architectures with .NET

16. Working with Serverless – Azure Functions

17. Presenting ASP.NET Core

18. Implementing Frontend Microservices with ASP.NET Core

19. Client Frameworks: Blazor

20. Kubernetes

21. Case Study

22. Case Study Extension: Developing .NET Microservices for Kubernetes

23. Answers

24. Other Books You May Enjoy

25. Index

Functional tests

These tests use the same techniques and tools as unit and integration tests but differ from them in that they are run only at the end of each sprint. They have the fundamental role of verifying that the current version of the entire software complies with its specifications.

Since functional tests also involve the UI, they need further tools to simulate, somehow, how the user acts in the UI. The need for extra tools is not the only challenge the UI brings with it because UIs also see frequent and major changes. Thus, we mustn’t design tests that depend on the UI’s graphical details, or we might be forced to rewrite all the tests completely at each UI change. We will discuss both the tools and the best practices for optimizing UI tests in the Automating functional tests in C# section.

Anyway, it is worth pointing out that sometimes it is better to renounce automated testing for some UI-related features and fall back to manual tests because the...