Overview of automated testing and how it applies to ASP.NET Core
Testing is an integral part of the development process, and automated testing becomes crucial in the long run. You can always run your ASP.NET website, open a browser, and click everywhere to test your features. That's legit, but it is harder to test individual units of code that way. Another downside is the lack of automation; when you first start with a small app containing a few pages, a few endpoints, or a few features, it may be fast to manually run those tests. However, as your app grows, it becomes more tedious, takes longer, and the likelihood of making a mistake as a tester increases. Don't get me wrong here, you will always need real users to test out your applications, but you may want those tests to focus on the UX, the features content, or on some experimental features that you are building instead of bug reports that automated tests could have caught early on.
There are multiple types of tests...