@@ -454,10 +454,7 @@ If you have installed the bridge through Composer, you can run it by calling e.g
454
454
Code coverage listener
455
455
----------------------
456
456
457
- Use case
458
- ~~~~~~~~
459
-
460
- By default the code coverage is computed with the following rule: if a line of
457
+ By default, the code coverage is computed with the following rule: if a line of
461
458
code is executed, then it is marked as covered. And the test which executes a
462
459
line of code is therefore marked as "covering the line of code". This can be
463
460
misleading.
@@ -503,7 +500,7 @@ Consider the following example::
503
500
504
501
The ``FooTest::test `` method executes every single line of code of both ``Foo ``
505
502
and ``Bar `` classes, but ``Bar `` is not truly tested. The ``CoverageListener ``
506
- aims to fix this behavior by adding the appropriate `` @covers `` annotation on
503
+ aims to fix this behavior by adding the appropriate `@covers `_ annotation on
507
504
each test class.
508
505
509
506
If a test class already defines the ``@covers `` annotation, this listener does
@@ -530,7 +527,7 @@ Add the following configuration to the ``phpunit.xml.dist`` file
530
527
</listeners >
531
528
</phpunit >
532
529
533
- If the logic followed to find the related code is too simple or doesn't work for
530
+ If the logic used to find the related code is too simple or doesn't work for
534
531
your application, you can use your own SUT (System Under Test) solver:
535
532
536
533
.. code-block :: xml
@@ -570,3 +567,4 @@ not find the SUT:
570
567
.. _`@-silenced` : http://php.net/manual/en/language.operators.errorcontrol.php
571
568
.. _`Travis CI` : https://travis-ci.org/
572
569
.. _`test listener` : https://phpunit.de/manual/current/en/appendixes.configuration.html#appendixes.configuration.test-listeners
570
+ .. _`@covers` : https://phpunit.de/manual/current/en/appendixes.annotations.html#appendixes.annotations.covers
0 commit comments