On Friday 14 April 2006 14:35, Piers Cawley wrote: > Piers Cawley <[EMAIL PROTECTED]> writes: > > extra understanding from the first, failed solution. As I've explained > > in my blog[1], I'm not totally averse (but getting more averse by > > Oopsie. Forgot the footnote. Here it is: > > 1. http://www.bofh.org.uk/articles/2006/03/12/if-you-test-it-i-will-patch
Just out of curiosity, how does one test a feature which by its very nature
requires contact with a server somewhere? Is there a common Jabber server
which unit tests might be able to connect to, which would always be present
in order to test something like Jabber notifications?
The same problem exists with mail notifications, naturally.
One might say that you can stub the thing which sends the mail. But if you
also stubbed the thing which sends the instant message, the existing
notification for Jabber would seem to be working, because the broken code is
inside the method you would need to stub.
TX
--
Email: [EMAIL PROTECTED]
Jabber ID: [EMAIL PROTECTED]
Web site: http://trypticon.org/
GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F A62C B8C7 BC8B 037E EA73
pgpYiGpqoCWxM.pgp
Description: PGP signature
_______________________________________________ Typo-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/typo-list
