Book Image

Modern Web Development with ASP.NET Core 3 - Second Edition

By : Ricardo Peres
Book Image

Modern Web Development with ASP.NET Core 3 - Second Edition

By: Ricardo Peres

Overview of this book

ASP.NET has been the preferred choice of web developers for a long time. With ASP.NET Core 3, Microsoft has made internal changes to the framework along with introducing new additions that will change the way you approach web development. This second edition has been thoroughly updated to help you make the most of the latest features in the framework, right from gRPC and conventions to Blazor, which has a new chapter dedicated to it. You’ll begin with an overview of the essential topics, exploring the Model-View-Controller (MVC) pattern, various platforms, dependencies, and frameworks. Next, you’ll learn how to set up and configure the MVC environment, before delving into advanced routing options. As you advance, you’ll get to grips with controllers and actions to process requests, and later understand how to create HTML inputs for models. Moving on, you'll discover the essential aspects of syntax and processes when working with Razor. You'll also get up to speed with client-side development and explore the testing, logging, scalability, and security aspects of ASP.NET Core. Finally, you'll learn how to deploy ASP.NET Core to several environments, such as Azure, Amazon Web Services (AWS), and Docker. By the end of the book, you’ll be well versed in development in ASP.NET Core and will have a deep understanding of how to interact with the framework and work cross-platform.
Table of Contents (26 chapters)
Section 1: The Fundamentals of ASP.NET Core 3
Section 2: Improving Productivity
Section 3: Advanced Topics
Appendix A: The dotnet Tool

Getting started with unit tests

Unit tests are not new. Essentially, a unit test is designed to test a feature of your system in isolation to prove that it is working as it should. The F.I.R.S.T principles of unit testingstate that unit tests should be the following:

  • Fast: They should execute fast, meaning they shouldn't carry out any complex or lengthy operations.
  • Isolated/independent: A unit test should not depend on other systems and should provide results independent of any specific context.
  • Repeatable: A unit test should yield the same result whenever it executes if nothing is changed on the implementation.
  • Self-validating: They should be self-sufficient—that is, they should not require any manual inspection or analysis.
  • Thorough/timely: They should cover all the important stuff, even if not required for 100% of the code.

In a nutshell, a unit test should run fast so that we don't...