Part of what I look for in a good test is catching errors in the data. I always try to put some errors into the input data to make sure they don't get all the way through into production. I still catch errors in real production data because the developers were lazy on data validation, always assuming their data was good.
/Tom Kern Donald Johnson wrote: > One thing to remember is that production data may not always be the best > test, as it may not contain all possible combinations of values in the > various fields. Just because it is production does not mean it is > comprehensive. > > * Don * ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
