THIS stops 90% of C# Developers Learning TDD

90% of C# Developers stop learning TDD for the same reason.
And that is because introductory videos say nothing about how to deal with real-world complex scenarios, like working with external dependencies.
So, to help you overcome this, let's see how to apply test-driven development on common use cases like Services that have external dependencies like Repositories.

🚨 KEY LINKS

👋 HEY FRIEND
If you're new to my Channel, my name is Guilherme, but you can call me Gui if Portuguese pronunciation is not your thing.
I see myself as a Minimalist Software Craftsman. That says a lot of what I talk about here.
So, why this YouTube channel? To share with you to simplify your life as a Developer through knowledge, technology, and practices.
If you are into those things as I do, don't forget to subscribe for new videos.

🔗 GET IN TOUCH

#dotnet #csharp #tdd #testdrivendevelopment

[alpsavasdev]

Wow, this is by far the most useful tutorial on TDD I have ever seen on YouTube. I appreciate it.

[minecraftwithdan]

Thank you so much for this video. Your explanation is so clear and it was exactly what I was looking for to keep on my TDD journey and not get dispondent 😊

[aweklin]

This approach makes you run smoothly, with little debugging because you saw through behaviours as you develop!
Love this & thanks for sharing.

[MarcusHammarberg]

Yes! The "Wishful thinking" part of TDD, imaging that the system we wanted to have, is a power tool. I also loved how you used the phrase "put our test into a green state", when we had stuff that didn't compile.

[johnnyserup]

I like his fast pace - finally an example of real use of TDD.

[FroboDaggins]

Great example of how to apply TDD in a realistic scenario.

I'd like to try out using fakes more as having the code written prior to the tests means I always tend to end up just using mocks.

[rezvlt]

Incredibly useful will use what I've learnt for my e-commerce project

[GavinHohenheim]

I love your frequent refactoring of not only the code, but also the tests. Most devs I see complaining about TDD do not understand how important that is..

[MrOcelot]

good content, even though I never coded c#, java for now, it's useful for showing the mindset and approach.

[chazzman]

Just started c#, switching from php 😊.
Very helpful channel! Thanks man.

[PeteSauerbier]

Good tutorial indeed. Quick question, why didn't you put the context initialization for your tested class into a setup?

[Kamuisakeu]

One amazing thing about this tutorial: This video, with all the explanations took almost 20 minutes and delivered a considerable amount of code with solid unit tests.

Now imagine doing this with focus, in the flow, using some AI assistance.

The productivity will skyrocket!

[martinmusli]

Finally somebody beyond "function takes argument"

[wolfgang]

what are the advantages of using fakes instead of moqs ?🤔

[diegomelgar]

Id like to see the repositories and also an integration test video example 😃

[PaulSebastianM]

One problem that I have whenever I try to distinguish between behaviour and implementation is what unit am I testing and how do I name my tests and/or test class. ’CreateOrderTests’ does not help me understand the unit it is testing, while it may help me understand the behaviour it is testing. Any thoughts on that?

[sebastienvandepoel]

Great video.

I just was wondering, why didn't you start with the happy path? Is there any reasoning behind it?

[eldhoabe]

Make sense. Could you create video about TDD on repository layer

[teamtosoz]

why is this better than let's say use schemathesis and test based on the openapi specification ?

[enzopowell]

Hi, I notice that the "shippingAddress" parameter is by default nullable and that's why you need to write test against it. Too sad C# has no null-safety feature like Dart. But now in c# 11, putting "!!" at the end of the name of arguments can let us skip all the if blocks checking for possible null arguments.