8000 Reword · githubfromgui/symfony-docs@b310e18 · GitHub
[go: up one dir, main page]

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit b310e18

Browse files
committed
Reword
1 parent fa19b45 commit b310e18

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

testing.rst

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -57,9 +57,10 @@ Symfony application.
5757
Unit Tests
5858
----------
5959

60-
A unit test is a test against a single behavior, also called a *unit*. If you
61-
want to test the overall way of your application, see the section about
62-
:ref:`Functional Tests <functional-tests>`.
60+
A `unit test`_ ensures that individual units of source code (e.g. a single class
61+
or some specific method in some class) meet their design and behave as intended.
62+
If you want to test an entire feature of your application (e.g. registering as a
63+
user or generating an invoice), see the section about :ref:`Functional Tests <functional-tests>`.
6364

6465
Writing Symfony unit tests is no different from writing standard PHPUnit
6566
unit tests. Suppose, for example, that you have an *incredibly* simple class
@@ -1135,5 +1136,6 @@ Learn more
11351136
.. _`PHPUnit`: https://phpunit.de/
11361137
.. _`documentation`: https://phpunit.readthedocs.io/
11371138
.. _`PHPUnit Bridge component`: https://symfony.com/components/PHPUnit%20Bridge
1139+
.. _`unit test`: https://en.wikipedia.org/wiki/Unit_testing
11381140
.. _`$_SERVER`: https://www.php.net/manual/en/reserved.variables.server.php
11391141
.. _`data providers`: https://phpunit.de/manual/current/en/writing-tests-for-phpunit.html#writing-tests-for-phpunit.data-providers

0 commit comments

Comments
 (0)
0