Become a Full-stack .NET Developer - Architecture and Testing
Pluralsight
Course Summary
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.
-
+
Course Description
As a .NET developer, you ought to know how to architect and test your applications - not only do these skills make you a more advanced developer, but they also help you build better apps. In this course, Become a Full-stack .NET Developer - Architecture and Testing, you'll learn how to do just that. This course is the third part of the "Become a Full-stack .NET Developer" series. In the previous two parts, you built a real-world mini social networking application for live music lovers. In this final part, you'll finish off the remaining use cases, modularize JavaScript code, and then refactor your application towards a clean, decoupled, and testable architecture. Next, you'll learn about programming against interfaces, and finally you'll write unit and integration tests for various moving parts. By the end of this course, you'll be able to create highly testable apps with better architecture, and you'll be one step closer to being a full-stack .NET developer.
-
+
Course Syllabus
Implementing the Remaining Use Cases- 25m 8s
—Introduction 1m 36s
—Planning the Third Iteration 0m 43s
—Exercise 2m 40s
—Gig Review 4m 13s
—Using Lookups 5m 50s
—Finding Affected Areas in the Code 3m 20s
—Implementing the Toggle Behavior 4m 30s
—Code Review 1m 35s
—Summary 0m 37sModularizing JavaScript Code- 40m 56s
—Introduction 0m 23s
—Extracting JavaScript Code 4m 0s
—Revealing Module Pattern 5m 26s
—Refactoring Using Revealing Module Pattern 1m 47s
—Cleaning the Init Method 1m 54s
—Applying the DRY Principle 5m 58s
—Better Separation of Concerns 2m 27s
—Module Dependencies 5m 53s
—Physical Separation 2m 55s
—Optimization 2m 54s
—Exercise 1m 28s
—Code Review 4m 43s
—Summary 1m 2sRefactoring Towards the Clean Architecture- 41m 56sProgramming Against Interfaces- 44m 2sTesting Controllers- 34m 54sTesting Repositories- 19m 2sAdding Integration Tests- 33m 7s
