Knowing how to architect and test ASP.NET MVC applications helps you build better apps. In Part 3 of the "Become a Full-stack .NET Developer" series, you'll refactor your app toward a better architecture as well as write unit and integration tests.
Hi everyone, my name is Mosh Hamedani and welcome to the third part of my course Become a Full-stack .NET Developer
I am a software engineer and author with 15 years of professional experience.
The demand for full-stack developers who are comfortable with both front-end and back-end development is increasing constantly, and in fact, some companies only hire full-stack developers.
This part is all about architecture and unit testing.
Some of the major topics that we will cover include:
Dependency inversion principle
Repository and unit of work patterns
Clean architecture, and
Unit and integration tests
This part is packed with advanced concepts and techniques, and I believe if you watch all the videos and do the exercises, by the end of this part you’re going to go from an intermediate-level developer to a senior developer.
Before beginning this course, ideally you should have watched the first two parts because there I’ve covered a lot of concepts and techniques. So if you’re new to this series, you may wonder why I’ve done things in a certain way, or you may think I’m coding too fast. If that’s case, then you really need to go back and start from the first part. Also, you should be familiar with unit testing. At least you should have gone through one tutorial and be familiar with assertions and mocking. In this part I’ll show you the proper way to write unit and integration tests for your ASP.NET MVC applications.
I hope you’ll join me on this journey to learn full-stack development with Become a Full-stack .NET Developer course, at Pluralsight.