# from Keith Lofstrom
# on Thursday 12 April 2007 11:11 am:
>So if you want to move forward, help figure out a testing method. To
>start with, testing will be manual.
As I mentioned before, I'm pretty certain that overriding
CORE::GLOBAL::system() is a workable method to zero-impact testing.
That at least gets us to the point of verifying that the rsync command
is right. It probably also makes it possible to check the error
handling. It is going to cause trouble if the code checks the
filesystem (e.g. with -e $filename) or tries to write files
before/after the sync.
The only part keeping me from doing it is that I can't find stopped
clock.
The trouble with manual testing is the latency and disconnect. It takes
so long to get a change tested everywhere that you might have already
moved-on to layering other changes on top of it by the time a tester
reports a bug. Further, mis-communication and human error adds another
layer of complexity.
--Eric
--
"Matter will be damaged in direct proportion to its value."
--Murphy's Constant
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
_______________________________________________
Dirvish mailing list
[EMAIL PROTECTED]
http://www.dirvish.org/mailman/listinfo/dirvish
