Why We Need Testing

The things we visit "software" is not like anything that human club is utilized to think. The software is wish an automobile and something wish math, and something wish lyric, and something wish idea and graphics, and data.... but software is not really any of those other things. The protein quality of software is a major source of its fascination. It also makes software very powerful, very subtle, very unpredictable and very dangerous.

Some software is bad and buggy. Some is "robust," even "bulletproof." The software is the best that has been tested by thousands of users under thousands of different conditions in recent years. It is then known as "stable". This does NOT mean that the software is flawless, error-free. Usually means there are a lot of mistakes in it but the bugs are well identified and fairly well.

There is simply no way to ensure that the software is free of defects. Though software is mathematical in nature, cannot "proven" as a mathematical theorem, the software is more like language, with inherent ambiguities, with different definitions, different assumptions, different levels of meaning that can conflict. "

Software development involves ambiguity, assumptions and faulty human communication. Every change made to a piece of software, each new piece of functionality, each attempt to fix a defect, introduces the possibility of error. With each error, the risk that the software will not meet its intended purposes increases.

Try reducing that risk. We can use the quality control processes to try to prevent the entry defects in software, but all I can do to reduce the number of errors and this is to prove it. Following a test cycle and rectification can identify and solve problems.

The evidence also helps us to quantify the risk in an untested piece of software. After modifications were made, a piece of software can run in a controlled environment and observed behavior. This provides evidence that informs the decision to move to the next phase of the project or to help rectify the problem.

And finally, in some (dare I say enlightenment?) The efforts of software development, done tests can be used to promote development. Following the statistical models and software development methodologies such as usability testing, software development can move from an artistic endeavor out of focus to a structured discipline.