- 3270e18 Revert "[autotest] Always use tko tables on master from shards." by Jakob Juelich · 10 years ago
- e2bf396 [autotest] Always use tko tables on master from shards. by Jakob Juelich · 10 years ago
- 3536b98 Fix django 1.3 DeprecationWarning for DATABASES. by Mike Truty · 13 years ago
- 74a314b Upstream Autotest merge. by Dale Curtis · 13 years ago
- 78f5b01 Update to Django 1.1.1. I want to use a new feature for my RESTful interface prototyping (direct inclusion of URL patterns in URLconfs). by showard · 15 years ago
- 9bb33ec handy-dandy function to print all SQL queries executed during a unit test, useful for debugging failing tests (you can call it from tearDown) by showard · 15 years ago
- a5288b4 Upgrade from Django 0.96 to Django 1.0.2. by showard · 15 years ago
- 844960a make the readonly connection fallback to the regular Django connection when running in the scheduer. this is really important, because otherwise the readonly connection is not autocommit and bad, bad things could happen, though i'm not sure exactly what existing problems there might have been. we used to do this only for testing, but since we do it in another context here, i renamed the method to be more generic and appropriate. by showard · 15 years ago
- f8b1904 Add the ability for users to add test attributes. Non-user-created attributes (added by the parser) are still immutable. by showard · 15 years ago
- 364fe86 Refactor the basic environment setup code out of django_test_utils.py into setup_django_environment.py, and rename django_test_utils.py to setup_test_environment.py. Also changed the environment setup code to run at import time. This makes it easy for scripts, both test and non-test, to use Django models without running through manage.py. The idea is that scripts will import setup_django_environment before importing Django code (somewhat akin to common.py), and test code will subsequently import setup_test_environment. by showard · 16 years ago