Hi,
I have been in business long time and I used to do 0 (zero) testing before releasing new updates. And invariably, as soon as the app would get in the hands of a customer, it would crash. I even remember the times - before internet - when I had to ship a diskette overnight or send it with a taxi.
Now I am doing much more testing, even though updating is much simpler.
Which brings me to a question. I don't have a QA, so I am it :)
Currently I am doing a refactoring where 3 SQL Select statements are replaced with 1. The SQL Select is very important because it is part of the important Business unit of the application. The way I am testing it as follows:
1. I created a list of test cases (various possibilities of data)
2. Run this new SQL Select and BROWS the resulting cursor
3. Run the old 3 SQL Selects against the same data and BROWSE resulting cursor.
4. Compare - row-by-row the two cursors.
How else would you suggest that I test this change?
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
