History of Software Testing

History of Testing 

Software Testing came into existence in 1960, not in a structured manner but it was the beginning. The oblivious reason of the birth or rather the need for a testing came because of lack of established standards of software engineering practices. Poor design and Regular hardware up gradation left many types of software in-effective and thus a strong need arose in the industry to produce faster and highly reliable software. The requirement of Software Testing increased with the increasing dependency on software along with good engineers.

Software Testing Originated to address the below issues:

• Enhance the  processes,
• Increase the reliability of product,
• Deliver a quality product,
• Deliver in time

D. Gelperin and W.C. Hetzel in their Book The Growth of Testing has briefly defined the classification in the below.They classified for software testing the following phases and goals:

• Until 1956 it was the debugging oriented period, where testing was often associated to debugging and there was no clear difference between testing and debugging.
• From 1957-1978 there was the demonstration oriented period where debugging and testing was distinguished now - in this period it was shown, that software satisfies the requirements.
• The time between 1979-1982 is announced as the destruction oriented period, where the goal was to find errors.
• 1983-1987 is classified as the evaluation oriented period: intention here is that during the software life cycle a product evaluation is provided and measuring quality.
• From 1988 on it was seen as prevention oriented period where tests were to demonstrate that software satisfies its specification, to detect faults and to prevent faults