[TIP] structure of a testing talk

[Gabriel Pugliese]

I mean, if you are talking to *experienced* developers :)
*--

Gabriel Pugliese* +55 11 9-9374-2720
http://www.blogcloud.com.br



On Wed, Oct 3, 2012 at 12:21 AM, Gabriel Pugliese <
gabrielhpugliese at gmail.com> wrote:

> If you talking to developers, tell them how can they improve Python
> testing...we could have some record testing that I wish it was built, like
> vcr.py [1] (Just a proof-of-concept from Ruby)
>
> [1] https://github.com/kevin1024/vcrpy
>
> *--
>
> Gabriel Pugliese*+55 11 9-9374-2720
> http://www.blogcloud.com.br
>
>
>
> On Tue, Oct 2, 2012 at 1:33 PM, Hugo Lopes Tavares <hltbra at gmail.com>wrote:
>
>> Hey Andrea,
>>
>> 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
>> > http://lists.idyll.org/listinfo/testing-in-python
>>
>> _______________________________________________
>> testing-in-python mailing list
>> testing-in-python at lists.idyll.org
>> http://lists.idyll.org/listinfo/testing-in-python
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20121003/e39fcbd7/attachment.htm>