
|
[arachne]
||
[Date Prev]
[06-2005 Date Index]
[Date Next]
||
[Thread Prev]
[06-2005 Thread Index]
[Thread Next]
[arachne] Re: [a4dos-list] Re:Re:Re: Upgrade tests, requirements
- From: Scott Warnick <scottwarnick@xxxxxxxxxxx>
- To: arachne4dos@xxxxxxxxxxxx, arachne@xxxxxxxxxxxxx
- Date: Sun, 12 Jun 2005 22:56:23 -0600
Arachne at FreeLists---The Arachne Fan Club!
>Still, your approach is like looking for lost keys under a street light
>rather than where you lost them as the light isn't good enough to find
>them there. Greg is genuinely suggesting the final stage of testing,
>system testing, and what you propose intrinsically doesn't do that but
>only a lot of unit testing in one go. PML.
>GST+NPT=JOBS
>
>
>
Not sure I agree with this, so I'll just make some comments on testing.
1. If all of Greg's changes are to core.exe and arachne.bat then testing
with a new core is
a system test, since those are the only changes to the system.
2. I would suggest doing this the way we test release candidates on my
day job:
Step 1 - Create a clean install of 1.83 in a new directory (using any
convenient method).
Step 2 - Move in the new files from the change list, in this case
core.exe and arachne.bat
This is a full system test; the fact that you created the new system by
patching the old one is irrelevant for the
purpose at hand. (As is the distinction between unit tests and system
tests in some senses as core.exe is in most ways "the system".
Step 3 - When we are satisfied that the system works with the patch
install, we can move on to the full install,
which basically tests the install packaging and for any issues injected
by the install packaging.
As was previously noted it is the use of a development sandbox with
potential contamination by a developers work-in-process that
creates the distinction between advanced unit testing and system
testing. Everything done in a development sandbox
is unit testing by its nature.
And yes, I said "we". I now have my Borland 3.1 compiler up and running
and I have successfully compiled core.exe from the
nokey.prj file. I could just download modified source files,
compile core.exe myself, install it the way I just said and then report
my results (the way everyone else does). I would like to
start out by just testing and documenting at first as my DOS C
development skills are more than a little rusty.
Only thing is, it's been so long since I got things running that I've
forgotten where the developer's Yahoo group is. Glenn wrote it
all down for me but I've since deleted his very helpful instructions.
Could someone be so kind as to post them again..that way I could
get at the modified sources.
>[Sponsored by:]
>_____________________________________________________________________________
>The newest lyrics on the Net!
>
> http://lyrics.astraweb.com
>
>Click NOW!
>
>
>
>
Arachne at FreeLists
-- Arachne, The Web Browser/Suite for DOS and Linux --
|

|