IMHO, since TDD focuses too much on code implementation and is tightly coupled with the code (simply, method names and parameters must match), this metric still does not mean you're safe. If your tool allows you to see the lines of code covered by tests, you can use it to see the parts of the code that are NOT covered by any test - then you can write, if necessary, some more tests. However, in general I think that following the Test Diamond strategy is more beneficial (if you don't know what it is, here's a short introduction: https://www.code4it.dev/architecture-notes/testing-pyramid-vs-testing-diamond/ )

Great article, Daniel!

I've never understood why they turn off ICMP. BTW in some environments, such as the Azure Portal, you can use the tcpping command ( here, in an old article )

Great article, Daniel 🚀

Special thanks to Moke who found an error in the last example.

What do you think of interfaces implemented by only one class, when that class represents a Service and not a DTO? Something like public interface IDoSomething { void Do ( ) ; } public class DoSomething : IDoSomething { void Do ( ) ; }

Yes, indeed! They're the same thing, just with an acronym easier to remember. Both AAA and Given-When-Then just refer to setting up preconditions, executing the main operation, and checking the result.

Also, spelling mistakes make it more difficult to search for a term in your code, if you search for it using the correct word.