--------------enig71E725BE6BA61E6FBCC9BCC1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

James Mead wrote:
> Good to see such a well-argued, logical and rational argument for not using
> mocks in tests.

I'll have a pint of irony to go with that shot of sarcasm.

There's a time and place for mocks. Substituting resources / environment
that's not under your control during production / ever (the network,
user input) with mocks is indeed fine and useful, I even my life-saver
success stories with that. Substituting an essential runtime component
that is under your control at development-time, and operates predictably
or controllably, like a RDBMS, or a webserver to avoid their influence
on the test process is patent nonsense if the test is to provide
feedback on actual behaviour of the components.

David Vallner


--------------enig71E725BE6BA61E6FBCC9BCC1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)

iD8DBQFFMqCPy6MhrS8astoRAua9AJ0SlEFpUjWlwIY5zbg+RKvl9u9biwCfbuh4
u9ybNQ/ic2GgL377YdcEakkhD
-----END PGP SIGNATURE-----

--------------enig71E725BE6BA61E6FBCC9BCC1--