On 11/7/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
Stefano Bagnara wrote:
> The second connection made (using a connection limit of 1) expect
> to received a connection exception, instead it seems to get
> stalled waiting to connect.
If I understand you (and the code in testConnectionLimitExceeded) correctly, it
seems that the defect is in the test's assumption not the ServerConnection code.
The one (Test) can not live without the other (Testee) - and the other
way round, I'd say.
It is best practice to run, extend, adjust and re-run unit tests when
the implementation changes. Otherwise, the tests are pretty useless.
what needs to be changed is the test, not the revised ServerConnection. :-)
Right. Thanks for volunteering ;-)
Bernd
PS: google feeling lucky for "test infected"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
