django-sane-testing (0.4.0) unstable; urgency=low

  * Django development server is multithreaded now
  * You can use CherryPy webserver instead of Django one

 -- Lukas Linhart <almad@cnt-ella-dev.dev.chservices.cz>  Mon, 26 Jan 2009 09:50:36 +0100

django-sane-testing (0.3.1) unstable; urgency=low

  * Fixed bad non-method-cases handling 

 -- Lukas Linhart <almad@cnt-ella-dev.dev.chservices.cz>  Thu, 22 Jan 2009 15:22:58 +0100

django-sane-testing (0.3.0) unstable; urgency=low

  * Django's client available for !HttpTestCase
  * Proper handling of ./manage.py test
  * Tests skip themselves if they rely on plugin that is not loaded
  * No Database care when running true unit tests whatsoever
  * ...and few fixes
 

 -- Lukas Linhart <almad@cnt-ella-dev.dev.chservices.cz>  Thu, 22 Jan 2009 13:53:11 +0100

django-sane-testing (0.2.0) unstable; urgency=low

  * Support for Selenium

 -- Lukas Linhart <almad@cnt-ella-dev.dev.chservices.cz>  Mon, 19 Jan 2009 18:22:10 +0100

django-sane-testing (0.1.0-2) unstable; urgency=low

  * Initial version for 0.1.0

 -- Lukas Linhart <bugs@almad.net>  Tue, 13 Jan 2009 11:00:49 +0100

django-sane-testing (0.1.0-1) unstable; urgency=low

  * Initial release (Closes: #nnnn)  <nnnn is the bug number of your ITP>

 -- Lukas Linhart <bugs@almad.net>  Mon, 12 Jan 2009 15:45:19 +0100

