{"id":3390,"date":"2016-02-03T10:10:35","date_gmt":"2016-02-03T10:10:35","guid":{"rendered":"https:\/\/www.happiestminds.com\/blogs\/?p=3390"},"modified":"2024-04-10T08:10:08","modified_gmt":"2024-04-10T08:10:08","slug":"viewing-testing-as-an-observation-on-data-in-motion","status":"publish","type":"post","link":"https:\/\/www.happiestminds.com\/blogs\/viewing-testing-as-an-observation-on-data-in-motion\/","title":{"rendered":"Viewing Testing as an observation on “Data in Motion”"},"content":{"rendered":"
<\/div>

Testing has been traditionally viewed as an exercise of observing and commenting on the behavior of an “application under test<\/a>“. Testers have been always groomed to be honest to the “requirements” that form the basis of solutions. Then came the era of scale and the consequent resource contention issues that software (and associated hardware). “Nonfunctional Requirements” also got added as a new dimension to testing. But the focus still remained the same – application behavior. As applications grew to become integrated solutions<\/em> and then platforms, the philosophy of testing remained the same.<\/p>\n

A parallel view for testing evolved in the meantime – primarily led by the data warehouse world – a concept that looked at software as a “means” to achieving data transformation, processing and reporting. Testing can also be viewed as data in motion. Of course, the functions that retrieve, store, transmit, process and syndicate\/present data are as important as the data itself from a testing standpoint, but then – as long as the data moves in an expected fashion from the source to the end under a spectrum of conditions, the product can be deemed “Quality Assured<\/a>“.<\/p>\n

A few aspects of data centered testing\u00a0 – One needs a thorough understanding of<\/strong><\/p>\n