Testing software development: is it as easy as 1-2-3?

Technology analysts and (unsurprisingly) software testing vendors are always keen to highlight the number of failed application development projects that repeatedly occur. While ‘project skew’ and shoddy coding may indeed throw projects off course, what really matters is the final product and whether it is indeed fit for purpose. The most valuable question we should be asking in light of this reality is just how often and by what methods should application code be tested - so where do we start?

Any IT manager will be familiar with software bugs. These are the glitches, the defects and sometimes the juddering halts that cause a software program to behave in a way that causes problems for its users.

You need to be a subscriber to read the rest of this article.

Already a subscriber? Sign in here