db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "siddharthsrivastava/QuickStartGuide_NewDevelopers" by siddharthsrivastava
Date Thu, 31 Mar 2011 12:24:10 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The "siddharthsrivastava/QuickStartGuide_NewDevelopers" page has been changed by siddharthsrivastava.
http://wiki.apache.org/db-derby/siddharthsrivastava/QuickStartGuide_NewDevelopers?action=diff&rev1=7&rev2=8

--------------------------------------------------

  
   . b)     __  ____Building Derby from source:__
   . Refer to [[http://svn.apache.org/viewvc/db/derby/code/trunk/BUILDING.html?view=co|BUILDING.html]]
for  detailed instructions.
+  .  .  .
+  .  c)     __ ____Running Regression Tests__
+  . A quick introduction to get started:  There are two types of test in Derby: Harness Tests
and [[http://wiki.apache.org/db-derby/IntroToJUnit|JUnit]] Tests. We are converting the harness
tests to JUnit Tests . [[http://wiki.apache.org/db-derby/KillDerbyTestHarness#Goals|Why]]
?
+  . Whenever you make changes to the code, these tests need to be run so as to make sure
that the changes didn’t break any other part of Derby.
+  .  .  To run '''suites.All''' (the suite that runs all the JUnit tests in Derby), add junit.jar
to your classpath and run:
  
+  . ''          java -XX:MaxPermSize=512m  junit.textui.TestRunner org.apache.derbyTesting.functionTests.suites.All''
+  . (Note: It can take approximately 4-6 hours for regression tests to complete)
-  .  . c)     __ ____Running Regression Tests__
-  .   A quick introduction to get started:  There are two types of test in Derby: Harness
Tests and [[http://wiki.apache.org/db-derby/IntroToJUnit|JUnit]] Tests. We are converting
the harness tests to JUnit Tests . [[http://wiki.apache.org/db-derby/KillDerbyTestHarness#Goals|Why]]
?
-  .   Whenever you make changes to the code, these tests need to be run so as to make sure
that the changes didn’t break any other part of Derby.
-  .  .   To run '''suites.All''' (the suite that runs all the JUnit tests in Derby), add
junit.jar to your classpath and run:
  
+  .  . To run derbyAll (the suite for running harness tests in Derby), add jakarta-oro-2.0.8.jar
 to your classpath and run:
-  .                              ''java -XX:MaxPermSize=512m  junit.textui.TestRunner org.apache.derbyTesting.functionTests.suites.All''
-  .  (Note: It can take approximately 4-6 hours for regression tests to complete)
  
+  . ''                                ''''java org.apache.derbyTesting.functionTests.harness.RunSuite
   derbyall'''''''' '''
-  .
-  .        To run derbyAll (the suite for running harness tests in Derby), add jakarta-oro-2.0.8.jar
 to your classpath and run:
  
-  .  ''                          ''''java org.apache.derbyTesting.functionTests.harness.RunSuite
   derbyall''
+  .  . '''For detailed information about tests, refer [[http://svn.apache.org/viewvc/db/derby/code/trunk/java/testing/README.htm?view=co|Testing
README]] '''
  
+ '''Developer Tips:'''''' '''
-  .
-  .    For detailed information about tests, refer [[http://svn.apache.org/viewvc/db/derby/code/trunk/java/testing/README.htm?view=co|Testing
README]]
  
- '''Developer Tips:'''
+ '''1)       While running tests, clean your current directory containing any artifacts from
previous tests. Refer [[https://issues.apache.org/jira/browse/DERBY-5129|DERBY-5129]] '''
  
- 1)       While running tests, clean your current directory containing any artifacts from
previous tests. Refer [[https://issues.apache.org/jira/browse/DERBY-5129|DERBY-5129]]
+ '''2)       When you rebuild Derby,  if you face issues related to the build procedure (buildjars),
not being able to overwrite some of the existing jars, delete the existing jars from trunk/jars/sane
directory in run the buildjars (ant –quiet buildjars) again.See [[https://issues.apache.org/jira/browse/DERBY-5128|DERBY-5128]]
'''
  
- 2)       When you rebuild Derby,  if you face issues related to the build procedure (buildjars),
not being able to overwrite some of the existing jars, delete the existing jars from trunk/jars/sane
directory in run the buildjars (ant –quiet buildjars) again.See [[https://issues.apache.org/jira/browse/DERBY-5128|DERBY-5128]]
- 

Mime
View raw message