[Pydns-developer] unit tests.

[Anthony B. <an...@in...>]

[starting a different thread for each major topic - I find it's
easier this way to keep track of stuff]

We talked before about unit tests, and how it's difficult because
the test data changes around a bit (as servers move &c.) 

A couple of ways we could handle this:

1. Make the test suite call (and parse!) "dig" or similar to get 
   a set of current test data. Only works on unix. Oh well.

2. Make a different script that generates the test data and gets 
   run automatically from cron and makes the test data available on 
   the pydns website. Better, but probably more work. Still has a 
   window of opportunity for it to be broken.

3. Just ignore the problem and leave it as something that might
   change, sometimes, and that the developers and anyone who wants 
   to run the suite will just have to Just Deal With.

4. Don't bother with unit tests (booo!)

Anthony