<div dir="ltr">Ah, then I agree. Hence the term "microtest" (credit to geepawhill).<div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, May 9, 2017 at 9:22 PM Ben Finney <<a href="mailto:ben%2Bpython@benfinney.id.au">ben+python@benfinney.id.au</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Tim Ottinger <<a href="mailto:tottinge@gmail.com" target="_blank">tottinge@gmail.com</a>> writes:<br>
<br>
> Actually, the type of test is important to TDD.<br>
<br>
I didn't mean to imply otherwise. What I'm doing is distinguishing TDD,<br>
wihch is a process, versus the kind of test being written.<br>
<br>
TDD is *not* a kind of test. TDD is a process for developers to follow.<br>
<br>
If one is describing a kind of test to write, “TDD” is not a helpful<br>
term for that.<br>
<br>
That was my contention.<br>
<br>
--<br>
\ “The Way to see by Faith is to shut the Eye of Reason.” |<br>
`\ —Benjamin Franklin |<br>
_o__) |<br>
Ben Finney<br>
<br>
<br>
_______________________________________________<br>
testing-in-python mailing list<br>
<a href="mailto:testing-in-python@lists.idyll.org" target="_blank">testing-in-python@lists.idyll.org</a><br>
<a href="http://lists.idyll.org/listinfo/testing-in-python" rel="noreferrer" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a><br>
</blockquote></div>