[Purdue-pm] Meeting in one Week
bradley.d.andersen at gmail.com
Tue Mar 12 09:09:05 PDT 2013
I would really be interested in this as well, and might attend, depending
on the day of week.
In all the places I have ever worked, we always say we're going to do the
leg work before we write any code, or we're gonna do test-driven
Guess how many *.t files I have ever seen, outside of CPAN?
Nobody writes tests. And I mean nobody.
So I have very limited experience, because I only have time to do what
people will pay me to do, and they will never pay me to write tests. And
they are all losing money in the end because of it.
On Tue, Mar 12, 2013 at 11:29 AM, Dave Jacoby <jacoby at purdue.edu> wrote:
> In almost exactly one week, we'll be getting together for the next
> scheduled meeting of the Purdue Perl Mongers.
> Do we have ideas for topics?
> The one thing I have is a curiosity on unit testing. Writing tests is a
> subject like "eat right", "exercise", "back up your data" and "use revision
> control", in that I'm convinced by society that these are the right things
> to do, but in practice, I find myself at a loss on how to go how I
> currently do them to the glorious new world where I do things right.
> My issue isn't how to use the *.t syntax and testing modules. My issue is
> knowing what to test for in the first place. Once I know what to test and
> how to test, the syntax can and will be learned.
> I could pull out a module or two and we could determine what should be
> Or, we could do something else.
> Dave Jacoby
> Code Maker, Purdue Genomics Core Lab
> 391 days until the end of XP support
> Purdue-pm mailing list
> Purdue-pm at pm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Purdue-pm