Changes between Version 112 and Version 113 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
07/23/07 07:17:10 (8 years ago)
Author:
russellm
Comment:

Added note on changes to run_test.

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v112 v113  
    3030 * [5654] July 12, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Changed__init__parametersinsyndicationframeworksFeedclass Changed __init__() parameters in syndication framework's Feed class]
    3131 * [5708] July 15, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#POfilesmustbeUTF-8encoded PO files must be UTF-8 encoded]
     32 * [5752] July 23, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Addedinteractiveargumenttorun_tests Added `interactive` argument to `run_tests`]
    3233
    3334== Database constraint names changed ==
     
    250251
    251252Note that existing code and message catalogs will not break even if you update your code to [5708] or later. This change only takes effect the next time you run make-messages.py.
     253
     254== Added `interactive` argument to `run_tests` ==
     255
     256In [5752] the parameter ``interactive`` was added to the run_tests method. This parameter allows tests to be added to automated build scripts where interactive questions (such as being asked if it is ok to delete an existing test database) cannot be asked.
     257
     258If you are using the default Django test runner, no change is required.
     259
     260However, if you have defined a custom test runner, you must be able to accept (and handle appropriately) the `interactive` argument to the test runner. For most test runners, the only change required will be to change the call to `create_test_db` to use the keyword argument `autoclobber=not interactive`.
Back to Top