Yes, in the patch that I posted for TUSCANY-1264, this is exactly
what the JUnit tests in sca/itest/samples do. Not perfect, but
better than nothing. It may be possible to add some level of
output checking, but I haven't attempted this yet.
Simon
Jean-Sebastien Delfino wrote:
[snip]
Simon Nash wrote:
It exercises the non-JUnit sample client code to make sure it runs.
Ah OK, I understand now :) I'm +1 on having these separate itests as
well then. Are we just going to make sure that they run without throwing
exceptions?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
