Menu
I have a fairly complex Django project which makes it hard/impossible to use fixtures for loading data.
What I would like to do is to load a database dump from the production database server after all tables has bene created by the testrunner and before the actual tests start running.
I've tried various "magic" in MyTestCase.setUp(), but with no luck.
Any suggestions would be most welcome. Thanks.
971
Open /catalog/tests/test_models.py.from django. test import TestCase # Create your tests here. Often you will add a test class for each model/view/form you want to test, with individual methods for testing specific functionality.
django-nose provides all the goodness of nose in your Django tests, like: Testing just your apps by default, not all the standard ones that happen to be in INSTALLED_APPS. Running the tests in one or more specific modules (or apps, or classes, or folders, or just running a specific test)
The preferred way to write tests in Django is using the unittest module built-in to the Python standard library. This is covered in detail in the Writing and running tests document. You can also use any other Python test framework; Django provides an API and tools for that kind of integration.
Writing tests Django's unit tests use a Python standard library module: unittest . This module defines tests using a class-based approach. When you run your tests, the default behavior of the test utility is to find all the test cases (that is, subclasses of unittest.
Django supports loading SQL files when doing syncdb, reset, or starting a test runner -- this does exactly what you describe:
http://docs.djangoproject.com/en/dev/howto/initial-data/#providing-initial-sql-data
You need to create an "sql" directory in your app directory, and then put a file named "mymodel.sql" in that directory (where "MyModel" is the corresponding model name).
myproject/
|--myapp/
|--sql/
|--mymodel.sql
You can create this SQL with dump tools for your database.
After dumping, you'll need to edit the file to remove everything but the appropriate INSERT statements, or other complicated stuff. In particular, you must remove transaction handling, index creating, and table creating SQL to avoid errors when loading duplicate create statements.
I use this method for loading really, really big fixtures -- it takes far too long to process the json, but a straight sql import is pretty snappy.
Do be aware that this method will load the sql for any invocation of synchdb, reset, etc. in addition to loading data for the test runner -- so you won't be able to have different data for different test cases, and you'd have to remove files before a reset if you didn't want them loading back onto your production server.
[1] http://www.sqlite.org/sqlite.html
[2] http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html
[3] http://www.postgresql.org/docs/8.1/static/backup.html#BACKUP-DUMP
100
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
