in reply to No plan "weakens" my Test scripts?

What if there's a problem in your test data and you end up loading ten times the number of records that you intended to run? How will you catch that?

Suppose a query changes and accidentally pulls too much or too little data. How will you catch that?

I feel a little more paranoid than usual any time my tests have loops or depend on data that comes from somewhere else. I really like having test plans there to catch my assumptions then.

Replies are listed 'Best First'.
Re^2: No plan "weakens" my Test scripts?
by thor (Priest) on Feb 08, 2005 at 12:44 UTC
    What if there's a problem in your test data and you end up loading ten times the number of records that you intended to run? How will you catch that?
    Because one of the tests is "count it on the database". If I ended up loading 10 times as much data, count on the database would be inflated and therefore not equal.

    I should be clear here, I'm not testing a module...I'm testing that a database conversion went as expected. In college, I had a warehouse job. Our mantra there was "If it came in by count, count it. If it came in by weight, weigh it". That's exactly what I'm doing here. I do counts before and after as a first level check. One of the tables is non-normalized in that it has the same 3 columns repeated over and over to reperesent different things (think a family; the columns are dad's hair color, occupation, and age, mom's hair color, occupation, and age, etc). There are a different number of sets depending on the database. For each of these sets of columns, I want to check that it got into the normalized structure correctly. Once the counts are verified, I "weigh" it. That is to say that I make sure that the quality of the data before and is the same.

    thor

    Feel the white light, the light within
    Be your own disciple, fan the sparks of will
    For all of us waiting, your kingdom will come