The Rules For TESTABLE C# Code Design - Part 2 - The New Keyword

💻 DOWNLOAD THE SOURCE CODE 👉 https://bit.ly/my-source-ciu 👈 🔔 SUBSCRIBE FOR MORE C# LESSONS 👉 http://bit.ly/mytestedaspnet 👈 ► Part 1 - Framework - https://youtu.be/cHe4tCDdKAA ► Part 2 - The New Keyword - THIS VIDEO In this video series, you will learn how to write clean and testable C# code. In the second part, I show why the new keyword and direct object creation is the test's worst enemy. The code starts with bad design and lots of smells. Throughout the tutorial, I use refactoring and best practices to make it more testable in terms of proper architecture and structure. Each code change is then asserted with proper unit test automation, following the "Arrange, Act, Assert" paradigm. ASP.NET Core is used as an example, but the concepts shown can be transferred to any kind of application - Desktop, Web API, Game, Single Page Application, and so on. xUnit, Visual Studio, and 'dotnet test' are used as testing tools. The code becomes easier for faking and mocking, because of the SOLID principles and the dependency injection shown after the refactoring process. ► My Tested ASP.NET Source Code: https://github.com/ivaylokenov ► My Tested ASP.NET Website: https://mytestedasp.net ★★ BECOME A BACKER OR SPONSOR ★★ ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ ► Patreon: https://www.patreon.com/ivaylokenov ► OpenCollective: https://opencollective.com/mytestedaspnet ► PayPal: http://paypal.me/ivaylokenov ► Buy Me A Coffee: http://buymeacoff.ee/ivaylokenov ★★ Follow My Tested ASP.NET ★★ ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ ► Instagram: https://www.instagram.com/mytestedaspnet ► Twitter: https://twitter.com/MyTestedASPNET ► Facebook: https://www.facebook.com/mytestedaspnet ► LinkedIn: https://www.linkedin.com/company/mytestedaspnet ★★ Follow Me ★★ ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ ► Instagram: https://www.instagram.com/ivaylokenov ► Facebook: https://www.facebook.com/ivaylo.kenov ► LinkedIn: https://www.linkedin.com/in/kenov