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

6 vistas
Ir al primer mensaje no leído

Django

no leída,
3 abr 2016, 5:58:11 a.m.3/4/2016
para django-...@googlegroups.com
#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: <https://code.djangoproject.com/ticket/26448>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

no leída,
3 abr 2016, 7:00:30 a.m.3/4/2016
para django-...@googlegroups.com
#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: <https://code.djangoproject.com/ticket/26448#comment:1>

Django

no leída,
4 abr 2016, 8:34:16 a.m.4/4/2016
para django-...@googlegroups.com
#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: <https://code.djangoproject.com/ticket/26448#comment:2>

Django

no leída,
5 abr 2016, 4:03:16 p.m.5/4/2016
para django-...@googlegroups.com
#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: <https://code.djangoproject.com/ticket/26448#comment:3>

Django

no leída,
5 abr 2016, 8:06:31 p.m.5/4/2016
para django-...@googlegroups.com
#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: <https://code.djangoproject.com/ticket/26448#comment:4>

Django

no leída,
5 abr 2016, 9:44:29 p.m.5/4/2016
para django-...@googlegroups.com
#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 <timograham@…>):

* 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: <https://code.djangoproject.com/ticket/26448#comment:5>

Responder a todos
Responder al autor
Reenviar
0 mensajes nuevos