I am thinking of more like number 6. This is for internal testing purposes

to make sure the changes have been thoroughly tested. Thanks!

-----Original Message-----

From: Michael Madigan [mailto:mmadi10699@yahoo.com]

Sent: Thursday, October 16, 2003 2:16 PM

To: ProFox Email List

Subject: Re: [NF] Testing procedures

1. Don't test it yourself, because others can break your

software in ways you never dreamed of:)

2. There are some books written on this very subject if you

check Amazon.

3. Create a test area for the software, a copy of the current

data, and let them bang away at it, that way any problems won't

interfere with live data.

4. On changes to reports, print out the before and after copies

to show your client.

5. On changes to screens, print out the before and after screen

captures of each screen.

6. On any changes to behaviour, write a written procedure to

prove that the function works. Like:

1. Enter data in field 1

2. Press button b.

3. Observe result.

--- "Crooks, David L." <croodl@ispec.com> wrote:

> Has anyone created any procedure for testing? I am trying to

> create some

> form of a checklist to make sure the new features work and also

> the rest of

> the application works as it should. Any ideas?

>