[TIP] structure of a testing talk
Hugo Lopes Tavares
hltbra at gmail.com
Tue Oct 2 09:33:48 PDT 2012
I don't see you mentioning tests as regression tests. It is very
important. You can use as an example someone new coming to the team.
That people is not used to the codebase, and without tests, he can
break stuff without even noticing.
And tests as documentation is very worth mentioning too, because it is
very useful to see how code works reading tests. You can see the
corner cases and lots of scenarios you may even not know about.
Congratz for the talk.
On Tue, Oct 2, 2012 at 11:33 AM, andrea crotti
<andrea.crotti.0 at gmail.com> wrote:
> 2012/10/2 Jonathan Hartley <tartley at tartley.com>:
>> On 02/10/2012 14:16, Jonathan Hartley wrote:
>> I think I answered my own question: I was mentally comparing the situation
>> *with* tests for Python versus for other languages. I should have been
>> comparing the situations *without* tests. An alien mindset. Thanks for being
>> my sounding-board.
> Yes that's the point.. In other languages you're in serious trouble
> if you don't test properly, in Python you're simply doomed ;)
> But on the other hand we have things like mock that more static
> languages don't have, so there are pros and cons..
> Another thing which people often say is "well it's just a small script
> I don't need tests", and then 3 months later is 5000 lines of
> monstruosity used in production.
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
More information about the testing-in-python