On 29/01/07, John Kaputin <[EMAIL PROTECTED]> wrote: [...]
Many of the Woden unit tests do use impl classes directly, violating the Woden API. I've even written some of these myself! This was done for convenience originally - short cuts when creating tests, but as Woden has evolved it has become more important to use the API correctly. These unit tests don't actually break, either because setters have been used to correctly initialize them or because they don't exercise the code paths that might cause problems when not correctly initialized. However, as users may end up looking at the test cases for coding examples I think we should review them and change them to use the API where it's easy to do so.
+1 to that.
And document the exceptions if there are any (e.g. it might just be easier in some cases to set up a complex test case programmatically by using non-API techniques).
wouldn't that mean users have an excuse to do the same. 'White box' unit tests should be allowed to use ctors - we could document these tests as such and discourage users to copy the code. Cheers, Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
