Testing, Testing, 1.2.3.4.5.6..ad infinitum
Before testing... I've now been in development/engineering/coding/hacking or whatever you want to call it for more than 10 years. Testing has always been important, but it - in my line of work - is now at the forefront of everything I do. For the business this is great, every line of code, component and group of components is covered by some set of tests. Be it unit, integration, component...the overloaded terms go on. This means that a set of requirements - to some degree - have been determined to have been met by these tests and the business is getting what it wants (all manner of development and agile practices not withstanding - they all get us to the same place) It struck me today though that earlier in my career, when testing was still important but lines were - perhaps - a little more blurred and things were a bit more hit and miss, things were less clinical, less contrived and quite frankly less boring. This is obviously not a good model for delivering qual