I'm still having problems running the tests but I am getting further now that I have the right test files. Also I don't see any mention of which tests are run.
Running just regard essentially runs all tests (over a thousand).
Before you said I need to write a test like xml-batik/test-sources/org/apache/batik/transcoder/image/ GenericDocumentTest.java.
Regard creates/populates a directory called 'test-reports' at the
top level. This directory should contain directories with the current date/time (when regard completed). These directories then contain
html and xml subdirs, you want 'html' and that has regardReport.html
which has the test results for the tests run.
> How do I tell if these tests are successful?
Read the report. :)
It summarizes pass/total then gives an index of all the failed tests with a link to the test results for that test.
You can run subsets of tests by giving a string to regard like:
./build.sh regard text
Will run all the tests with 'text' in their 'id'.
The top-level 'manifest' of tests is located in:
test-resources/org/apache/batik/test/regard.xml
This then references lots of other test suites. Like .../batik/test/samplesRendering.xml, or .../batik/transcoder/image/unitTesting.xml which has the Generic Document test.
Here is the result of my 'ant regard': regard: Loading document ... Running test run... Running samplesRendering Running samples Running samples/anne.svg
[...] You are running on MacOSX? I am very surprised that these pass this means that the MacOSX renderer is pixel & sample accurate with Windows. Which I was distinctly under the impression it wasn't...
Running tests.spec.color
Running samples/tests/spec/color/colorProfile.svg
Exception in thread "main" JavaAWT: Assertion failure: Java exception thrown
It looks like Mac OSX does not like color profiles! The simplest thing to do is either just run the transcoder.image tests (build regard transcoder.image). Or remove tests that fail hard like this one from your local copy of the regard test "manifest" files. This file would be in samplesRendering.xml.
It stalled on the last test and I had to kill the java process.
Yah if the test hoses the JVM we are SOL. Otherwise the tests are very good about catching errors and reporting them in the test report.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
