I'de like to make a suggestion to the user pool if I may... When I was at
KM3T's company (Mathworks) last year I got the grand tour and saw how a
professional software company develops software. They have a team of
software writers that work on their individual areas of the software.
Whenever they make a change, they submit the change. The change is
compiled and another computer starts running a check on the code for
errors. Kind of like faking the program into thinking someone was using
it. The testing program was running on top of THE program checking for bugs.
Well I dont think we have to write a program to test NA, but I do think we
have enough people using this program that if we all pulled together as a
team we could be as good as a program.
Say Dave comes up out with version 10.25 tomorrow. Each of us would be
assigned a particular part of the program to test. This would ensure that
everything was tested and that nobody forgot something. As it is now, we
only find out about bugs two days before the contest or during the contest.
We could divide it up like...
K4XYZ Tests all possible key strokes. ALT-Y, ALT-X, ALT-Z for errors.
K3XYZ Tests multi-op operation and related activities.
K1XYZ Tests two radio operation.
K0XYZ Tests DVP and Keyer operation.
Etc... I'm sure with enough volunteers we could really make this software
that much better. You cant expect Dave to beta test this software. WE
have to do it. I'm all ears.
73
Bill, W4AN
Bill Fisher, W4AN (EX KM9P)
http://www.contesting.com
--
Submissions: na-user@contesting.com
Administrative requests: na-user-REQUEST@contesting.com
WWW: http://www.contesting.com/datom/
Questions: owner-na-user@contesting.com
|