It doesn't look like TDD. It looks like the usual unit tests writing after implementation. TDD, in my opinion, means just to announce the service's interface, write all unit tests that cover future service functionality and only after this write exact service's implementation. Correct me if I'm wrong please.
Thank You - excellently done! You could break the work down into smaller segments (chapters?) and let the viewer have the opportunity to just jump to that area. Looking forward to more super informative videos!
Mohamed, very interesting video. Thank you. And like from me. Can we have more videos about testing please? Maybe a video about integration tests on the example of an old project from the previous video?
I would like to second this. Majority of the online blogs and RUclips channels are pretty dated as far as Clean Architecture in Dotnet is concerned. The concept may be same but the implementation(workflow and naming convention) has changed over the years. I'm currently stuck and not aware what to follow from a beginner's standpoint-Different libraries i.e. Auto mapper and MediatR libraries have had a fresh smell of paint over the years and so is DotNetCore where Startup.cs class was removed in favor of program.cs and Minimal Api also had a slight facelift and to keep up with all this and fit them together in an application is overwhelming. I would pretty much appreciate if you could do one video capturing the clean architecture crud web Api in dotnet using generic repository pattern unit of work, DTos, Auto mapper and MediatR in one application.
Exactly@@felixpatric4056 , actually most productive applications don't even care about minimal apis, but to keep DDD and clean architecture in order to have a maintenable project, instead of focusing on minimalistic approaches. This is imo the best thing an API dev has to understand
Why u have not use existing .net 7 api projet that you posted on your channel earlier that uses automapper, entity framework & repository pattern?. That would be easy for you to use existing project u only need to add & explain unit test thinks.
@@MohamadLawand I agree previous example was very good and solid base foundation for api building and adding a unit test for that project is like Cherry on cake.
Sorry but this is not real test-driven development. Watch "TDD Is The Best Design Technique" by Continous Delivery to learn what real TDD is. However, this video is fine at showing how to write .NET tests with those tools.
![[DRAGON BALL LEGENDS REVEALS ＆ STUFF] LEGENDS FESTIVAL 2024 Special Edition Part 1](http://i.ytimg.com/vi/mV5bGIswTtQ/mqdefault.jpg)
It has a clear and detailed explanation to test controllers and services. Thank you.
btw, u can use IEnumerable which in ur case better than list while u getting List of data from I/O
It doesn't look like TDD. It looks like the usual unit tests writing after implementation. TDD, in my opinion, means just to announce the service's interface, write all unit tests that cover future service functionality and only after this write exact service's implementation. Correct me if I'm wrong please.
You're abolutely right.
Mohamad hi. 🖐
Please place your camera in the bottom right corner.
That way it won't overlap the useful information from the video.
I am not sure why he does that, if it is intentional or not.
Thank You - excellently done!
You could break the work down into smaller segments (chapters?) and let the viewer have the opportunity to just jump to that area.
Looking forward to more super informative videos!
very nice, thank you Mohammed
شكرا
Mohamed, very interesting video.
Thank you. And like from me.
Can we have more videos about testing please? Maybe a video about integration tests on the example of an old project from the previous video?
Why you add video margin? It's problematic for Fullscreen watching
Next we need a DDD approach please
I would like to second this. Majority of the online blogs and RUclips channels are pretty dated as far as Clean Architecture in Dotnet is concerned. The concept may be same but the implementation(workflow and naming convention) has changed over the years. I'm currently stuck and not aware what to follow from a beginner's standpoint-Different libraries i.e. Auto mapper and MediatR libraries have had a fresh smell of paint over the years and so is DotNetCore where Startup.cs class was removed in favor of program.cs and Minimal Api also had a slight facelift and to keep up with all this and fit them together in an application is overwhelming. I would pretty much appreciate if you could do one video capturing the clean architecture crud web Api in dotnet using generic repository pattern unit of work, DTos, Auto mapper and MediatR in one application.
Exactly@@felixpatric4056 , actually most productive applications don't even care about minimal apis, but to keep DDD and clean architecture in order to have a maintenable project, instead of focusing on minimalistic approaches. This is imo the best thing an API dev has to understand
Testing implementation and framework mmm
Why u have not use existing .net 7 api projet that you posted on your channel earlier that uses automapper, entity framework & repository pattern?. That would be easy for you to use existing project u only need to add & explain unit test thinks.
Good point, I needed to showcase how to get started from the beginning of a new project rather an existing project
@@MohamadLawand I agree previous example was very good and solid base foundation for api building and adding a unit test for that project is like Cherry on cake.
Very informative. Thanks for the video. one request pls can you speak little slower , hard to follow.
Sorry but this is not real test-driven development. Watch "TDD Is The Best Design Technique" by Continous Delivery to learn what real TDD is. However, this video is fine at showing how to write .NET tests with those tools.
Dude, fix you audio please.
TDD should be ❌✅❌✅❌✅
Tests should be written first.