10000 Added note about using the Validator TypeTestCase in form unit testing by pierredup · Pull Request #7587 · symfony/symfony-docs · GitHub
[go: up one dir, main page]
Skip to content

Added note about using the Validator TypeTestCase in form unit testing #7587

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 9 commits into from
Jan 10, 2018
Merged

Added note about using the Validator TypeTestCase in form unit testing #7587

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
3e6dc19
Add docs about the validator TypeTestCase class
pierredup Mar 6, 2017
d4979eb
Fix typos
pierredup Mar 6, 2017
d17821a
Fix heading underlining
pierredup Mar 6, 2017
070b2c0
Renamed TestedTypeTests to TestedTypeTest
pierredup Mar 7, 2017
cf0f9e6
Update fomr testing sentence
pierredup Mar 7, 2017
6fda2df
Removed extra class
pierredup Mar 7, 2017
f0887ae
Remove section about forms using validation
pierredup Jun 24, 2017
ff1bd8e
Reverted some changes
javiereguiluz Jan 10, 2018
c495b92
Readded a blank line
javiereguiluz Jan 10, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
8000
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Reverted some changes
  • Loading branch information
@javiereguiluz
javiereguiluz authored Jan 10, 2018
commit ff1bd8ee7384436c815c8458d7cd27a189afda64
12 changes: 10 additions & 2 deletions form/unit_testing.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,7 +161,8 @@ Adding Custom Extensions
------------------------

It often happens that you use some options that are added by
:doc:`form extensions </form/create_form_type_extension>`.
:doc:`form extensions </form/create_form_type_extension>`. One of the
cases may be the ``ValidatorExtension`` with its ``invalid_message`` option.
The ``TypeTestCase`` only loads the core form extension, which means an
:class:`Symfony\\Component\\OptionsResolver\\Exception\\InvalidOptionsException`
will be raised if you try to test a class that depends on other extensions.
Expand All @@ -172,23 +173,30 @@ allows you to return a list of extensions to register::
namespace AppBundle\Tests\Form\Type;

use AppBundle\Form\Type\TestedType;
use Symfony\Component\Form\Extension\Validator\ValidatorExtension;
use Symfony\Component\Form\Form;
use Symfony\Component\Form\Forms;
use Symfony\Component\Form\FormBuilder;
use Symfony\Component\Form\Test\TypeTestCase;
use Symfony\Component\Validator\ConstraintViolationList;
use Symfony\Component\Validator\Mapping\ClassMetadata;
use Symfony\Component\Validator\Validator\ValidatorInterface;

class TestedTypeTest extends TypeTestCase
{
protected function getExtensions()
{
$validator = $this->createMock(ValidatorInterface::class);
// use getMock() on PHPUnit 5.3 or below
// $validator = $this->getMock(ValidatorInterface::class);
$validator
->method('validate')
->will($this->returnValue(new ConstraintViolationList()));
$validator
->method('getMetadataFor')
->will($this->returnValue(new ClassMetadata(Form::class)));
return array(
new MyFormExtension(),
new ValidatorExtension($validator),
);
}

Expand Down
0