The amount of effort involved in software testing varies from one project to another. A key management challenge is to balance the risk of errors against the testing effort. Very often a greater degree of testing is desirable but impractical due, partly, to time constraints and partly due to the sheer effort involved in finding a reducing number of errors in subsequent test cycles.
It is obvious that if the testing process can be made more effective in determining errors and if it can also become less time and resource consuming, projects will be delivered on-time or early, at a reduced cost and implementation will be easier.
A key factor in a successful testing strategy is to maximize testing at the earliest opportunity. This is when the effort in detecting, documenting, fixing and re-testing an error is at its lowest. Very often, testing performed in the development/coding phase is not even considered to be ‘real testing’, yet it has the greatest opportunity to impact the remainder of the project. In the case of a modification in an existing system, the code change might be relatively small, say two or three hours work, yet the testing that will be involved could easily be measured in days if the change affects a core part of a system. By starting improvements here, it could be possible to eliminate 80% of this testing effort and reduce testing and required re-work because more errors have already been eliminated.
In this paper you can read more about the automation of those testing processes that can not only drastically reduce the inefficiencies and downtime, but also improve the quality and the speed of application development programs. You will learn about the shortcomings of traditional automation tools and that they can be overcome by looking at solutions with more functionality and a design ethos centered around the user.
You can download this paper from: http://www.origsoft.com/whitepapers/cio-insight-strategic-software-quality/