| Home >> All >> org >> jxcl >> jxunit |
Package Samples:
• org.jxcl.jxunit.textui
• org.jxcl.jxunit.reports
• org.jxcl.jxunit.cover.stmt
• org.jxcl.jxunit.frontend.ant
• org.jxcl.jxunit.runner
• org.jxcl.jxunit.framework
Classes:
• JXunitTask: Ant task for running JXunit and JUnit. The JXunit Ant task is meant to be a plug-in replacement for the Ant JUnitTask. Whatever build.xml works with JUnitTask should behave identically with JXunitTask. The opposite is not true: using JXunitTask allows you to run coverage tests in addition to JUnit unit tests Parameter names / build file options are compatible with the build.xml options for JUnitTask as of Ant 1.5.3-1, so that if <junit> and </junit> are replaced with <jxunit> and </jxunit> respectively in the build.xml file, test behavior should be the same. Build file options ...
• StmtRegistry: Registry for statement coverage information. As JXunit-instrumented classes are loaded, they register their z$$z hit count arrays and are assigned an ID unique in the life of the registry. The registry maintains: hit counts , keyed on class name method end counter indexes , keyed on class and method name line number ranges , keyed on class and counter index This and other information in the registry allows it the generate a number of reports summarizing coverage at package level (soon) class level (now) method level (now) line level (soonish) The registry is associated with the JXunit class loader ...
• ClassAction: Add instrumentation at the class level, creating <clinit> if necessary. Three fields are added and initialized: z$$z , the int[] hit counts array z$$zID , a class identifier unique within this run z$$zStmtReg , reference to the StmtRegistry z$$zVer , a JXunit class file format version All of these fields are public final static . They are initialized by clinit when the class is loaded, running bytecode inserted by JXunit.
• CounterVertex: A CodeVertex which carries counter instrumentation and a label. The counter has an index. Whenever the flow of execution passes through this vertex, the counter code adds 1 to the hit count table, to z$$z[n] , where n is the counter index. Counter indexes are unique and assigned consecutively. They are not the same as vertex indexes. In the current revision of the software, counter vertices are also labeled with the counter index.
• MethodAction: Process a MethodGen method before and after graph creation and manipulation. A JXunitClassLoader can have any number of such pre/post-processors. The preprocessors will be applied in order before graph generation and then the postprocessors will be applied in reverse order after graph manipulation is complete. If any fatal errors occur, transformers must issue a warning message on System.err and either undo any changes or set method to null.
• JXunitTest: Parameters for controlling an individual task. These are and must be compatible with names used in Ant build.xml build control files. Most are set by methods whose name is derived from the variable name -- for example fork is set by setFork(b) .
• TestStmtCoverage: This is derived from org.jxcl.cl.TestTransformer; it instruments the test-data classes and the classes synthesized by ClassFactory. All of the instrumented classes are run and checked to see that they produce normal output, despite the instrumentation ;-)
• GraphAction: Walk the control flow graph, adding counter vertices on all edges inbound to code vertices. XXX Except those likely to cause problems; need to review this code later to make sure that all possibilities are covered.
• Scheduler: Collects individual and batch tests during initial processing of the Ant build.xml file, then schedules tests for running. Before running any tests, batch tests are unpacked and attributes assigned.
• BaseTestRunner: Stand-along JXunit test runner, fully compatible with Ant's JUnit options. Accepts options from Ant via JXunitTask; can also be run from the command line using TestRunner.
• XMLFormatter: Produce an XML document containing the test data for the run. This will in general contain the results of many tests, but only those resulting from one JXunitTest.
• ForkTest: Run an individual test in a separate JVM. Search on Ant Bug 23150; needs to return correct status code if interrupted or times out.
• MockExec: Echoes attributes for a given JXunitTest back to the Ant user. Useful in finding out how Ant and JXunit interpret your batch.xml.
• Formatter: Interface presented by all Ant/JXunit-compatible test result formatters. Extend BaseFormatter to build new formatters.
• CallTest: Handles an individual JXunitTest suite by directly calling it rather than forking it.
• Textui: Template textui test runner. Need to add main() and runWithIt().
• SummaryAttribute: Accept a limited set of String values for the summary attribute.
• MockTestRunner: Echoes parameters for a given JXunitTest back to the Ant user.
• MockTestRunner: Minimal test runner; just echoes the test description.
• BatchTest: Stores Ant filesets and convert them to JXunitTests.
• TaskControl: Run control parameters from the Ant build.xml file.
• Msg: Debug message module. XXX No longer used anywhere?
• BaseFormatter: Basic test result formatter for Ant/JXunit/JUnit.
• Runner: Abstract class extended by JXunit test runners.
| Home | Contact Us | Privacy Policy | Terms of Service |