Skip to main content

Review of 2012

2012 has been a full-on year with lots of change. I started the year in my previous role, preparing for a transition into a newly created role of "Solution Architect"; moving away from both day to day coding and purely concentrating on .NET applications / systems. It sounded a really interesting challenge but another opportunity presented itself working for my current company in another newly created role of "Technical Team Lead". It was a hands-on development role, leading a team of 3 developers bringing a large business critical application in-house and helping to roll out scrum and other processes (such as TDD/BDD, Continuous Integration, etc.) to the business and team.

The very first challenge was the knowledge transfer sessions for the "out-sourced" application, which had been designed and developed by one company and then the maintenance passed onto a second company. It's probably fair to say that the code has grown organically rather than being designed and has undergone several architectural changes without completing or replacing the previous model(s). As a result it contains both direct SQL access via ADO.NET and at least 2 different ORM implementations. Many other areas of the code based might contain a mixture of design patterns alongside some large "procedural based" class methods. There were no automated tests of any form, and most documentation had either been lost or was now hopelessly out of date! Having just had the opportunity of working in a completely green field system in my last role, getting the chance to apply that knowledge in a large, deployed, business critical brownfield system seemed like a nice challenge (I have spent much time wondering if I was mad!)

With such an interestingly complex system we had our most success videoing the hand over sessions, recording what didn't work as much as what did work as this both gave us the instant knowledge and the ability to go back after the event to refresh our memories. This also meant that those sessions are available as a record for new members joining the team. The very first win was the ability to deploy and develop all aspects of the system locally, with instruction guides that could be followed by the entire team and worked every time on every machine (no small achievement!). We are now preparing for the production deployment of our first "in-house" developed release of this application including a few small pieces of new functionality but mostly containing massively increased logging to help track down issues reported by the business in the production environment.

As well as taking over responsibility for the main application code base, we have replaced an existing ASP system with an MVC application developed in sprints using Scrum, TDD and TeamCity Continuous Integration - a massive learning curve for the team which they handled extremely well. This system has had two functionality deployments so far, with a third currently in test. This is a big improvement over the current norm of deployments every 3 or 6 months but there is still a little way to go before we can look to release at least every sprint.

I think that on the whole the team can be really happy as we have accomplished everything that was promised in 2012, just not necessarily everything that was hoped for - but we have to leave something to improve upon in 2013!

Comments

Popular posts from this blog

Mocking HttpCookieCollection in HttpRequestBase

When unit testing ASP.NET MVC2 projects the issue of injecting HttpContext is quickly encountered.  There seem to be many different ways / recommendations for mocking HttpContextBase to improve the testability of controllers and their actions.  My investigations into that will probably be a separate blog post in the near future but for now I want to cover something that had me stuck for longer than it probably should have.  That is how to mock non abstract/interfaced classes within HttpRequestBase and HttpResponseBase – namely the HttpCookieCollection class.   The code sample below illustrates how it can be used within a mocked instance of HttpRequestBase.  Cookies can be added / modified within the unit test code prior to being passed into the code being tested.   After it’s been called, using a combination of MOQ’s Verify and NUnit’s Assert it is possible to check how many times the collection is accessed (but you have to include the set up calls) and that the relevant cookies have …

Injecting HttpContextBase into an MVC Controller

It is a shame that when the ASP.NET MVC framework was released they did not think to build IoC support into the infrastructure. All the major components of the MVC engine appear to magically inherit instances of HttpContext and it’s related objects – which can cause no end of problems if you are trying to utilise Unit Testing and IoC. Reading around various articles on the subject just to get around this one problem requires the implementation of several different concepts and you are still left with a work around. The code below, along with the other links referenced in this article is my stab at resolving the issue. There’s probably nothing new here, but it does attempt to relate all the information needed to do this for Castle Windsor. The overview is that all controllers will need to inherit from a base controller, which takes an instance of HttpContext into it’s constructor. It then overrides the property HttpContext in the main controller class, supplying it’s own version…

Unit Testing Workflow Code Activities - Part 1

When I first started looking into Windows Workflow one of the first things that I liked about it was how it separated responsibilities. The workflow was responsible for handling the procedural logic with all it's conditional statements, etc. Whilst individual code activities could be written to handle the business logic processing; created in small easily re-usable components. To try and realise my original perception this series of blog posts will cover the unit testing of bespoke code activities; broken down into: Part One: Unit testing a code activity with a (generic) cast return type (this post)Part Two: Unit testing a code activity that assigns it's (multiple) output to "OutArguments" (Not yet written)So to make a start consider the following really basic code activity; it expects an InArgument<string> of "Input" and returns a string containing the processed output; in this case a reverse copy of the value held in "Input".namespace Ex…