p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Refs #34043 -- Clarified how to test UI changes.

This commit is contained in:
sarahboyce 2023-06-27 09:00:35 +02:00 committed by Mariusz Felisiak
parent 54b23b1835
commit e083f3082c
2 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/internals/contributing/writing-code/unit-tests.txt
View File

@ -247,6 +247,8 @@ Note that the ``--reverse`` option doesn't impact on ``--start-at`` or
``--start-after`` options. Moreover these options cannot be used with test
labels.
.. _running-selenium-tests:
Running the Selenium tests
--------------------------

9
docs/intro/contributing.txt
View File

@ -188,7 +188,11 @@ have to create a new virtual environment, :ref:`install the previously cloned
local copy of Django in editable mode <intro-contributing-install-local-copy>`,
and create a new Django project outside of your local copy of Django. You will
immediately see any changes you make to Django in your new project, which is
of great help when writing your first patch.
of great help when writing your first patch, especially if testing any changes
to the UI.
You can follow the :doc:`tutorial</intro/tutorial01>` for help in creating a
Django project.
Running Django's test suite for the first time
==============================================
@ -259,7 +263,8 @@ __ https://djangoci.com
For this tutorial and the ticket we're working on, testing against SQLite
is sufficient, however, it's possible (and sometimes necessary) to
:ref:`run the tests using a different database
<running-unit-tests-settings>`.
<running-unit-tests-settings>`. When making UI changes, you will need to
:ref:`run the Selenium tests <running-selenium-tests>`.
Working on a feature
====================