Validating database results when refactoring legacy code

This post talks about some data-hashing techiques I employed w/ SQL Server to help validate database results in the absense of automated (unit) tests. Recently I was working on a legacy application in the financial services sector - the code in question performs a hypothetical ("what if") valuation of gas contracts over a period of time. Not really a mark-to-market but rather a set of calculated values (quantity allocated, liquidated charges etc), There was nothing particularly complicated about the calculation…


End of content

No more pages to load