Release date: not yet released
Release name: 0.0.9 alpha
CVS tag: release_0_0_9_alpha
Date Issue Type Comment
[57] XMLResultPrinter stylesheet incorrectly prints OK when tests fail
The message: OK (XXX tests) should only be printed if ALL tests pass, just as it is the case with AnsiColourResultPrinter. The stylesheet currently prints this messages even though tests have failed. The stylesheet seems to behave correctly if there are errors as well as test failures.
bug-fix ?????
[64] need to restructure regression testing
need to restructure regression testing to allow for easy, seperate testing of different UTF-X components
enhancement Full regression test has been broken up into three regression tests: Java, Samples and Tests. Each of the sub regression tests can now be ran individually.
[65] restructure 'tests' directory
UTF-X tests in the 'test' directory should be broken up into two categories 1. correct tests (expected to pass) 2. incorrect tests (expected to fail or generate error) correct tests should then be included in the full regression test and executed once for each transformer factory impl supported just as the samples
enhancement Tests have been grouped into three categories: good, failing and error. This allows for easier automated testing and result checking.
[61] incorrect usagge message
TestGenerator prints incorrect usage message; pls improve the documentation
bug-fix Corrected TestGenerator usage message.
[62] need an option to normalise white space
need to be able to normalise white space insode elements, so more complex source and expected fragments can be tested even after auto formatting by an XML editor. For example, one may want to consider the following two paragraphs as equivalent: <para>This is an example of some long pragraph with text which will wrap if formatted within an XML editor such as oXygen</para> <para>This is an example of some long pragraph with text which will wrap if formatted within an XML editor such as oXygen</para> This feature is over and above the Canonical XML 1.0 specification
bug-fix Added support for normalisation of whitespace inside elements. This feature is useful when large content chunks are used in utfx:source and/or utfx:expected elements.
[63] Typos in build.xml
--- build.xml~ 2006-08-23 11:34:36.000000000 -0400 +++ build.xml 2006-09-02 16:26:14.984075200 -0400 @@ -77,15 +77,15 @@ <!--~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~--> <!-- Java 1.5 bundled Xalan XSLTC processor - <property name="tarnsformer_factory_impl" value="com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl" /> + <property name="transformer_factory_impl" value="com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl" /> Xalan XSLTC processor - <property name="tarnsformer_factory_impl" value="org.apache.xalan.xsltc.trax.TransformerFactoryImpl" /> + <property name="transformer_factory_impl" value="org.apache.xalan.xsltc.trax.TransformerFactoryImpl" /> Xalan Interpretive processor - <property name="tarnsformer_factory_impl" value="org.apache.xalan.processor.TransformerFactoryImpl" /> + <property name="transformer_factory_impl" value="org.apache.xalan.processor.TransformerFactoryImpl" /> Saxon 8B XSLT 2.0 processor - <property name="tarnsformer_factory_impl" value="net.sf.saxon.TransformerFactoryImpl" /> + <property name="transformer_factory_impl" value="net.sf.saxon.TransformerFactoryImpl" /> --> - <property name="tarnsformer_factory_impl" value="net.sf.saxon.TransformerFactoryImpl" /> + <property name="transformer_factory_impl" value="net.sf.saxon.TransformerFactoryImpl" /> @@ -216,7 +216,7 @@ <!--~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~--> <target name="rt" depends="jar"> <java fork="true" classname="${testrunner}"> - <jvmarg value="-Djavax.xml.transform.TransformerFactory=${tarnsformer_factory_impl}" /> + <jvmarg value="-Djavax.xml.transform.TransformerFactory=${transformer_factory_impl}" /> <jvmarg value="-enableassertions" /> <jvmarg value="-Xmx512m" /> <classpath refid="runtime.classpath" /> @@ -279,7 +279,7 @@ <java classname="${testrunner}" fork="yes"> - <jvmarg value="-Djavax.xml.transform.TransformerFactory=${tarnsformer_factory_impl}" /> + <jvmarg value="-Djavax.xml.transform.TransformerFactory=${transformer_factory_impl}" /> <jvmarg value="-Dutfx.test.dir=samples" /> <!-- <jvmarg value="-Dutfx.test.file=samples/utfxdoc/test/utfxdoc_xhtml_test.xml" /> --> <jvmarg value="-enableassertions" /> @@ -356,7 +356,7 @@ <target name="tests" depends="jar"> <java classname="${testrunner}" fork="yes"> - <jvmarg value="-Djavax.xml.transform.TransformerFactory=${tarnsformer_factory_impl}" /> + <jvmarg value="-Djavax.xml.transform.TransformerFactory=${transformer_factory_impl}" /> <jvmarg value="-Dutfx.test.dir=tests" /> <jvmarg value="-enableassertions" /> <arg value="utfx.framework.XSLTRegressionTest" /> @@ -377,7 +377,7 @@ <target name="testfile-has-error" depends="jar"> <java classname="${testrunner}" fork="yes"> - <jvmarg value="-Djavax.xml.transform.TransformerFactory=${tarnsformer_factory_impl}" /> + <jvmarg value="-Djavax.xml.transform.TransformerFactory=${transformer_factory_impl}" /> <jvmarg value="-Dutfx.test.file=tests/test/broken_stylesheet_test.xml" /> <jvmarg value="-enableassertions" /> <arg value="utfx.framework.XSLTRegressionTest" />
bug-fix Fixed typos in build.xml. Patch sent by Tony Graham
[47] 5 failures when running rt on windows xp
jvm 1.5.0_06
bug-fix Fixed the test files by making them as binary in CVS. This stops CVS from changing End Of Line characters upon checkout. Corrected CanonicalForm implementation to correctly convert all EOL characters to '\n';
[49] TestRunner with utfx.test.file does not report errors
Found in branch_0_0_x STEPS TO REPRODUCE: * define ant target in build.xml <target name="test" depends="jar"> <java classname="${testrunner}" fork="yes"> <jvmarg value="-Djavax.xml.transform.TransformerFactory=$ {tarnsformer_factory_impl}" /> <jvmarg value="-Dutfx.test.file=tests/test/broken_stylesheet_test.xml" /> <jvmarg value="-enableassertions" /> <arg value="utfx.framework.XSLTRegressionTest" /> <classpath refid="runtime.classpath" /> </java> </target> * ant test ACTUAL RESULT: [java] OK (0 tests) EXPECTED RESULT: [java] Tests run: 1, Errors: 1 [java] Java Result: 1
bug-fix Fixed the test file by making setting as binary in CVS. CVS now correctly checks out the UTF-16 encoded file under Windows without converting EOL characters and therefore breaking the file.
Release date: 26 August 2006
Release name: 0.0.8 alpha
CVS tag: release_0_0_8_alpha
Date Issue Type Comment
Not completed
[44] implement change history management
need to manage history of changes in an XML file; the history.xml file should show releases with changelog of most significant enhancemts/bug fixes etc. This history should be integrated with issue tracking and CVS logs. It should be a UTF-X sample just as UTF-X Doc.
enhancement TODO JACEK
[47] 5 failures when running rt on windows xp
jvm 1.5.0_06
bug-fix Fix for CR/LF problem on Windows in CanonicalForm class which transforms an XML document into its canonical form.
[35] stylesheet out of synch with the DTD
XSL:FO stylesheet does not work as it is out of synch with the DTD
bug-fix Major improvements to rendering XSL:FO Test Definition Files.
[51] should render the output into HTML
As well as chosing a result printer to render test run result, one should be able to tell the framework to render the output into HTML and open the file in browser after test run. This HTML rendition should done be via the XMLResultPrinter, which can be done now, but transformation is an additional manual step.
feature New (default) option to render the test results into a HTML report and automatically open the file in browser after the test run.
[54] add libraries to utfx.jar manifest
the manual gives examples of using UTF-X from a command line but does not talk about CLASSPATH. If utfx.jar has all the required libraries in its manifest then it will be much easier to run it from the command line
enhancement utfx.jar now includes all required libraries in Class-Path property found in the manifest. Now you only need utfx.jar in your CLASSPATH to run the software from a command line
[45] stylesheet needs fixing
very ugly output
bug-fix Major improvements to rendering of XHTML Test Definition Files.
[52] XMLResulltPrinter does not output test name in error
When createing test summary for errors, the XMLResultPrinter does not output the name of the test that vaused the error
bug-fix Fixed a bug whereby XMLResultPrinter did not output test name when printing error summary.
[50] Support of named templates in TestGenerator
Currently the TestGenerator does not support named templates. It just inserts a comment into the generated TDF: <!-- ignoring name teplate XXX (not yet supported) -->
feature Generation of test skeleton for named templates with parameters.
[22] need ability to apply CSS to expected fragment
TDF should allow one to specify a CSS stylesheet which will be used to style the <utfx:expected> fragment. This feature will allow to produce more realistic HTML output. DTD will also need to be modified.
feature If you use a CSS stylesheet to style your generated (via XSLT) HTML, you can now use this CSS stylesheet when rendering your test definition file. This feature gives the expected fragment rendition a true look and feel when rendering HTML TDFs.
[49] TestRunner with utfx.test.file does not report errors
Found in branch_0_0_x STEPS TO REPRODUCE: * define ant target in build.xml <target name="test" depends="jar"> <java classname="${testrunner}" fork="yes"> <jvmarg value="-Djavax.xml.transform.TransformerFactory=$ {tarnsformer_factory_impl}" /> <jvmarg value="-Dutfx.test.file=tests/test/broken_stylesheet_test.xml" /> <jvmarg value="-enableassertions" /> <arg value="utfx.framework.XSLTRegressionTest" /> <classpath refid="runtime.classpath" /> </java> </target> * ant test ACTUAL RESULT: [java] OK (0 tests) EXPECTED RESULT: [java] Tests run: 1, Errors: 1 [java] Java Result: 1
bug-fix TestRunner now reports errors correctly in the test execution summary when executed with a single file (utfx.test.file).
[42] Absolute XPath Expressions can't be used
The root element passed to stylesheet under test is <utfx-wrapper> and not the child of the <utfx:source> element in the TDF. Therefore absolute XPath expressions can't be used in the stylesheet under test. ============================== STEPS TO REPRODUCE: Stylesheet under test: <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:template name="absolute-copy-of"> <xsl:copy-of select="/"/> </xsl:template> </xsl:stylesheet> TDF: <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="../../../src/xsl/test_definition_xhtml.xsl"?> <utfx:tests xmlns:utfx="http://utfx.org/test-definition"> <utfx:stylesheet src="absolute_xpath_tests.xsl"/> <utfx:test> <utfx:name>absolute xpath test</utfx:name> <utfx:call-template name="absolute-copy-of"/> <utfx:assert-equal> <utfx:source> <root> <branch> <leaf></leaf> </branch> </root> </utfx:source> <utfx:expected> <root> <branch> <leaf></leaf> </branch> </root> </utfx:expected> </utfx:assert-equal> </utfx:test> </utfx:tests> Actual result: [java] [1] absolute xpath test [java] actual: [java] <utfx-wrapper>< [ DIFF ] utfx-wrapper><root><branch><leaf></leaf></branch></root></utfx-wrapper></utfx-wrapper> [java] expected: [java] <utfx-wrapper>< [ DIFF ] root><branch><leaf></leaf></branch></root></utfx-wrapper> Expected result: Passed
bug-fix Added support for absolute XPath expressions in the stylesheet under test. Additionally the context node can be set with the context-node attribute in the utfx:source element.
[46] expected frgment validation fails parsing document
invalid utf-8 character (one byte encoding). This can be reproduced on Windows with the current version ( of address_book_xhtml.xml TDF. My guess is that the non braking character 0x160 is causing the problem. Oxygen claims that the document is well formed so my guess that this is caused by some intermediate DOM serialisation into a platform specific encoding (which I don't believe is utf-8 on windows). It works for me on Linux where the default platform encoding is utf-8.
bug-fix UTF-8 is now used in all String->byte[] and vice versa conversions
[24] Setting of XSL parameters
We have some stylesheets that use <xsl:param> (both top level and template level). Can there be some way in the test definition to set the value of these parameters?
feature Added support for named template and stylesheet parameters.
[34] The addres book sample is incomplete
Need to complete both XSLT stylesheets and the corresponding tests. Also need a larger sample XML document. You may want to add other elements to the DTD. I don't really care what you do with as it is a stand alone samples and does not have to comply with any utf-x structure/style rules. In fact it would be better if it was different to other stylesheets and TDF in the framework to show a slightly different way of using UTF-X.
enhancement Cleaned up the address book sample
[40] utf-x does not work with Saxon 8 on Windows
Xalan fails to correctly import import the stylesheet from the wrapper when running under Windows. Possibly '/' vs '\' issue.
bug-fix The imported stylesheet filename is now correctly converted to a relative URI to match the XSLT specification and Saxon8 implementation.
[33] t.g. should be able to use sample XML for generating TDF
currently the test generator parsers the stylesheet and generates tests based on the templates found in the stylesheet. for each template test generator creates an element with some text, passes the element through the stylesheet and uses source and output to form a utf-x test. It would be helpful if a user could also pass a sample XML document (or W3C Schema) to the generator (as well as the XSLT) and use that document/schema as the source of element structure. Generated tests would be then much more meaningful
enhancement You can now pass a sample XML document to the TestGenerator. By doing so the TestGenerator will generate a more meaningful Test Definition File.
[37] need a XSLT 2.0 stylesheet test
currently all tests (and samples) use XSLT 1.0 stylesheets; we should ensure the framework works with XSLT 2.0 as well.
enhancement Added a basic XSLT 2.0 stylesheet and a corresponding Test Definition File.
Release date: 2006-03-26
Release name: 0.0.7 alpha
CVS tag: release_0_0_7_alpha
Date Issue Type Comment
[21] source fragment is missing attributes
TDF rendition does not output source fragment attributes. Will be fixed in 0.0.7
bug-fix Attributes are now printed except for xmlspace. xmlns: etc
[25] regression test should include samples
utf-x sample unit tests should be executed as part of the regression test. furthermore, all samples should be executed once for each XSLT processor supported ; currently j2se5 buil in, xalan and saxon8 utf-x tests that are executed as part of the 'tests' target should also become part of the regression test but this is little bit more tricky as for some tests correct behaviour is to either fail or throw an exception. Some sort of a wrapper test case would have to be written.
enhancement Full regression test now runs all the samples once per each supported XSLT engine
[28] report validation errors in xsl and test xml
If the xsl or xml is invalid, you just get a message saying "0 tests" and you have to view the log file to see any errors. It would be useful to see any validation errors in the test summary.
bug-fix Broken TDF or XSLT stylesheet now produces an error in the report
[29] AnsiColourResultPrinter does not reset suite name
if there are TDFs at the same level as test directories with TDFs then the printer will print incorrect test suite name. This is because suite names are only set upon entering a suite and assumption was made that every suite name will be set correctly upon starting that suite. this does not work if a TDF follows a suite at the same level (ie a test case is a sibling of a test suite). Test suite names will have to be stored on a stack. This may also apply to other result printers.
bug-fix Fixed
[32] render XMLResultPrinterOutput
need a stylesheet to render output generated by the XMLResultPrinter so test results can be displayed in a HTML page
enhancement Regression test results can now be rendered to HTML
Release date: 21 August 2005
Release name: 0.0.6 alpha
CVS tag: release_0_0_6_alpha
Date Issue Type Comment
[3] utf-x does not work on windows
path problems on windows; need to write windows specific unit tests
[7] use-source-parser is ignored
if there is a <utfx:source-builder> element at the top level, it is always invoked even if use-source-parser="no" is specified on the <utfx:source> element.
[8] some named template tests do not work
this happens if the named template assumes that the current context node is what it expects. currently all named templates are called from the root node (i.e. utfx-wrapper), which is not always correct, instead the current context should be set to the first child element of <utfx-wrapper>.
[9] building the source fails in certain cases
this can happens when validate="no" and use-source-parser="yes". the root element is not initialised, so an invalid DOCTYPE is generated. also rawSource is not set under this situation, so an empty fragment is passed to the SourceBuilder.
[13] stylesheet out of synch with the DTD
this stylesheet needs to be updated so its usable; this is an important part of the system
[14] utf-x tries to validate source if utfx:source-validation element is not present
if a test definition file does not have <utfx:source-validation> element but validate="true" attribute is present on a <utfx:source> element then the framework attempts to validate the fragment ... and obviously fails cos no DTD is defined. validate="true" should be ignored on <utfx:source> elements unles <utfx:source-validation> is specified. Same applies to <utfx:expected> !
[15] <utfx:message> is ignored
for some reason <utfx:message> content is not used when test fails.
[17] component needs to be implemented
need to be able to generate UTF-X test definition file skeleton from a an XSLT stylesheet
[19] default result printer should be platform dependand
currently ANSIColourResultPrinter is the default result printer, but it does not work well on windows platforms as they do not suppport ANSI colour escaping. default result printer should be different for Linux and other platforms so result printing works well out of the box.
Release date: 26 March 2005
Release name: 0.0.5 alpha
CVS tag: release_0_0_5_alpha
Date Issue Type Comment
Release date: 14 March 2005
Release name: 0.0.4 alpha
CVS tag: release_0_0_4_alpha
Date Issue Type Comment
[2] error not reported if <expected> is not well formed
if <expected> fragment is not well formed then the test fails where error should be generated.
[1] UTFXTestCases requires unit tests
unit tests are required for all assert*() methods defined in UTFXUnitTest class
Release date: 20 February 2005
Release name: 0.0.3 alpha
CVS tag: release_0_0_3_alpha
Date Issue Type Comment
Release date: 7 February 2005
Release name: 0.0.2 alpha
CVS tag: release_0_0_2_alpha
Date Issue Type Comment
Release date: 31 January 2005
Release name: 0.0.1 alpha
CVS tag: release_0_0_1_alpha
Date Issue Type Comment