Skip to content
0:00 / 0:00

#csharp#dotnet#dependencyinjection

The refactoring test (1) - Dependency Inversion & Unit tests | Cracking the .NET interview

Nick Chapsas

429K subscribers • 62 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Nick Chapsas

Intermediate. Assumes working knowledge.

119K views5 years ago2 recommendations

Tools and practiceSoftware designTestingDesign patternsRefactoring and legacy code

Nick Chapsas demonstrates how to refactor legacy .NET code using dependency inversion to make it testable and write unit tests for it.

Become a Patreon and get source code access: patreon.com/nickchapsas Check out my courses: dometrain.com Hello everybody I'm Nick and in this video series I am teaching you how you can crack every part of the interview process as a .NET software engineer and get the job. In this video we are going to see a very common scenario where where interview test is a refactoring test. I will explain the thought process and methodology and show you how you can apply the best practices. Even if you are not looking for a job, practicing those tests keep your knowledge sharp. Timestamps Intro - The problem - Taking a look at the code - First things first - Making the class testable (DIP) - Writing the unit tests - Don't forget to comment, like and subscribe :) Social Media: Follow me on GitHub: bit.ly/ChapsasGitHub Follow me on Twitter: bit.ly/ChapsasTwitter Connect on LinkedIn: bit.ly/ChapsasLinkedIn Keep coding merch: keepcoding.shop #dotnet #csharp #refactoring

Why it's here

2 people recommend this

What people say. Recommended as a great practical guide on refactoring legacy code using dependency injection and unit tests for .NET interviews.

u/worstspiderin r/dotnet • Recommends

On “WPF Best Practice for Dependency Injection and Unit Tests?”

Nick Chapsas made a great video some weeks ago. It actually is about refactoring legacy code but in its first part he talks about DI and Unit, hope this helps you link to this video

u/CaptainIncrediblein r/dotnet • Recommends

On “[deleted by user]”

The guy in this video takes a piece of legacy code that is kinda badly written, and applies unit tests to it. Honestly, I kinda liked this video, and found it educational. It might be helpful for you. link to this video You can get all the source code and follow along at home.

u/Darth_Hannibalin r/dotnet • Mentions

…ave seen around the internet talking about : algorithms and system design but I think that is for the big big companies. I am under the impression that normal lets say companies ask more practical stuff like give you an exercise, or a home project and discuss on it where design patterns, refactoring, unit tests may be involved something like this: link to this video What are your experiences, what is the type of interview style you have generally seen or heard from other people? Thank you very in advance, appreciate your responses :)…