Not all tests provided by Django are run at the build time

[Krzysztof Klimonda]

We are missing quite a few of them actually:
 * There are three tests disabled explicitly by us because they require
an internet connection and they can't be ran inside buildd session:
test_urlfield_39, test_urlfield_40 and test_correct_url_value_passes.
 They all require internet connection to access external websites in
order to check if both URLField validation/cleanup and cleanup at the
Model level are working as expected.
 * Some tests require additional packages to be installed at the build
time in order to run:
   - memcached
   - python-yaml
   - python-textile
   - python-markdown
 * Every database backend should be tested. There are three we can test:
   - postgresql_psycopg2
   - mysql
   - sqlite3
   other two are oracle and postgresql (depending on the old psycopg
package)

What has to be done:
 The easiest part is to add additional build-time dependencies - it's
not going to take much time and will give us an instant coverage boost.
We could do it even just after Natty is open for uploads. It's basically
a low-hanging fruit.
 The second thing to do would be to enable testing of all three database
backends. In order to do that we need a working MySQL and PostgreSQL
installations, the build time increase isn't going to be that big as
only tests that are related to ORM and databases have to be run more
than once.
 Both first and second paragraph to be discussed with Debian Developers.
 The hardest part is going to be making all tests pass without the
internet connection - that would require a local HTTP server, either a
configured DNS server or entries in /etc/hosts and probably access to
port 80 to simulate a real website. This one has to be discussed with
all parties - Debian, Ubuntu and Django developers.

 affects ubuntu/python-django
 severity low
 assignee kklimonda
 status inprogress

--
Sent from Ubuntu