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?
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?
>
>
> _______________________________________________
> Post Messages to: ProFox@leafe.com
> Subscription Maintenance:
> http://leafe.com/mailman/listinfo/profox
> OT-free version of this list:
http://leafe.com/mailman/listinfo/profoxtech
=====
Since we haven't found Saddam Hussein yet, does that mean he never existed either?
A little pricey! In order to have the testing functions it is almost $900.
-----Original Message-----
From: Juergen Wondzinski [mailto:woody@prolib.de]
Sent: Thursday, October 16, 2003 2:26 PM
To: 'ProFox Email List'
Subject: RE: [NF] Testing procedures
Hi David,
what about that one:
http://www.hallogram.com/foxrunner/
It's a product of CAL, Germany:
http://www.cal.de/cgi-bin/index.pl?lang=e&js=1&content=../e/prod_foxrunner1.
html
(wrapped link)
Servus
wOOdy
|\_/| ------ ProLib - programmers liberty ---------
(.. ) Unsere MVPs bringen den Fuchs zum Laufen...
- / auf www.prolib.de und www.AFPages.de
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?
>
Hi David,
what about that one:
http://www.hallogram.com/foxrunner/
It's a product of CAL, Germany:
http://www.cal.de/cgi-bin/index.pl?lang=3De&js=3D1&content=3D../e/prod_fo=
xrunner1.
html
(wrapped link)
Servus
wOOdy
|\_/| ------ ProLib - programmers liberty ---------
(.. ) Unsere MVPs bringen den Fuchs zum Laufen...
- / auf www.prolib.de und www.AFPages.de
There is another pgm called automanual from Roger Woodsmall .
Works very well for testing MOST things in VFP -
web site used to be : http://www.woodsmall.com/index1.htm
but - have no clue where it is these days .
mondo regards [Bill]
--
William Sanders / Electronic Filing Group Remove the DOT BOB to reply via
email.
FREE LONG DISTANCE -> mailto:excel-info@efgroup.net
Free Satellite Receivers and installation ->
http://www.vmcsatellite.com/?aid=58456
mySql / VFP / MS-SQL
----- Original Message -----
From: "Crooks, David L." <croodl@ispec.com>
To: "ProFox Email List" <profox@leafe.com>
Sent: Thursday, October 16, 2003 1:25 PM
Subject: RE: [NF] Testing procedures
> A little pricey! In order to have the testing functions it is almost $900.
>
> -----Original Message-----
> From: Juergen Wondzinski [mailto:woody@prolib.de]
> Sent: Thursday, October 16, 2003 2:26 PM
> To: 'ProFox Email List'
> Subject: RE: [NF] Testing procedures
>
> Hi David,
>
> what about that one:
>
> http://www.hallogram.com/foxrunner/
>
> It's a product of CAL, Germany:
>
http://www.cal.de/cgi-bin/index.pl?lang=e&js=1&content=../e/prod_foxrunner1.
> html
> (wrapped link)
>
> Servus
>
> wOOdy
>
>
> |\_/| ------ ProLib - programmers liberty ---------
> (.. ) Unsere MVPs bringen den Fuchs zum Laufen...
> - / auf www.prolib.de und www.AFPages.de
>
>
>
[excessive quoting removed by server]
"Used to" is correct as the link does not work.
-----Original Message-----
From: William Sanders [mailto:wsanders@efgroup.net]
Sent: Thursday, October 16, 2003 2:56 PM
To: ProFox Email List
Subject: Re: [NF] Testing procedures
There is another pgm called automanual from Roger Woodsmall .
Works very well for testing MOST things in VFP -
web site used to be : http://www.woodsmall.com/index1.htm
but - have no clue where it is these days .
mondo regards [Bill]
--
William Sanders / Electronic Filing Group Remove the DOT BOB to reply via
email.
FREE LONG DISTANCE -> mailto:excel-info@efgroup.net
Free Satellite Receivers and installation ->
http://www.vmcsatellite.com/?aid=58456
mySql / VFP / MS-SQL
----- Original Message -----
From: "Crooks, David L." <croodl@ispec.com>
To: "ProFox Email List" <profox@leafe.com>
Sent: Thursday, October 16, 2003 1:25 PM
Subject: RE: [NF] Testing procedures
> A little pricey! In order to have the testing functions it is almost $900.
>
> -----Original Message-----
> From: Juergen Wondzinski [mailto:woody@prolib.de]
> Sent: Thursday, October 16, 2003 2:26 PM
> To: 'ProFox Email List'
> Subject: RE: [NF] Testing procedures
>
> Hi David,
>
> what about that one:
>
> http://www.hallogram.com/foxrunner/
>
> It's a product of CAL, Germany:
>
http://www.cal.de/cgi-bin/index.pl?lang=e&js=1&content=../e/prod_foxrunner1.
> html
> (wrapped link)
>
> Servus
>
> wOOdy
>
>
> |\_/| ------ ProLib - programmers liberty ---------
> (.. ) Unsere MVPs bringen den Fuchs zum Laufen...
> - / auf www.prolib.de und www.AFPages.de
>
This is a test.
I'm testing spam blocking software called "Choice Mail Free"
Anyone else using it?
Chet
--------------------------------------------
My mailbox is spam-free with ChoiceMail, the leader in personal and corporate anti-spam solutions. Download your free copy of ChoiceMail from www.choicemailfree.com
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
I thought Ed was for a minute and it blocked everthing <g>
Allen
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]
On Behalf Of Chet Gardiner
Sent: 27 October 2004 20:45
To: profoxtech@leafe.com
Subject: [NF] Testing Spam Blocker
This is a test.
I'm testing spam blocking software called "Choice Mail Free"
Anyone else using it?
Chet
It seems to be working well.
FYI, It's an opt-in system. When someone emails you they have to opt-in on
a web page. You then have the option to accept them in your whitelist or
not. I imported my address book and setup all of the email list names and
get those just fine. So far, so good...
C
----- Original Message -----
From: "Chet Gardiner" <chetdude@pacbell.net>
To: <profoxtech@leafe.com>
Sent: Wednesday, October 27, 2004 12:44 PM
Subject: [NF] Testing Spam Blocker
This is a test.
I'm testing spam blocking software called "Choice Mail Free"
Anyone else using it?
Chet
--------------------------------------------
My mailbox is spam-free with ChoiceMail, the leader in personal and
corporate anti-spam solutions. Download your free copy of ChoiceMail from
www.choicemailfree.com
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
[excessive quoting removed by server]