This article is old and is being consolidated into the book.
Please refer to the corresponding chapter(s) therein.
If the chapters or sections are not completed yet, you can use this article.
Refer to the examples as they are tested against the latest code.

Table Of Content

Java White-Box Testing with Embedded JudoScript

By James Jianbo Huang    March 2002       non-printer version

Abstract   JudoScript allows seamless Java code invocation, hence is perfect for Java code white-box unit testing. The language engine explicitly supports this by allowing JudoScript code to be embedded in (the comments in) Java source files. Special tags enclose JudoScript code, and the engine extract and run them. JudoScript is also great for batch black-box and load testing.

 

JudoScript has two characteristics that make it an ideal testing language especially for Java software. They are a) seamlessly invoking Java code and b) rich application features. If you go through its readily available feature list, plus the potential to use any Java software as its extension libraries, you will find why JudoScript is a powerful batch black-box and load testing language.

This article focuses on JudoScript's white-box testing capability for Java. It has a feature that is designed especifically for this purpose -- embedded JudoScript code. It is like JUSP, except that this is not for generating web pages but rather embedding scripts in Java source files. It is very simple to use. In the Java source file, use a pair of special tags, /*[judo] and [judo]*/, to enclose any JudoScript code; you can have unlimited such JudoScript code segments. Then, simply "run" that Java source file with JudoScript: 

java judo Foo.java
the language engine will extract all the JudoScript code and run. The following is the source code:

Listing 1. Foo.java 
public class Foo
{ 
   /*[judo] 
     function ut_sum { 
       println 'UnitTest: int sum(int[])'; 
       x = javanew Foo; 
       ia = javanew int[] { 1, 3, 5 }; 
       println 'Is this 9? -- ', x.sum(ia); 
       println 'For null -- ', x.sum(null); 
     catch: 
       $_.printStackTrace(); 
     } 
   [judo]*/ 
   public int sum(int[] ia) { 
     int sum=0; 
     for (int i=0; i<ia.length; i++) sum += ia[i]; 
     return sum; 
   } 
} 
/*[judo] 
   println '[UnitTest: class Foo]'; 
   ut_sum(); 
   println '[/UnitTest]'; 
[judo]*/

This incredibaly simple scheme is incredibly effective and efficient. It is better than Java unit testing with Java code for these reasons:

  • Simple, straightforward, concise. No need to adopt frameworks to create a multitude of test classes (in Java) for testing. No house-keeping code.
  • Easy to run and maintain. No need to compile. Just modify and run.
  • Easy to organize test cases. With the help of !include, you can use common testing libararies and/or testing-time parameters.
  • JudoScript's rich application features help in white-box tests, too. Tests typically need to set up environment; JudoScript is designed to manipulate computer resources including data. Java is a system language, calling APIs to set up is not a pleasant task for most programmers.

JudoScript source code itself uses embedded JudoScript code. In file MethodOrdinals.java, JudoScript code is used to detect ambiguous or replicated function ordinals. In file VariableAdapter.java, JudoScript code tests the basic methods used by all the value types.


Copyright c 2001-2021 JudoScript.COM. All Rights Reserved.