  .TP
  .B \-\-keepdb
  .UNINDENT
  .sp
  
  .sp
  The \fB\-\-keepdb\fP option can be used to preserve the test database between test
  runs. This has the advantage of skipping both the create and destroy actions
  which can greatly decrease the time to run tests, especially those in a large
  test suite. If the test database does not exist, it will be created on the first
  run and then preserved for each subsequent run. Any unapplied migrations will also
  be applied to the test database before running the test suite.
  .INDENT 0.0
  .TP
  .B \-\-reverse
  .UNINDENT
  .sp
 
</s> remove .B \-\-reverse
 </s> add .B \-\-reverse, \-r </s> remove .B \-\-keepdb
 </s> add .B \-\-keepdb, \-k </s> remove The \fB\-\-failfast\fP option can be used to stop running tests and report the
failure immediately after a test fails.
 </s> add Stops running tests and reports the failure immediately after a test fails. </s> remove .B \-\-testrunner
 </s> add .B \-\-testrunner TESTRUNNER </s> remove The \fB\-\-testrunner\fP option can be used to control the test runner class that
is used to execute tests. If this value is provided, it overrides the value
provided by the \fBTEST_RUNNER\fP setting.
 </s> add Controls the test runner class that is used to execute tests. This value
overrides the value provided by the \fBTEST_RUNNER\fP setting.
Preserves the test database between test runs. This has the advantage of
skipping both the create and destroy actions which can greatly decrease the
time to run tests, especially those in a large test suite. If the test database
does not exist, it will be created on the first run and then preserved for each
subsequent run. Any unapplied migrations will also be applied to the test
database before running the test suite.
  .TP
  .B \-\-keepdb
  .UNINDENT
  .sp
Preserves the test database between test runs. This has the advantage of
skipping both the create and destroy actions which can greatly decrease the
time to run tests, especially those in a large test suite. If the test database
does not exist, it will be created on the first run and then preserved for each
subsequent run. Any unapplied migrations will also be applied to the test
database before running the test suite.
Preserves the test database between test runs. This has the advantage of
skipping both the create and destroy actions which can greatly decrease the
time to run tests, especially those in a large test suite. If the test database
does not exist, it will be created on the first run and then preserved for each
subsequent run. Any unapplied migrations will also be applied to the test
database before running the test suite.
Preserves the test database between test runs. This has the advantage of
skipping both the create and destroy actions which can greatly decrease the
time to run tests, especially those in a large test suite. If the test database
does not exist, it will be created on the first run and then preserved for each
subsequent run. Any unapplied migrations will also be applied to the test
database before running the test suite.
Preserves the test database between test runs. This has the advantage of
skipping both the create and destroy actions which can greatly decrease the
time to run tests, especially those in a large test suite. If the test database
does not exist, it will be created on the first run and then preserved for each
subsequent run. Any unapplied migrations will also be applied to the test
database before running the test suite.
Preserves the test database between test runs. This has the advantage of
skipping both the create and destroy actions which can greatly decrease the
time to run tests, especially those in a large test suite. If the test database
does not exist, it will be created on the first run and then preserved for each
subsequent run. Any unapplied migrations will also be applied to the test
database before running the test suite.
Preserves the test database between test runs. This has the advantage of
skipping both the create and destroy actions which can greatly decrease the
time to run tests, especially those in a large test suite. If the test database
does not exist, it will be created on the first run and then preserved for each
subsequent run. Any unapplied migrations will also be applied to the test
database before running the test suite.
Preserves the test database between test runs. This has the advantage of
skipping both the create and destroy actions which can greatly decrease the
time to run tests, especially those in a large test suite. If the test database
does not exist, it will be created on the first run and then preserved for each
subsequent run. Any unapplied migrations will also be applied to the test
database before running the test suite.
Preserves the test database between test runs. This has the advantage of
skipping both the create and destroy actions which can greatly decrease the
time to run tests, especially those in a large test suite. If the test database
does not exist, it will be created on the first run and then preserved for each
subsequent run. Any unapplied migrations will also be applied to the test
database before running the test suite.
  .INDENT 0.0
  .TP
  .B \-\-reverse
  .UNINDENT
  .sp
keep keep keep keep replace replace replace replace replace replace replace replace keep keep keep keep keep
 Updated man page for Django 2.0 alpha. 
docs/man/django-admin.1