From: Kent Beck <kentbeck@cs...> - 2001-10-22 15:45:05
">Doesn't this put us back in the serialization business?
not necessarily, creation of TestEvents would
happen on the client side only. In the remote test runner case the test run
server sends Strings and the client (RemoteTestRunner in the remote AWT UI)
wraps them into TestEvents."
Okay, so we'll base the TestRunListener on TestEvents. I noticed, Erich,
that your remote runner had it done both ways.
From: Vladimir Bossicard <vladimir@bo...> - 2001-10-22 19:02:25
> Okay, so we'll base the TestRunListener on TestEvents. I noticed, Erich,
> that your remote runner had it done both ways.
Where can I have a look at some code? What I have done is the
TestResult communicating with TestEvent and I'm interested in seeing
I personally find my solution (the TestResult doing all the dispatching
work, for UI and non-UI listeners) quite heavy.
From: Kent Beck <kentbeck@cs...> - 2001-10-22 20:17:47
I'll send the code when I've had a chance to change it in Erich's suggested
direction. TestResult doesn't seem the right place to broadcast all
messages, at least not yet. However, what is now the BaseTestRunner is
likely to get thinner and thinner. I can imagine we will want to merge it
with TestResult, but only after the diet.
Get latest updates about Open Source Projects, Conferences and News.