... deprecated features in the 1.1 branch, see the Django 1.1 リリースノート . Backwards-incompatible changes in 1.1.2 ¶ Test runner exit status code ¶ The exit status code of the test runners ( tests/runtests.py and python manage.py test ) no longer repr ... failed tests, since a failure of 256 or more tests resulted in a wrong exit status code. The exit status code for the test runner is now 0 for success (no failing tests) and 1 for any number of test failures. If needed, the number of test failures can ... be found at the end of the test runner's output. Cookie encoding ¶ To fix bugs with cookies in Internet Explorer, Safari, and possibly other browsers, our encodi ... ... deprecated features in the 1.1 branch, see the Django 1.1 リリースノート . Backwards-incompatible changes in 1.1.2 ¶ Test runner exit status code ¶ The exit status code of the test runners ( tests/runtests.py and python manage.py test ) no longer repr ... failed tests, since a failure of 256 or more tests resulted in a wrong exit status code. The exit status code for the test runner is now 0 for success (no failing tests) and 1 for any number of test failures. If needed, the number of test failures can ... be found at the end of the test runner's output. Cookie encoding ¶ To fix bugs with cookies in Internet Explorer, Safari, and possibly other browsers, our encodi ... ... ault. See 持続的 (persistent) な接続 for details. Discovery of tests in any test module ¶ Django 1.6 ships with a new test runner that allows more flexibility in the location of tests. The previous runner ( django.test.simple.DjangoTestSuiteRunner ) fo ... und tests only in the models.py and tests.py modules of a Python package in INSTALLED_APPS . The new runner ( django.test.runner.DiscoverRunner ) uses the test discovery features built into unittest2 (the version of unittest in th ... was only an option for PostgreSQL, and it was disabled by default. This option is now ignored and can be removed. New test runner ¶ In order to maintain greater consistency with Python's unittest module, the new test runner ( django.test.runner.Discove ... ... ault. See 持続的 (persistent) な接続 for details. Discovery of tests in any test module ¶ Django 1.6 ships with a new test runner that allows more flexibility in the location of tests. The previous runner ( django.test.simple.DjangoTestSuiteRunner ) fo ... und tests only in the models.py and tests.py modules of a Python package in INSTALLED_APPS . The new runner ( django.test.runner.DiscoverRunner ) uses the test discovery features built into unittest2 (the version of unittest in th ... was only an option for PostgreSQL, and it was disabled by default. This option is now ignored and can be removed. New test runner ¶ In order to maintain greater consistency with Python's unittest module, the new test runner ( django.test.runner.Discove ... ... !/usr/bin/env python import os import sys import django from django.conf import settings from django.test.utils import get_runner if __name__ == "__main__" : os . environ [ "DJANGO_SETTINGS_MODULE" ] = "tests.test_settings" django . setup () TestRunner ... = get_runner ( settings ) test_runner = TestRunner () failures = test_runner . run_tests ([ "tests" ]) sys . exit ( bool ( failures )) ... に構築されたテストを通常のDjangoテストのように呼び出す方法に対応しています。 ./manage.py test を実行するとき、Django は TEST_RUNNER 設定を見て、何をするかを決定します。デフォルトでは、 TEST_RUNNER は 'django.test.runner.DiscoverRunner' を指します。このク ... ... !/usr/bin/env python import os import sys import django from django.conf import settings from django.test.utils import get_runner if __name__ == "__main__" : os . environ [ "DJANGO_SETTINGS_MODULE" ] = "tests.test_settings" django . setup () TestRunner ... = get_runner ( settings ) test_runner = TestRunner () failures = test_runner . run_tests ([ "tests" ]) sys . exit ( bool ( failures )) ... に構築されたテストを通常のDjangoテストのように呼び出す方法に対応しています。 ./manage.py test を実行するとき、Django は TEST_RUNNER 設定を見て、何をするかを決定します。デフォルトでは、 TEST_RUNNER は 'django.test.runner.DiscoverRunner' を指します。このク ... ... report documentation on controlling the creation order of test databases for details. GeoDjango ¶ The function-based TEST_RUNNER previously used to execute the GeoDjango test suite, django.contrib.gis.tests.run_gis_tests , was finally deprecated in fa ... vor of a class-based test runner, django.contrib.gis.tests.GeoDjangoTestSuiteRunner , added in this release. In addition, the GeoDjango test suite is now i ... ... py script used to run Django's own test suite now support a --failfast option. When specified, this option causes the test runner to exit after encountering a failure instead of continuing with the test run. In addition, the handling of Ctrl-C during a ... ting over __dict__ to obtain a list of fields, you must now be prepared to handle or filter out the _state attribute. Test runner exit status code ¶ The exit status code of the test runners ( tests/runtests.py and python manage.py test ) no longer repr ... iled tests, because a failure of 256 or more tests resulted in a wrong exit status code. The exit status code for the test runner is now 0 for success (no failing tests) and 1 for any number of test failures. If needed, the number of test failures can ... ... report documentation on controlling the creation order of test databases for details. GeoDjango ¶ The function-based TEST_RUNNER previously used to execute the GeoDjango test suite, django.contrib.gis.tests.run_gis_tests , was finally deprecated in fa ... vor of a class-based test runner, django.contrib.gis.tests.GeoDjangoTestSuiteRunner , added in this release. In addition, the GeoDjango test suite is now i ... ... py script used to run Django's own test suite now support a --failfast option. When specified, this option causes the test runner to exit after encountering a failure instead of continuing with the test run. In addition, the handling of Ctrl-C during a ... ting over __dict__ to obtain a list of fields, you must now be prepared to handle or filter out the _state attribute. Test runner exit status code ¶ The exit status code of the test runners ( tests/runtests.py and python manage.py test ) no longer repr ... iled tests, because a failure of 256 or more tests resulted in a wrong exit status code. The exit status code for the test runner is now 0 for success (no failing tests) and 1 for any number of test failures. If needed, the number of test failures can ... 2026年10月08日