Featured White Papers

• Measuring Risk to Improve Java Software Quality
• Do You Really Get Classloaders?
• Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
• Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
• Coding with JRebel, Java Forever Changed
• 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data

Sponsored Links

• Graph databases are 1000x faster than relational.

  Learn More!

• Career opportunities at Harman- Careers That'll Rock Your Socks Off.

  Learn More!

• Developer-friendly Java PDF libraries by Qoppa Software

  Live Demos

• Stop blaming your app! Diagnose Java performance issues.

  Free tool >

• UrbanCode: Go From Continuous Integration to
  Continuous Delivery

  Learn More!

Sponsored Links

Optimize with a SATA RAID Storage Solution
Range of capacities as low as $1250 per TB. Ideal if you currently rely on servers/disks/JBODs

Test for fun and profit, Part 3: The XML test framework

Test your Java code with an XML-based testing framework

By Todd Sundsted, JavaWorld.com, 12/29/99

For the last two months, I've described testing, I've explained its terminology, and I've explained how it works. This month, I move from the abstract to the concrete by presenting a simple framework for unit and component testing. If you're joining us for the first time, you might want to read the first two articles in the series before launching into our sample code.

A simple example

For the purposes of this article, we will build and test a simple scanner. Our scanner will search a string for javadoc tags (that is, lines that begin with the @ character).

Let's take a look at our scanner's code:

import java.util.Vector;
public
class Scanner {
  public
  int
  scan(Vector vector, String string, int nBegin, int nLength) {
    if (vector == null)
      throw new NullPointerException("vector");
    if (string == null)
      throw new NullPointerException("string");
    if (nBegin + nLength > string.length())
      throw new StringIndexOutOfBoundsException("nBegin + nLength > string.length()");
    if (nBegin < 0)
      throw new StringIndexOutOfBoundsException("nBegin < 0");
    if (nLength < 0) nLength = string.length() - nBegin;
    vector.removeAllElements();
    int n1 = string.indexOf("/**", nBegin);
    if (n1 < nBegin)
      return -1;
    int n2 = string.indexOf("*/", n1 + 3);
    if (n2 < 0 || n2 > nBegin + nLength)
      return -1;
    StringBuffer stringbuffer = null;
    int n = n1 + 3;
    while (n < n2) {
      int nEOL = string.indexOf("\r\n", n);
      int nNextLine = nEOL + 2;
      if (nEOL < 0) {
        nEOL = string.indexOf('\r', n);
        nNextLine = nEOL + 1;
      }
      if (nEOL < 0) {
        nEOL = string.indexOf('\n', n);
        nNextLine = nEOL + 1;
      }
      if (nEOL < 0) {
        nEOL = n2;
        nNextLine = nEOL;
      }
      if (nEOL > n2) {
        nEOL = n2;
        nNextLine = nEOL;
      }
      if (nEOL > n) {
        char c = string.charAt(n);
        while ((c == ' ' || c == '\t' || c == '*') && n < n2)
          c = string.charAt(++n);
        if (string.charAt(n) == '@') {
          if (stringbuffer != null) vector.addElement(stringbuffer);
          stringbuffer = new StringBuffer();
        }
        if (stringbuffer != null) stringbuffer.append(string.substring(n, nEOL));
      }
      n = nNextLine;
    }
    if (stringbuffer != null) vector.addElement(stringbuffer);
    return n2 + 2;
  }
}

The scan() method searches the supplied string for a javadoc-style comment (that is, a comment that begins with /** and ends with */). If it finds one, it searches the body of the comment for lines that begin with the @ character. These lines begin javadoc tags. Upon finding such a tag, scan() copies it, along with all subsequent lines up to the next tag or up to the end of the comment, into a collection. Once it has found all such tags, it returns both the collection and the point at which it stopped searching.