Видео

Since this video came out, Microsoft actually recommend against in memory databases for testing. Best thing to do is to mock out the repository when unit testing and use a docker image when you want to test the interaction with the database. Hope this helps

Thanks for the comment. I really appreciate that. Whenever I get around to the next video, I’ll make sure that I increase the font size. It’s always one of those things that slips my mind when making them 😊

There’s a function on the factory called something like “RegisterTestServices”. Here you can replace the service that you don’t want and pass in your mock. Here’s also a more detailed blog on the subject and I also think that there’s some simplified examples on how to do this on the Microsoft website. If you’re still not sure after reading then I’ll try to root out the code 😊 timdeschryver.dev/blog/how-to-test-your-csharp-web-api#keep-test-cases-short-and-readable-with-extension-methods

Thanks! Glad you found it useful 😊

They’re not equivalent. Null and empty string are different values in C#. The best you could do is tell fluent assertions to ignore that field.

@@themusingsofadev3565 I can't ignore because I want to compare other values to be equals

Then I would override the equals method on your class if possible, otherwise I think you’re out of luck. You could always ignore it on that test and then write a specific test for the empty string null problem

@@themusingsofadev3565 I need a generic solution for every model that I read form a csv or xlsx, you know, string null becomes string empty in a file

@@themusingsofadev3565now you understand?

I think it is worth noting that In-Mem is also very good for teaching or demoing code.

You have to take into account that an in memory database won’t do anything more than put data there. It won’t check for relational integrity and doesn’t check database validation. So it all depends on what you’re test is doing. If you’re just using it to check simple logic then a in memory database is a nice option. If you’re writing tests that actual check the interaction with the database (integration tests, repository tests) then I would avoid in memory databases.

I never thought of providing the source code to be honest 😅 I’ll make sure I provide a link to the source code in the description for future videos and will add it to this one as soon as I can!

No problem, hope it helped 😊

Glad that your test caught that odd bug!!

As the desktop background you mean? I honestly have no idea, it’s just one of the default background options 😊