Re: [Django] #26448: Improve docs for running tests using a different database

[Django]

#26448: Improve docs for running tests using a different database
--+
 Reporter:  aschn |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"361cb7a857f1ca69754c0e3a0038097d09508f2c" 361cb7a]:
 {{{
 #!CommitTicketReference repository=""
 revision="361cb7a857f1ca69754c0e3a0038097d09508f2c"
 Fixed #26448 -- Added details for running tests with a different database
 backend.
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.90020e368bf3abba5ced56fcd9dbbd10%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26448: Improve docs for running tests using a different database

[Django]

#26448: Improve docs for running tests using a different database
--+
 Reporter:  aschn |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * has_patch:  0 => 1


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.8efc54bfdd9fe4581d69e1f6f7e2ad0a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26448: Improve docs for running tests using a different database

[Django]

#26448: Improve docs for running tests using a different database
--+
 Reporter:  aschn |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by krisys):

 Greetings,

 aschn and timgraham, I just updated the documentation to reflect the
 suggestions and I have created a pull request for the same -
 https://github.com/django/django/pull/6418

 Thank you.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.d8a0ccf9b17a48a97030b9fb4f2cc674%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26448: Improve docs for running tests using a different database

[Django]

#26448: Improve docs for running tests using a different database
--+
 Reporter:  aschn |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.68384663c239423de1c5b3cc8b8f1b96%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26448: Improve docs for running tests using a different database

[Django]

#26448: Improve docs for running tests using a different database
-+-
 Reporter:  aschn|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aschn):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Old description:

> For new contributors working on `contrib.postgres`, it is confusing when
> the tests in `test_postgres` are skipped by default. Some possible
> improvements include:
>
> In the "skipped tests" paragraph of
> https://docs.djangoproject.com/en/1.9/intro/contributing/#running-
> django-s-test-suite-for-the-first-time, mention that another reason that
> tests might get skipped is if the tests are specific to a non-sqlite
> database. Add a link to
> https://docs.djangoproject.com/en/1.9/internals/contributing/writing-code
> /unit-tests/#using-another-settings-module to help people use a different
> settings module.
>
> In https://docs.djangoproject.com/en/1.9/internals/contributing/writing-
> code/unit-tests/#using-another-settings-module, clarify that the default
> settings module is located at `django/tests/test_sqlite.py`.

New description:

 For new contributors working on `contrib.postgres`, it is confusing when
 the tests in `postgres_tests` are skipped by default. Some possible
 improvements include:

 In the "skipped tests" paragraph of
 https://docs.djangoproject.com/en/1.9/intro/contributing/#running-django-s
 -test-suite-for-the-first-time, mention that another reason that tests
 might get skipped is if the tests are specific to a non-sqlite database.
 Add a link to https://docs.djangoproject.com/en/1.9/internals/contributing
 /writing-code/unit-tests/#using-another-settings-module to help people use
 a different settings module.

 In https://docs.djangoproject.com/en/1.9/internals/contributing/writing-
 code/unit-tests/#using-another-settings-module, clarify that the default
 settings module is located at `django/tests/test_sqlite.py`.

--

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.8c544a1e465f1a9558feb6536dfdfb17%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26448: Improve docs for running tests using a different database

[Django]

#26448: Improve docs for running tests using a different database
--+
 Reporter:  aschn |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.9
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 For new contributors working on `contrib.postgres`, it is confusing when
 the tests in `test_postgres` are skipped by default. Some possible
 improvements include:

 In the "skipped tests" paragraph of
 https://docs.djangoproject.com/en/1.9/intro/contributing/#running-django-s
 -test-suite-for-the-first-time, mention that another reason that tests
 might get skipped is if the tests are specific to a non-sqlite database.
 Add a link to https://docs.djangoproject.com/en/1.9/internals/contributing
 /writing-code/unit-tests/#using-another-settings-module to help people use
 a different settings module.

 In https://docs.djangoproject.com/en/1.9/internals/contributing/writing-
 code/unit-tests/#using-another-settings-module, clarify that the default
 settings module is located at `django/tests/test_sqlite.py`.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/048.8036e4599651ccd146d475aec5407bdd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.