From: Aredridel <aredridel@...>
Date: 2003-09-05T02:00:14+09:00
Subject: Re: [OT] Unit Tests and Encapsulation


--=-1cnqXW5UOhvCGRTubiFP
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


> Are there general unit testing strategies for dealing with things=20
> outside the system you have control over?

You can always test the failure cases, too -- and when you find one you
haven't tested, add it to the suite.

Fake a 500.  Fake a 404.  Fake a timeout -- throw an exception that
could happen in your code.  Send it bogus data.  Send it good data.  All
should pass tests.  Use your intuition about what will possibly break,
and if you can, think of /all/ the ways it can break, if it's a
documented enough system.

Ari

--=-1cnqXW5UOhvCGRTubiFP
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQA/V2+AtP09exA3hooRAkd4AKCzlSFsXSH9LAXPmK+mcC+Q87F5gACg6Skt
5vMwbD1qVca7y3IVy3FOSrw=
=IGDA
-----END PGP SIGNATURE-----
0
--=-1cnqXW5UOhvCGRTubiFP--