Hearing no objectsions :) I went ahead and added this into
jaxws-test-harness and then integrated into wsit workspace. Disabled
wsrm/dispatch (harness shortcoming) and wsrm/testserver (incompletely
ported tests). Added as optional 'skip' attribute on main
'test-discriptor' element (defaults to false).
This leaves one failure which appears to be an issue in the WS Trust
code itself. Jiandong is aware of it and said this AM he would look
into it today. Once that is fixed, we will show finally zero
failures... I'll send a note to that effect to tango-tech and make sure
people know that when they do local runs, they should also be getting
zero errors/failures before checking in.
Ken
Ken Hofsass wrote:
> Hi Kohsuke & Co,
>
> I would like to propose adding an attribute(?) to the test descriptor
> to mark that its test instance should be skipped. I'm proposing for
> situations like the one we have with wsrm/dispatch, where a structural
> change in the underlying JAXWS/WSIT infrastructure has broken or
> caused/exposed shortcomings in the test harness. And also for the
> case (which shouldn't really happen) when someone checks in
> incomplete/broken tests (which is causing two test failures right now).
>
> Comments or other ideas?
>
> thanks,
> Ken
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_ws-test-harness.dev.java.net
> For additional commands, e-mail: dev-help_at_ws-test-harness.dev.java.net
>