Last time we talked about the impact leaving testing to chance can have on your implementations (and it’s not good), this week we’re going to look at the different types of testing that you can use to give your testing the best chance of catching the defects it’s supposed to.

How many of your implementations are painless exercises in moving files?  In my experience not many and a major factor is the lack of an effective testing strategy.  Testing has been well documented in other forms of application development but for some reason the document industry is still catching up so how do you make sure your testing gives a good return on time and effort?

Given that we're generally up against tight deadlines, often we're completely focussed on what the client wants rather than what we need.  However a little thought upfront can often save a lot of time later in the development and maintenance cycle...