Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
Tony Hoyle [SMTP:tmh at nothing-on.tv] wrote: > sanity.sh breaks every time you change the wording of the output... I'd > prefer a script that checked what cvs did, rather than what it looked > like... cvsnt changes rather a lot & it would be a pain to modify a > script every time the output changed slightly (anyay it's shell script > so it won't run under NT). > > Changing the expected stdout and stderr to $(DOTSTAR) would disable most of the checks on the wording of the output. But perhaps checking this is a good way to keep compatibility with scripts that parse stdout or stderr from CVS. sanity.sh does at least some checking on changes to files and directories. I got sanity.sh running on windows NT 4.0 on cygwin B20 at CVS 1.9.28. Some tests (symlinks and others) I couldn't see how to make work on NT - so I skipped them. It was a lot of work to do, but my boss was happy to pay for it. And it took a long time to run (a few hours). > I've never seen a testing procedure that worked satisfactorily, though. > They're supposed to be developing one at work but it's the same > problem with 50 developers modifying bits of the code by the time > anyone has written a test script it's obsolete anyway. There is a 'sort > of OK' test script that just checks that program core functions are > reasonably sane, and that's as far as it goes. > > I haven't had that experience myself either. But the Extreme Programming folks report great results from their usual practices of writing unit tests before coding, testing everything that could possibly break, continuous integration with all unit tests passing 100%. I'm starting to adopt those practices as much as I can in my work. So far it feels pretty good to me. > Something that tested the basic functions - commit, import, add, remove, > etc. & checked the RCS files & repository for sanity would be nice. > It'd probably have to be a perl or python script. > > Back in september, devel-cvs had a message that Alexy Mahotkin was going to start "the hard work of converting the insanity.sh to Autotest" for whatever that's worth. Cheers, Murray. _______________________________________________ Cvsnt mailing list Cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs