I tried doing this in ``CELERYBEAT_SCHEDULE`` because we don't have to explicitly populate the rows in ``djcelery_intervalschedule``. Celery appears to do this magically and we hard code foreign key ids in the fixture like so, ``interval": 2``, which is kind-of horrifying because I think we're relying on the default way in which ``djcelery_intervalschedule`` is populated to get the foreign key references correct. If you look at the default contents of ``djcelery_crontabschedule``, they are empty. Oddly enough this strategy works locally for me without any errors, the crontabschedule table contains the entries from  ``CELERYBEAT_SCHEDULE`` and all of the tests pass. I will try adding fixtures for both ``djcelery_intervalschedule`` and `djcelery_crontabschedule`` and remove ``CELERYBEAT_SCHEDULE`` from ``settings.py`` so we have better control of the hard coded foreign key references. This will require that foreign key checks are disabled when the fixtures are created otherwise we will have order dependency issues with the foreign keys... fingers crossed