Testing evolution

Testing evolution • It’s all started with programming and debugging phase, when finding errors during debugging

was considered testing. In 1957, testing got an individual identity and was treated as a separate activity from the debugging process.

•

Till the late ’70s, testing was seen as an exercise to ensure that the software works as per the specified requirements. It was then extended to find the errors, besides ensuring the proper functioning of the software. In the ’80s, the testing activity was also considered as a measurement of quality. With this, it gained more importance and was treated as a clearly defined and managed process of the software development life cycle. By the mid-’90s, the testing process had its own life cycle.

• In this article, we have segregated the phases of software testing evolution in terms of different eras for a better understanding.

The Era of Programmers and Testers

Development and testing were treated as mutually independent activities during this era. Once the software was ready, it was passed on to the testing team for verification.

The Era of Exploration and Manual Testing • The late ’90s saw the advent of various methodologies like agile testing, exploratory testing, etc. Testing was done manually using detailed test cases and test plans.

• Exploratory testing gave freedom to test and break software in indigenous ways by exploring the software within the gamut of testing charters.

If you are interested in learning more about Webomates’ CQ service please click here and schedule a demo or reach out to us at info@webomates.com