Home en de fr et

#2522 (How to test database migrations)

State: Started (last update 2019-04-25 17:01:12.150465+00:00)
Created 2018-09-02 03:12:16+00:00 by Luc Saffre
Site: core.deploy

The demo projects for which there is a registered production site (team, lydia, adg, ...) should have a new type of test where we keep a database snapshot for each released version and test whether that snapshot imports correctly to every new version.

    I opened #2587 for this question. (6 months, 1 week ago by Luc Saffre)
    Please explain why do you set loading_from_dump to False after the migration is done. (6 months, 1 week ago by Luc Saffre)
    Seems that argparse in restore.py sees the arguments which were given to manage.py test. (6 months, 3 weeks ago by Luc Saffre)
    The following is still failing: go lydia and then python manage.py test --noinput --failfastIt says usage: --noinput [-h] [--noinput]--noinput: error: unrecognized arguments: --failfast (6 months, 3 weeks ago by Luc Saffre)
    No need for a list of stable projects. Just a dumps subdir in the tests subdir of the stable demo projects. (6 months, 3 weeks ago by Luc Saffre)
    The snapshots would be in a subdir named "dumps". For every new registered production site we would make sure that a demo project exists and that it is marked "stable" ("supports stable hosting"). There should be a command to get a list of "stable demo projects".  (7 months, 1 week ago by Luc Saffre)