sfeldman.NET

.NET, code, personal thoughts

  • Code Coverage Tool – New Kid on the Block

    We are utilizing NCover to perform code coverage as a part of CI process on the build server. On development machines, at least for now, we don’t have it (which is a bummer). PartCover (a free alternative to NCover) is not there yet, so we waited till the right time would come to buy workstation licenses. It looks like the time is almost right. JetBrains has announced they will release dotCover tool starting with the traditional EAP program (which is well known from R#).

  • SpecFlow

    Specification based testing is kind of testing I prefer. Once in a while I like to see what’s available. This time, it was SpecFlow framework. Based on Gherkin style specification, it creates your specs, nicely integrating with Visual Studio .NET (I used 2008). This is what an output of a test written with SpecFlow looks like in VS2008 (used R# 5 Beta 2 for as a test runner).

  • Reporting with NHibernate?…

    About over a year+ we had a little application that was leveraging NHibernate for a simple domain. Along all the requirements, one was to generate a pre-defined report with a few simple filters on it. Initial thought was to leverage the same domain we’ve worked out and build report based on that. It was obviously not the best solution there, but once we got the profiling, it was obviously the worse one we could come up with. Re-hydrating entities for reporting was a little bit of a waste. So what would be an alternative without re-investing a lot? We ended up re-using same NHibernate, but in a slightly different manner.

  • ASP.NET WebFormsMVP

    First it was classic ASP, then ASP.NET with WebForms. At the previous company I used to work with it implementing Model-View-Presenter. Since then, I have not touched web development a lot. A lot has changed, and the biggest addition was ASP.NET MVC Framework. Now, there’s a new kid on the blog, that gives ASP.NET WebForms a second change – WebFormsMVP. Check it out.

  • Cortex BDD Test Framework

    Back in 2008 I joined Cortex. I was lucky to join a dynamic and growing development team, not afraid of experimenting and pushing the boundaries of Test-driven development. We were on the learning curve from classical state and interaction-based testing to something bigger. Terry and I started to look into ways to reduce the friction and repetition of test initialization and mocking framework usage (RhinoMocks at that time). This was the beginning of the BDD (behavior-driven development) test framework at Cortex that has since evolved into our standard for all of the projects.

  • Software Quality

    Lately I’m involved in a side project for my son’s school web site. It is a simply imagebasic thing and my part was to observe that the school gets a final result that is possibly to maintain and grow when needed. Decision was made to go with a specific “service provider” that would create the solution. It was agreed on ASP.NET 3.5 – simple.

  • Automate It!

    Development, QA, Deployment, Production Support, Infrastructure,… it doesn’t matter what aspect of software you are affiliated with. Automation is your best friend. And if it is not, you are living a worse nightmare without yet realizing it.