Recent changes to patches

DTD Correction of UDTs

Douglas Kvidera — Tue, 27 Jun 2006 14:20:30 -0000

sqlunit.dtd line 88 needs the following change to
support handling UDT outparams as <struct> elements:

<!ELEMENT connection
(((driver,url,user,password,(jarfile-url)?)|(datasource,jndi)?))>

should be:

<!ELEMENT connection
(((driver,url,user,password,(jarfile-url)?,(typemap)?)|(datasource,jndi)?))>

Adds support for UDTs as STRUCTs

Douglas Kvidera — Tue, 13 Jun 2006 03:11:59 -0000

Supports outparams as nested UDTs where fields are
JavaBean properties (less className and SQLTypeName).
Fields are sorted by name, case-insensitive.

Example:
<test name="My Test">
<call>
<stmt>begin ? := myFunct(); end;</stmt>
<param id="1" type="STRUCT" typename="MY_OBJTYP"
inout="out" />
<result>
<outparam id="1" type="STRUCT">
<struct>
<field name="aField">
<struct>
<field name="xField">red</field>
<field name="yField">23.5</field>
</struct>
</field>
<field name="bField">NULL</field>
</struct>
</outparam>
</result>
</test>

UDTs must be declared in the connection.

Example:
<connection>
...
<typemap>
<typedef typename="MY_OBJTYP"
classname="my.org.MyClass" />
<typedef typename="THEIR_OBJTYP"
classname="their.org.TheirClass" />
</typemap>
</connection>

Upgrade of Jdom.jar

Paul King — Tue, 11 Apr 2006 21:52:31 -0000

I upgraded to the final version of JDom and that
required the following patches (attached).

In addition to jdom-1.0.jar, I also upgraded:

log4j-1.2.13.jar
commons-logging-1.0.4.jar
commons-lang-2.1.jar

with no problems that I noticed - though many of the
unit tests seemed to assume a linux build environment.

Make Reporters fail when severe errors occur

Andreas Kutschera — Mon, 27 Mar 2006 15:12:03 -0000

When SQLUnit encounters a severe error, e.g.
a ClassNotFoundException when trying to load
the JDBC driver, the tests fail, but the reporter
reports a success.
This patch adds to the test failure count, so
the reporters knows that the tests failed.
I tested this with the canoo test reporter and
now I get a "successful='no'" instead of a 'yes' with
the full error message.
I do not know, however, if this breaks other tests!
Specifically, since there are so many
SQLUnitExceptions,
I did assume that all of them report some kind of
test failure. If that is not so, this patch
probably won't work.
The file that needs to be patched is SQLUnit.java.
Hope this helps
Andreas

set test name for reporting purposes

Andreas Kutschera — Tue, 21 Feb 2006 13:31:59 -0000

Currently all SQLUnit tests are called "sqlunit"
in the report files.
When you have many different SQLUnit tests (e.g.
as part of Canoo Webtests, where I click on a button
and want to find out if the internal database has
been changed), it can get quite confusing.
Therefore I suggest an addition to the ant task,
where sqlunit gets an extra attribute "name", that
defaults to "sqlunit", but may be set to any string,
so test reports give you a quicker view about what
failed and what didn't.
This patch is against SqlunitTask.java Version 1.8.

Make changed ant properties available to ant

Paul King — Sun, 20 Nov 2005 13:07:36 -0000

The enclosed patch provides the ability to return any
changed ant properties back to ant - they can then be
used elsewhere in the ant script. Ant properties are
sqlunit properties starting with the "${ant." prefix.

Example build file:
---
<sqlunit testfile="sqltest.xml" haltOnFailure="false"
failureProperty="sqlunit.failed"/>
<echo message="NumColumns=${sqlunit-numcolumns}"/>
<fail if="sqlunit.failed"/>
---
Example sqlunit test file:
---
<sqlunit>
<connection.../>
<setup>
<set name="${ant}">
<sql>
<stmt>select count(*) from AGECOMMENTS</stmt>
</sql>
<result>
<resultset id="1">
<row id="1">
<col id="1"
type="INTEGER">${sqlunit-numcolumns}</col>
</row>
</resultset>
</result>
</set>
</setup>
<test .../>
</sqlunit>
---

It also enables the support for failureProperty (the
set method must have been left out when we proposed
this some time back) - see the example above.

diff -c -r1.8 SqlunitTask.java
*** src/net/sourceforge/sqlunit/ant/SqlunitTask.java
28 Jul 2005 01:27:28 -0000 1.8
--- src/net/sourceforge/sqlunit/ant/SqlunitTask.java
20 Nov 2005 12:32:30 -0000
***************
*** 25,30 ****
--- 25,31 ----
import net.sourceforge.sqlunit.SQLUnit;
import net.sourceforge.sqlunit.SQLUnitException;
+ import net.sourceforge.sqlunit.SymbolTable;
import net.sourceforge.sqlunit.reporters.ReporterList;

import org.apache.tools.ant.BuildException;
*** 143,152 ****
--- 144,168 ----
throw new BuildException(e.getMessage());
}
} finally {
+ restoreAntVariables();
if (logStream != null) { logStream.close(); }
}
}

+ private void restoreAntVariables() {
+ Iterator it = SymbolTable.getSymbols();
+ while (it.hasNext()) {
+ String key = (String) it.next();
+ if (key.startsWith("${ant.")) {
+ String antkey = key.substring(6,
key.length()-1);
+ String value = SymbolTable.getValue(key);
+ if
(!value.equals(getProject().getProperty(antkey))) {
+ getProject().setProperty(antkey,
value);
+ }
+ }
+ }
+ }
+
/**
* Sets the value of the attribute testFile.
* @param testfile the full path name of the test
XML script.
***************
*** 164,169 ****
--- 180,193 ----
}

/**
+ * Sets the name of an ant property to set if the
sqlunit execution fails.
+ * @param failureProperty name of ant property.
+ */
+ public final void setFailureProperty(final String
failureProperty) {
+ this.failureProperty = failureProperty;
+ }
+
+ /**
* Sets the value of the attribute debug.
* @param debug can be set to true or false. If
true, returns the
* full stack trace of where the problem occured,
else returns a short

Ant task supporting multiple reporters and its testcases

Ivan Ivanov — Thu, 21 Jul 2005 20:07:21 -0000

The following patches contains an extension to current
<sqlunit> task that provides support for multiple
reporters. The contents of the reporters.zip is: src/
dir that contains the task implementation and
tests/src/ dir that contains the testcases for the task.

Documentation for tag

Ivan Ivanov — Mon, 13 Jun 2005 14:20:21 -0000

The attached zipped files contains:
1) javadoc.diff which stores the javadoc patches for
net.sourceforge.sqlunit.handlers.ClassifiersHandler /
CategoryHandler / SeverityHandler / SkipHandler.
2) tesgroupskip.xml is a short additition to SQLUnit
Users Guide and it should be merged in sqlunit-book.xml

Re: Support for customizable reporting

Paul King — Thu, 20 May 2004 10:23:56 -0000

Not sure this really belongs as a patch (perhaps it
should have been in the previous submission). Anyway,
this shows you the output you can get if you use the
previous patch.

Support for customizable reporting

Rob Nielsen — Wed, 05 May 2004 08:09:56 -0000

I have abstracted the reporting code formerly in
SQLUnit.java into a Reporter interface and added a
TextReporter which reports the same comments as the
existing code, and a CanooWebTestReporter which adds
support for outputting to an existing Canoo WebTest
results xml file. This allows users to run both Canoo
and SQLUnit and see the results on the same page.