<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 06/04/2010 13:22, Alfredo Deza wrote:
<blockquote
cite="mid:y2v212f9b21004060522sde352fd7ufd5c590f702d4b49@mail.gmail.com"
type="cite">Hi,
<div><br>
</div>
<div>I am trying to test as much as I can in a small project of mine.
However, the project has some network usage: pushes files from one spot
to another with Mercurial via SSH.</div>
<div><br>
</div>
<div>For now, I am creating a testing environment where I have some
SSH keys enabled and I am able to test this specific functionality.</div>
<div><br>
</div>
<div>However, I also have specific tests for all the
methods/functions involved. I had a user complain about the network
tests breaking (which is expected if he doesn't have a proper setup)
but I find it very</div>
<div>useful to have not only tests for methods/functions but also for
the final output: did the file actually made it?</div>
<div><br>
</div>
<div>Is this approach OK? </div>
<div><br>
</div>
<div>I have had situations where a test for a specific method didn't
picked up an error but the 'test_final_ouput.py' did (which made me
correct the tests).</div>
<div><br>
</div>
<div>Maybe I should not include them when distributing my project? Or
would documentation explaining how to set everything up so tests can
run correctly would be enough?</div>
</blockquote>
<br>
Having functional tests (end-to-end, integration tests, whatever you
want to call them) is a good thing - however ideally they should
*still* not rely on external resources. Really your test infrastructure
should setup the server your tests connect to locally. If these tests
have dependencies then you should document these.<br>
<br>
My 0.02c.<br>
<br>
Michael Foord<br>
<br>
<blockquote
cite="mid:y2v212f9b21004060522sde352fd7ufd5c590f702d4b49@mail.gmail.com"
type="cite">
<div><br>
</div>
<div>Thanks!<br clear="all">
<br>
-- <br>
Alfredo Deza<br>
<br>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
testing-in-python mailing list
<a class="moz-txt-link-abbreviated" href="mailto:testing-in-python@lists.idyll.org">testing-in-python@lists.idyll.org</a>
<a class="moz-txt-link-freetext" href="http://lists.idyll.org/listinfo/testing-in-python">http://lists.idyll.org/listinfo/testing-in-python</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.ironpythoninaction.com/">http://www.ironpythoninaction.com/</a>
<a class="moz-txt-link-freetext" href="http://www.voidspace.org.uk/blog">http://www.voidspace.org.uk/blog</a>
READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
</pre>
</body>
</html>