No I can't.
Communication is hard and I had to come up with a self contained example.
Enough to tell that these are extensive ETL operations shuffling and transforming trillions of data sets each night.
And I'm not going to tell my client that his code base of the last 20 years is "horse shit". *
The case is still interesting as such: What is the best approach for deep unit testing?
Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice
*) at least not on a daily basis ;-)
In reply to Re^4: "deep" unit testing
by LanX
in thread "deep" unit testing
by LanX
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |