Skip to content

Added tip to require browser-kit in WebTestCase. #8861

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Dec 22, 2017
Merged

Added tip to require browser-kit in WebTestCase. #8861

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b266c1b
Added tip to require browser-kit in WebTestCase.
Rubinum Dec 9, 2017
dcf2265
Changed spelling
Rubinum Dec 9, 2017
9ae575b
Moved tip block to headline. Changed tip description.
Dec 13, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions testing.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -129,6 +129,12 @@ tests as far as PHPUnit is concerned, but they have a very specific workflow:
Your First Functional Test
~~~~~~~~~~~~~~~~~~~~~~~~~~

First, install the BrowserKit component in your project:

.. code-block:: terminal

$ composer require --dev browser-kit

Functional tests are simple PHP files that typically live in the ``tests/Controller``
directory for your bundle. If you want to test the pages handled by your
``PostController`` class, start by creating a new ``PostControllerTest.php``
Expand Down