Managing A dev system

[Jerry Crespi]

At 03:01 AM 3/14/2014, you wrote:
>Does anyone use a development system for testing ?
>
>How do you make sure all changes are made after a new program is tested?
>
>Lots of notes?
>
>Richard

I also use the checksum of files and compare them between my dev 
system and the user systems.

In windows, I use sum.exe which is a DOS compilation of the UNIX sum 
(gnu.org) . In UNIX use sum.  Before I make a tar file or zip file, I 
make a list of the files.  Then I use the list to make the tar or zip 
file and to run sum on each of the tables to be transferred.  I pipe 
the results to a text file, and include the sum results text file in 
my tar or zip file.
Then, on the user system after extracting  the files, which included 
the file list and sum list, I run sum again piping the list file to 
sum and pipe the results to a new text file.  I can then run diff, or 
fc onmy original sum file and the user originated sum text and it 
picks up the differences.
Most of the time, the difference is because my change didn't go to 
the correct directory, or did not overwrite the older version.

This is useful when making a lot of changes, not for just one or two 
files. It takes longer to describe it, then to do it.
This is done before I begin testing on the user system, as others suggest.


Jerry Crespi, Ph.D.
President
Allied Business Systems Inc.
V. (714) 963-5554
F. (714) 964-0061  



-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4336 / Virus Database: 3722/7196 - Release Date: 03/14/14