Re: Problem with setInputSource of SAXSource (re: writing API coverage tests)

[Sh...@lotus.com]

Yup - that's what API coverage tests should be: to start with, calling
every API at least once and validating it did the most basic thing
correctly.  That's what many of my testCase1() methods are - just calling
all variants of ctor's and set/get methods.  Most of DOM and stream looks
good on this front.  More checkins to come.

> Someone on either side, if you have time, should write a simple test that
does checks for all the non-abstract setters and getters in TrAX.  > The
problem here was a simple assign in setInputSource that went:
>-scott

- Shane