Add a parameter to display migrations

[jaimebuelta]

Currently, when running the tests, the migrations are not displayed as they are applied. Instead, the first test waits until the migration is completed.

A way of showing the migrations as they are applied (just like the regular Django test suite does) will be useful.

This is related as well with issue #306, as it will be a good place to show errors in migrations.

[blueyed]

You can use -vv (or maybe just -v?!) - I typically use --no-migrations.

Do you think there should be an explicit setting for that, so that it can be used without -v?

[jaimebuelta]

Setting -v or -vv doesn't display the migrations. The migration happens after the first test is displayed, though no indication is given on what's happening.

Adding it under -v would perfectly work. Probably -vv should display extra information, just like the regular Django manage.py test command displays it with -v 2 and -v 3

[jaimebuelta]

This is the output of a run with pytest , as you can see, no indication on migrations:

============================= test session starts ==============================
platform linux2 -- Python 2.7.13, pytest-3.1.3, py-1.4.34, pluggy-0.4.0
Django settings: app.test_settings (from ini file)
rootdir: /home/rof/src/github.com/RapidRatings/dbapi2/src, inifile: codeship/pytest.ini
plugins: django-3.1.2
collected 352 items 

src/configuration/tests.py ...
src/one_app/tests.py .....................
src/app/tests/test_fixtures.py ........
src/app/tests/test_methods.py .........
...

While the migrations running manage.py tests -v 3 looks like (edited for clarity)

Creating test database for alias 'default' ('test_dbapi')...

Synchronizing apps without migrations:
  Creating tables...
    Running deferred SQL...
Running migrations:
  Applying contenttypes.0001_initial... OK (0.014s)
  Applying auth.0001_initial... OK (0.046s)
  Applying something.0001_initial... OK (0.041s)
  Applying something.0001_initial... OK (0.026s)
  Applying something.0002_logentry... OK (0.016s)
  Applying contenttypes.0002_remove_content_type_name... OK (0.034s)
  ...

Something like this would be ideal (mixing both)

============================= test session starts ==============================
platform linux2 -- Python 2.7.13, pytest-3.1.3, py-1.4.34, pluggy-0.4.0
Django settings: app.test_settings (from ini file)
rootdir: /home/rof/src/github.com/RapidRatings/dbapi2/src, inifile: codeship/pytest.ini
plugins: django-3.1.2
collected 352 items 

-- Migrations
Creating test database for alias 'default' ('test_dbapi')...

Synchronizing apps without migrations:
  Creating tables...
    Running deferred SQL...
Running migrations:
  Applying contenttypes.0001_initial... OK (0.014s)
  Applying auth.0001_initial... OK (0.046s)
  Applying something.0001_initial... OK (0.041s)
  Applying something.0001_initial... OK (0.026s)
  Applying something.0002_logentry... OK (0.016s)
  Applying contenttypes.0002_remove_content_type_name... OK (0.034s)
  ...

-- Tests
src/configuration/tests.py ...
src/one_app/tests.py .....................
src/app/tests/test_fixtures.py ........
src/app/tests/test_methods.py .........
...