mirror of
https://github.com/django/django.git
synced 2025-10-24 06:06:09 +00:00
Moved manual testing instructions from intro to submitting patches docs.
The section on manual testing, including how to use a local checkout of Django, is moved from the contribution intro to the submitting patches docs. This makes it easier for reviewers and authors to follow best practices.
This commit is contained in:
@@ -317,6 +317,25 @@ utilities, such as a ``@deprecate_posargs`` decorator to assist with converting
|
||||
positional-or-keyword arguments to keyword-only. See the inline documentation
|
||||
in the module source.
|
||||
|
||||
Testing with a Django project
|
||||
=============================
|
||||
|
||||
It's important to test local changes using a Django project. This allows
|
||||
ensuring that the changes behave as expected in a real environment, especially
|
||||
for user-facing features such as templates, forms, or the admin.
|
||||
|
||||
To do this:
|
||||
|
||||
#. Create a virtual environment and :ref:`install the cloned copy of Django in
|
||||
editable mode <intro-contributing-install-local-copy>`.
|
||||
|
||||
#. Set up a Django project outside the source tree (you can use the :doc:`first
|
||||
part of the tutorial </intro/tutorial01>` for guidance).
|
||||
|
||||
With this setup, any changes made to the Django checkout will take effect
|
||||
immediately in the test project, allowing manual testing of contributions
|
||||
against a new or existing app.
|
||||
|
||||
JavaScript contributions
|
||||
========================
|
||||
|
||||
|
||||
Reference in New Issue
Block a user