[TIP] Test Driven Development
raphael.marvie at lifl.fr
Mon Mar 5 00:33:11 PST 2007
Except for some prototypes, I tend to use TDD on most of my developments
for more than a year now. I mainly use unittest for driving both unit
tests and "functional" ones (for web apps I use a small lib I developed
for testing / querying the rendered html page, I did not know about
beautiful soup). I also use test coverage, but I am more interested when
coverage is not 100% (meaning I am missing something) than when coverage
is 100% not meaning that tests are ok.
We are starting a project with chemists on air quality modeling to do
forecasts. We have to integrate C++, Fortran and Python components and
to provide a web portal for offering computations to government
agencies. We are going to use TDD but we do not know yet how we will
implement components and integration testing (the idea is to provide
abstraction of C++ and Fortran elements as Python objects).
I will stay in touch for providing feedback and also to discuss our
difficulties with the members of this list. :-)
my 2 cents,
Michael Foord wrote:
> Hello all,
> I'm very pleased to see this mailing list, thanks to Titus for setting
> it up.
> I'm interested in how many people on this list are doing test driven
> development ?
> At Resolver we practise TDD, and have both unit tests and functional tests.
> All the best,
> Michael Foord
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
Raphael Marvie, PhD http://www.lifl.fr/~marvie/
Maître de Conférences / Associate Professor @ LIFL -- IRCICA
Directeur du Master Informatique Professionnel spécialité IAGL
Head of Master's in Software Engineering +33 3 28 77 85 83
More information about the testing-in-python