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.
Anders Jacob Truelsen wrote: > Instead of writing a huge test with cases for this and that scenario > there must be a standard test that is run when a new release is build. I > know at least CVS used to have such a thing that all new features had to > first survive and secondly to extend. The core functionality is tested using the testcvs script that is in the source tree (you'll need python to run it). That covers the stuff that everyone uses, and makes sure the build actually does basic stuff like checkout, branch and commit. On neat trick I've found recently is to use the eclipse JUnit tester for teamcvs on it - it fails in 3 cases out of 143 on my 58b builds but they don't look like critical cases... that seems quite thorough. The only known problem with 58a at the moment is the XML library I use (expat) keeps falling over if it's passed certain non-ascii characters (may be an issue for you in denmark...) I've got a workaround for that that'll be in 58b. Also eclipse has problems with module browsing in 58a and I've got a workaround for that in 58b. Tony