Writing long-term software

Carlos Ble show me for the first time the advantajes of using TDD in projects with software to be living for a long life cycle. I wasn’t ready to understood it when he did. However now I’m ready. Furthermore I investing huge amount of time in deploy a continuos integration tool for my company.

This post shows how to do a basic configuration. It runs tests and provides coverage reports, which are really useful. I have try to go even further using pylint, as explained here but the hudson server is in the server we use, which also server our LTSP environment, so I decided to put it away because it use too much resource and the information was not useful due to the massive uses of dynamic classes in Django and, probably, virtualenv.

Once we have a way to meter the goodness of our code, we have move to TDD, at least in all the new code written, doing so we assure the ability to maintain the software in the future, which is a really desirable thing in a project which should be running for many years.

Hudson has probe to be a really simple, but useful tool, we expect to use in all our development projects.

One Response to Writing long-term software

  1. carlosble says:

    Glad you are enjoying test driving your desings 🙂
    Thanks for this post. I was thinking of CI today on Python and thinking that Hudson might work better than my scripts and … this is a nice chance, you’ve just posted about it.
    I’ll give it a try.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: