HI Tiago, Thanks... I was wondering what it is :D !!
On Sun, Apr 11, 2010 at 3:12 PM, Tiago Espinha <[email protected]>wrote: > Hello Nirmal, > > You have run a regression test already :-) in fact you've run the whole > bunch of them! The normal unit tests are what we call regression tests, > because they test features as they are supposed to be implemented. So if you > (or anyone else) makes a change that inadvertently changes the normal > behavior, one of these tests (on suites.All) will fail and then we say we've > had a regression failure. > > Also, when you implement something completely new, you're supposed to > create a new test that tests that feature. So that in the future if someone > breaks that, your test will fail, letting that person know that they've > broken it. > > Hope that helps, > Tiago > > ------------------------------ > *From:* Nirmal Fernando <[email protected]> > *To:* [email protected] > *Sent:* Sun, 11 April, 2010 6:05:23 > > *Subject:* Re: Fw: Juni Tests > > > Hi Kristian, > > Thanks for the very clear explanations on testing Derby !!! > > I'm quite new to the Derby community, but I think I'm learning many from > all of your replies. > > I have another question, I haven't run a regression test yet. I would be > grateful if someone help me to run a regression test. > > > Thanks !!!! > > > > On Sun, Apr 11, 2010 at 12:09 AM, Kristian Waagan <[email protected] > > wrote: > >> On10.04.2010 18:37, Nirmal Fernando wrote: >> >> Thanks Tiago !! >> >> Ya, I ran the command that Bryan had posted few mails ago. It included >> those maximizing memory allocation. >> >> By the way, at what times we need to run suites.All? Is it only when we >> create a patch? >> >> >> I run suites.All with as good as every patch I commit. >> The exceptions are JavaDoc changes only, or other trivial changes. >> Sometimes I have committed what I believed was trivial changes, and then one >> or more tests failed in the nightly tests run by members of the community... >> Sometimes tests fail on some platforms only, so you may see failures in the >> nightlies even if the tests passed on your own machine. >> Running the regression tests is a good way to root out problems with >> patches early on. >> >> If you're working on a patch and you know specific tests are failing >> (maybe after running suites.All for the first time), it is better to keep >> running the specific test(s) until the errors have been corrected, otherwise >> your iterations will take a very long time. When you feel the code is ready, >> you can start the full suite again. >> For JUnit, run >> org.apache.derbyTesting.functionTests.tests.[directory]._Suite to run all >> tests within the specified directory (a Derby convention). >> >> As I mentioned above, some people run suites.All every day and post the >> results to derby-dev. For instance, see Ole's results at >> http://dbtg.foundry.sun.com/derby/test/ . >> As a developer, unless you have a special interest in testing, running the >> regression tests when you test patches should be sufficient. >> Sometimes running the tests with a clean code base is helpful to verify >> that the tests are running fine on your machine. >> >> >> Regards, >> -- >> Kristian >> >> >> >> >> Thanks!!! >> >> On Sat, Apr 10, 2010 at 9:56 PM, Tiago Espinha >> <[email protected]>wrote: >> >>> Hello Nirmal, >>> >>> I'm glad that you finally got it running. The how long tests take to >>> run depends a lot on the machine you're running them on and even on the >>> operating system. There are a few tests that if I recall correctly take ages >>> on Windows but are much faster on *nix systems. >>> >>> Since you're running them on Windows and with an average dual core >>> computer, you're looking at at least 3 or 4 hours for the whole suites.All. >>> >>> Also be wary that if this: >>> >>> java junit.testui.TestRunner >>> org.apache.derbyTesting.functionTests.suites.All >>> >>> is the way you're running your suites.All, your run will most certainly >>> fail. There are some tests in suites. All that require a great deal of >>> memory and it's easy to exhaust the 128Mb(?) limit imposed by default on >>> each JVM. >>> >>> Here's what I use: >>> >>> java -Xms128m -Xmx1024m -XX:MaxPermSize=512m junit.textui.TestRunner >>> org.apache.derbyTesting.functionTests.suites.All >>> >>> I start with 128Mb of memory allocated, allow it to expand to 1Gb and >>> that last argument I believe has to do with the size of the heap, as it does >>> run out for some of the tests as well. >>> >>> Hope it helps, >>> Tiago >>> >>> ------------------------------ >>> *From:* Nirmal Fernando <[email protected]> >>> *To:* [email protected] >>> *Sent:* Sat, 10 April, 2010 17:17:33 >>> >>> *Subject:* Re: Fw: Juni Tests >>> >>> Hi All, >>> >>> I think I found the reason, it's just that I'm using Windows Vista not >>> Unix. >>> >>> So in Windows my CLASSPATH variable's value should be following: >>> >>> >>> %jardir%\derby.jar;%jardir%\derbytools.jar;%jardir%\derbyrun.jar;%jardir%\derbynet.jar;%jardir%\derbyclient.jar;%jardir%\derbyTesting.jar;%tstjardir%\jakarta-oro-2.0.8.jar;%tstjardir%\junit.jar;%jardir%\derbyLocale_cs.jar;%jardir%\derbyLocale_de_DE.jar;%jardir%\derbyLocale_es.jar;%jardir%\derbyLocale_fr.jar;%jardir%\derbyLocale_hu.jar;%jardir%\derbyLocale_it.jar;%jardir%\derbyLocale_ja_JP.jar;%jardir%\derbyLocale_ko_KR.jar;%jardir%\derbyLocale_pl.jar;%jardir%\derbyLocale_pt_BR.jar;%jardir%\derbyLocale_ru.jar;%jardir%\derbyLocale_zh_CN.jar;%jardir%\derbyLocale_zh_TW.jar >>> >>> Note: *In Windows you have to use %aa% instead of $aa and ";" instead >>> of ":".* >>> * >>> * >>> * >>> * >>> * >>> Now I'm running Suites.All !! :) Usually how long will take to last? >>> >>> Thanks for all of you for your replies !!! >>> >>> >>> * >>> -- >>> Best Regards, >>> Nirmal >>> >>> C.S.Nirmal J. Fernando >>> Department of Computer Science & Engineering, >>> Faculty of Engineering, >>> University of Moratuwa, >>> Sri Lanka. >>> >>> >> >> >> -- >> Best Regards, >> Nirmal >> >> C.S.Nirmal J. Fernando >> Department of Computer Science & Engineering, >> Faculty of Engineering, >> University of Moratuwa, >> Sri Lanka. >> >> >> > > > -- > Best Regards, > Nirmal > > C.S.Nirmal J. Fernando > Department of Computer Science & Engineering, > Faculty of Engineering, > University of Moratuwa, > Sri Lanka. > > -- Best Regards, Nirmal C.S.Nirmal J. Fernando Department of Computer Science & Engineering, Faculty of Engineering, University of Moratuwa, Sri Lanka.
