Tests and Databases are two words that does not fit well together. Usually tests involving database interaction suffers by these smells Interacting Test: since each test can modify data in database it is highly possible that data written by a test can make another test fail. Moreover if more than one developer use the same [...]
Sometimes you write pieces of code like this. catch { LogException(…. This type of exception handler catch everything and log, despite the fact that is not so good practice to catch every exception that a piece of code could raise, one of the most frustrating thing is that if you place a breakpoint in the [...]
Continue reading about View the current exception in Visual Studio
Actually I’m working on a project that have a windows service that does a lot of calculation, invokes external servers, and stuff like these. Since we have no user interface, how can you know when error occurred and how can you be informed on the detail of the error? The solution is to create a [...]
Continue reading about A good log can really helps you to write better application
One of my italian Friend once asked me “what is the percentage of code coverage that you consider enough for your tests?â€. The answer is that probably there is not one. If you write a project on your own you can set some limit (Es. 80% code coverage) but in my experience, in the real [...]
This post is a simple test for a couple of plugins that Guardian signaled me. The first one is to insert a DotNetKick tag, I already used one, but this is automatic and does not require me to insert in each post. The second one is a plugin for dzone. Both of them are targeted [...]
