db-jdo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jdo Wiki] Update of "TestingAndBuilding" by RichardSchilling
Date Fri, 12 Sep 2008 17:23:44 GMT
Dear Wiki user,

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

The following page has been changed by RichardSchilling:
http://wiki.apache.org/jdo/TestingAndBuilding

------------------------------------------------------------------------------
  
  You've made a modification to the JDO code which you've already checked out from the SVN
repository.  And you have successfully built the source (with your new changes).  Now you
need to build a test to be certain your change works.  This is as important as making the
change itself, and a requirement of the JDO project to get your changes accepted.  
  
- This web page will walk you through the process.
+ The following steps, which are discussed below, is what you'll be doing to set up a successful
test:
+ 
+  1. Familiarize yourself with the test environment
+  2. Write your test code.
+  3. Set up configuration files.
+  4. Run your test. 
+  5. Examine the output of your test. 
  
  
-  1. Familiarize yourself with the directory structure associated with the test code, and
use your favorite IDE to do some discovery.
+  === 1. Familiarize yourself with the test environment ===
+ 
+ 
+     You're going to save yourself a lot of time if you take a few moments to examine the
directory structure associated with the test code.  You should use your favorite IDE just
to cruise around the directory tree and familiarize yourself with what you see.
  
  
      My preferred way of working code on a project is to just use the lowest common denominator
of tools to get the job done.  This usually means the VI editor for writing code, and build
tools (e.g. compilers and repository management tools) that can be run from a simple UNIX
command line.  Keeping things simple like this means you don't need more than that to get
your work done, and quite frankly, it's a much more efficient way to work because you don't
have to mess around with windowing GUIs, IDEs and the like.  And, you get the added benefit
of having your working build environment be identical to the production build environment
(which runs nightly in batch on a different box).
@@ -36, +45 @@

  
  
  
-  2. Add to the existing test code so that it stimulates the lines of code you changed in
the JDO source tree.
+  === 2. Write your test code. ===
+ 
+     Now that you've familiarized yourself with the test environment, you are ready to write
some test code.
  
      More coming soon ...
  
-  3. Set up configuration files.
+  === 3. Set up configuration files. ===
  
      More coming soon ...
      
-  4. Run your test.
+  === 4. Run your test. ===
  
      More coming soon ...
  
-  5. Examine the output of your test.
+  === 5. Examine the output of your test. ===
  
      More coming soon ...
  

Mime
View raw message