Just documenting my current thoughts. Not sure I'm actually on the dev
list again/still, but it's the right place for this rather than
inflicting it on j-users.
I'm pondering the cleanest way to move the currently-separate jira tests
into the main test suite. For example, the date formatting bug could be
run, as some of the existing tests are, by transforming into a
stringbuffer and checking that the zone offset is appropriately
formatted; I think we could use
System.setProperty("user.timezone","IST") to switch into the
fractional-hour offset mode to provoke the bug case.
But to really do this cleanly I'm doing some reverse-engineering of the
test framework, trying to recall the exact differences between the
various Testlet/Datalet Drivers. As the tests/bugzilla directory shows,
we did have ways of setting up a test directory with both simple
transform tests and explicit java Testlets (though the
BugzillaTestletDriver is a bit different from our usual setup and I need
to make sure I understand how.)
Note that tests/bugzilla is where we put tests for reported errors that
we were still working on, which is why some of them are stylesheet and
input which provoke the issue but don't have either a gold file or a
Testlet to execute and evaluate them.
Jira has replaced Bugzilla, so arguably we should now have an equivalent
tests/jira directory that demonstrates known unresolved issues, and they
should be moved into a directory that's part of the "live" regression
suite. This would require some updating of build.xml.
Yeah, I'm getting distracted by minutiae. I'd like to improve our
undersanding/doc for xalan-test so it's easier to deal with going
forward. But as a quick hack, I could just put jira-issue tests into
tests/bugzilla while working on them, and perhaps set up a
tests/jira-fixed which they'd be moved to when repaired, and
sanity-check whether they can be moved into the *right* test sets later.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
