JUnit XML Output Without Ant

It's fairly common for Continuous Integration (CI) tools (e.g., Jenkins) to run unit tests from a testing framework (e.g., JUnit) and display their results.  JUnit, in particular, has an XML output format that is accepted by result formatters (e.g, JUnitReport, aforementioned CI tools, etc.).  The XML can be produced quite easily from an Apache Ant task with the following:

     <target name="test"> 

       <mkdir dir="${result_dir}"/> 

       <junit fork="no" printsummary="yes" haltonfailure="no"> 

          <batchtest fork="no" todir="${result_dir}" > 

             <fileset dir="build"> 

                <include name="**/*Test.class" /> 

             </fileset> 

          </batchtest> 

          <formatter type="xml" /> 

          <classpath refid="classpath" /> 

       </junit> 

    </target>

But what if you don't want to use Ant as your primary build tool?  I found that producing the XML output was undocumented by JUnit, so I did some digging.

It turns out that the XML output format isn't defined by JUnit, but by Apache Ant.  Ant has its own JUnit TestRunner and Formatter that produce the XML output.  Some reverse engineering showed that I can produce simple console output using the following command-line structure:

# java -classpath .:/usr/share/ant/lib/ant.jar:\

 /usr/share/ant/lib/ant-junit.jar:lib/junit-4.9b2.jar \ 

 org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner  \ 

 HelloTest \ 

 formatter=org.apache.tools.ant.taskdefs.optional.junit.SummaryJUnitResultFormatter  \ 

 showoutput=true

...and the output is:

Running HelloTest
Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.015 sec
You'll notice that I needed a few things in my classpath:

• My test class (HelloTest)
• Any classes that the test class uses
• Apache Ant & Ant's JUnit Task (from default Ant install)
• JUnit

The main class org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner is from the Ant JUnit task jar and it expects (at the bare minimum) a test class (i.e., a set of unit tests).


It also expects a series of key/value pairs which explain what to output and how it should be formatted.  The most simple set includes a "formatter" class and a boolean "showoutput."


If instead, you want to produce XML output, all you need is to replace the "formatter" above with: 

 formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,\
 ${PATH_TO_TEST_OUTPUT_DIRECTORY}/TEST-HelloTest.xml
...which looks like:

# java -classpath .:/usr/share/ant/lib/ant.jar:\

 /usr/share/ant/lib/ant-junit.jar:lib/junit-4.9b2.jar \  

 org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner  \ 

 HelloTest \ 

 formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,\
 ${PATH_TO_TEST_OUTPUT_DIRECTORY}/TEST-HelloTest.xml

This will produce an XML file which contains the results of the unit test(s).

Doxygen: Automatically Generated Documentation

I find that automatically generated documentation is a great way to explore an existing code-base.

Specifically, the documentation produced by Doxygen (www.doxygen.org/index.html) is very helpful.  Even better, Doxygen has support for a large number of languages and producing HTML, LaTeX, and man page documentation.  Here's an example (from http://www.scfbm.org/) of a Doxygen-generated UML class diagram:

Adding meta-information to the source code is as simple as documenting it via the prescribed documentation format.  For example, Doxygen reads Javadoc-style comments:

/**

 * A String representation of an object suitable for debugging.

 */

public String toString() {

...

It's also worthwhile to look at the tags (e.g., "@todo") that Doxygen supports for the language that you're using.

Doxygen uses a configuration file, or Doxyfile to determine the type and style of documentation to produce.  I find that the easiest way to get started is by using Doxygen's GUI configuration file wizard: doxywizard

I highly recommend enabling the advanced features in "Expert" mode under the "Dot" topic for:

• Class Diagrams,
• Collaboration Graph,
• UML Look,
• Include/Included-by Graph,
• Call/Caller Graph, and
• Graphical Hierarchy.

Also in "Expert" mode, enable the "Source Browser."  It helps to do fast-pased IDE-style code traversal while you familiarize yourself with the code-base.

Hibernate's Lazy Initialization

Exception in thread "main" org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: <CLASS>.<METHOD>, no session or session was closed

If you've ever received this error from Hibernate, you're not alone.  It happens because of Hibernate's "Lazy" initialization for joined relations.  It's a common problem because it occurs when you close the Hibernate session before you've accessed all the members that you need from the class --- which happens when you try to abstract the Object-Relational Mapping layer from the higher layers of your application.

For example: a Student class has a list of Classes.  Logically, you add the Hibernate queries for students to the Student class.  Your code likely has the following structure:

• Create a new session
• Make the query
• Close the session
• Return the result

Unfortunately, if you return the Student class, then query getClassList() --- you end up with a "Lazy Initialization Error."  This is because hibernate only does a query for the class list when you explicitly ask for it.

Here's a way for you to keeps higher-level classes from knowing about Hibernate, while maintaining the ability to create/destroy Hibernate session(s) appropriately:

    1 
  2 import org.hibernate.Session;
  3 import org.hibernate.SessionFactory;
  4 import org.hibernate.cfg.Configuration;
  5               
  6 /**           
  7  * Keeps track of Hibernate session for us
  8  */           
  9 public abstract class Queryable {
 10               
 11    /**        
 12     * Hibernate session
 13     */  
 14    private static Session session = null;
 15         
 16    /**  
 17     * Get (or create a new) hibernate session
 18     */
 19    public static Session getSession() {
 20       if( session == null ) {
 21          SessionFactory sessionFactory = new
 22            Configuration().configure().buildSessionFactory();
 23          session = sessionFactory.openSession();
 24       }
 25       return session;
 26    } 
 27   
 28    /**
 29     * Manually close the session.
 30     */
 31    public void closeSession() {
 32       if( session != null ) {
 33          session.close();
 34          session = null;
 35       } 
 36    } 
 37   
 38 }

Simply make the Student class extend Queryable and use getSession() everywhere you would have created or referenced the Hibernate session.  Don't forget to close the session when you're done with the object!

Also, thanks to the following website that gave me some insight into the problem:
http://www.javalobby.org/java/forums/t20533.html

Subgraphs in Graphviz Dot

Graphviz Dot is an extremely useful program for visualizing graph data (e.g., Finite State Machines, network topologies, etc.).  What makes Dot even more powerful is the ability to draw subgraphs (graphs within graphs).  This capability is a bit tricky, however, so here is the simplest "Hello World" I can give:

  1 digraph dfg {
  2    compound = true;
  3    subgraph cluster_parent {
  4       color=blue;
  5       label="Parent";
  6       A->B [lhead=cluster_child_1];
  7       A->C;
  8       subgraph cluster_child_1 {
  9          color=green;
 10          label="Child #1";
 11          B->C;
 12       }
 13       subgraph cluster_child_2 {
 14          color=green;
 15          label="Child #2";
 16          C->D [ltail=cluster_child_1];
 17       }
 18       D->E;
 19       E->B [lhead=cluster_child_1];
 20    }
 21 }

The program above produces:

The key (non-intuitive) pieces for working with subgraphs are:

1. Subgraph names must start with the string "cluster" --- for example, cluster_child_1.
2. Edges that terminate at a subgraph (e.g., Node A to Child #1) must have the attribute "lhead" defined as the subgraph name.
3. Edges that start at a subgraph (e.g., Child #1 to Node D) must have the attribute "ltail" defined as the subgraph name.

Synchronized Text Editor Configuration

One of my most common pieces of advice is to get familiar with a text editor, configure it to your liking, and use it for everything!  I'm partial to Vim, but my advice applies to any configurable text editor (*cough* emacs *cough*).

Configuring your text editor can be a very time-consuming process and there's nothing worse than having a different configuration on all of the various computers you use.  My recommendation is to keep your text editor configuration in version control (e.g., subversion, mercurial, etc.) as a way of maintaining your preferences over time, as well as keeping your configuration consistent on every computer you use.

I keep my .vimrc under version control in Github as a way of sharing it:

https://github.com/radarku/kvim

The reason I chose Github is this great article about keeping all your Vim plugins up-to-date using Git submodules:

http://vimcasts.org/episodes/synchronizing-plugins-with-git-submodules-and-pathogen/

Modeling Inheritance in Relational Models

If you've ever designed Relational Model, you probably discovered that there are different ways to model the object-oriented concept of inheritance in relational models.  This becomes particularly important when using an Object-Relational Mapping (ORM) library, such as Hibernate.

There are several ways to accomplish this modeling, but I'll only talk about two methods, which I call:

1. Differentiation on a "discriminator" field
2. Shared Primary Key

Differentiation on a "discriminator" field
With this solution, there is a single table for the parent, children, grandchildren, and so on.  In this table, one field is a "discriminator," from which the type of the object can be derived.  The benefit to this solution is that it is a very simple way to model inheritance.  Unfortunately, it's also not a very robust solution.  First, if the children/grandchildren/etc. have many (disjoint) fields, it can lead to a very sparsely populated table (i.e., lots of "NULL" values).  Furthermore, making changes to the structure of the objects or hierarchy can be very tricky.

id	type	parent_field	child_1_field	child_2_field
1	parent	1	NULL	NULL
2	child_1	2	1	NULL
3	child_2	3	NULL	1

Shared Primary Key
Another way of modeling inheritance in a relational model is by constraining the child's primary key (PK) as a foreign key (FK) to the parent's PK.  This solution makes changing the structure or inheritance hierarchy simpler than the "discriminator" solution.  It also eliminates the unnecessary "NULL" values for inapplicable fields.

Parent:

id	parent_field
1	1
2	2
3	3

Child_1:

parent_id	child_1_field
2	1

Child_2:

parent_id	child_2_field
3	1

Cropping PDFs

If you ever received a PDF with a lot of extraneous whitespace, there's a nice little utility to remove it quickly and easily:

# pdfcrop <PDF File>

see http://pdfcrop.sourceforge.net/

...and even better: if you're a LaTeX user, you might already have it because it's included in TexLive!

In Ubuntu, it's in the package: texlive-extra-utils