I’ve been giving a number of presentations on Agile Software Development of late and I thought it might be useful to publish my take on Agile and how I present it. I have been using variations of this slide deck for my presentations.
Continue reading “Agile Software Development”
When I first started learning about how to do database code in .NET and in particular how to test your database code I came across a really useful post on the Code Project.
It basically goes through a tutorial on how to get a base class set up that sets up a brand new SQL Server CE database every test run and populates it from an NHibernate configuration.
This was great, but there were a number of issues that caused it to not work for me (including the fact I decided to use Fluent NHibernate rather than writing a heap of obscure XML). As well as this, there were a couple of fundamental flaws in the way the test worked and it didn’t work with the latest versions of SQL Server CE and NHibernate at the time.
Consequently, I fixed up the code so it worked and I wanted to outline those changes and the final result here in case anyone finds it useful.
As I alluded to in a previous post, I think that achieving high code coverage in controller tests is often a waste of time in terms of return on investment – most of the stuff in there will be trivial things that either work or don’t and will be hard to regressively break (e.g. returning the view with the model if model validation failed). In saying that, if there is a way to get really terse tests then they become easier to write and maintain and then it’s worth aiming for high code coverage (since the reward outweighs the cost).
Continue reading “Terse controller testing with ASP.NET MVC (part 1)”
This post describes a package I created to be able to run QUnit testing from within any .NET testing framework, and thus also from continuous integration servers.
This post outlines some of my views about testing web applications, and why automated testing of web applications is important. This post somewhat assumes an MVC pattern, but the same concepts apply if you aren’t using MVC.
Continue reading “Web application testing”
I’ve been doing web development professionally since 2004 and in that time I’ve learnt a lot and I consider myself to be a good web developer. I’m mostly self-taught, learning most of what I know from research on the Internet, in combination with experimentation, to both find out the way things work and figure out the best ways to use them.
While the Internet is an amazing resource, there is a lot of bad information out there and you should always be careful when taking information at face value. I’ve compiled a list of links to information that I personally think is important if you want to be a good web developer (or designer).
It’s really difficult trying to bring to mind all of the most important things that I know so there is probably quite a bit missing, but this is a good start. I may well follow this post with another one later with things I’ve missed. If you think there is something really important that I’ve missed fell free to leave a comment.
Without further ado (written in C# for fun, if you don’t know C# it’s ok just click on the links):
Previous to starting this blog I was posting on a blog I started with my job at Curtin University. As you will see if you look at the blog, I got VERY busy towards the middle / end of 2010 so there is a big gap in blog posts after I started.
The following posts were my favourite:
Continue reading “Previous Posts”