Ever introduced an extra parameter on a method, tracked all its usages and made the compiler happy by providing a corresponding extra argument in all the calls of that method?
Sure you have. Either that or removed a parameter from a method.
You just change the signature of the method,
…
My jaw still aches remembering the pain of dropping to the floor when Visual Studio refused to compile
It complains in no uncertain terms. In fact, it drives the message home by repeating the message, albeit with a different word order.
Operator ‘=’ cannot be applied to operands of type ‘string’
…
You have an interface that allows you to treat all worker classes – classes that handle a specific type of work – as just one type: IWorker;
You want your worker classes to be able to do their work without having to check their backs every step of the way.
…
Moving from Delphi to C# is fun most of the time.
Discovering stuff I can do in C# that is impossible, or (very) time consuming, in Delphi is fun. Discovering that stuff I take for granted in Delphi – i.e. metaclasses (officially “class references”),
…
The strategy laid out in Testing strategy for validation and action methods calls for a single test per action method, to show that it actually calls the validation method.
Validation methods throwing exceptions on invalid input provide you with a handy means of checking whether it has been called by your action methods.
…
How do you test a set of methods that call each other without repeating yourself unnecessarily?
You are more than tired of debugging “List index out of bounds”, “Duplicates not allowed” and similar exceptions. You want some help from your code so you don’t have to hit “Next” until you are blue in the face to figure out the information not contained in the standard exception messages.
…
You have an interface and multiple implementers of that interface. You want to test all those implementing classes using the same tests. And you do not want to repeat yourself. That would be … like … Gah!
Using NUnit that is a breeze. But you, you use MSTest,
…
You have an interface and multiple implementers of that interface. You want to test all those implementing classes using the same tests. And you do not want to repeat yourself. That would be … like … Gah!
Using a unit test framework like NUnit that is a breeze.
…
You don’t want to spend your effort on futile tasks. And testing all methods of a base class and then testing them again for every descendant sounds futile.
After all, non virtual methods are not going to change in a descendant, so, really, testing the base should be enough?
…
Storing your application and user settings should be a solved problem. After all, we have done it since the dawn of software development. Yet, the question “What is the best way to store settings?” keeps cropping up. The answers vary widely and quite often spark religious wars.
As interested as I am in why people are so invested in whatever they use,
…
