You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yesterday, a new cookbook article was merged about Unit Testing your forms1.
There was a discussion about the place of the TypeTestCase class in the current workflow. Now it is documented, I think we should move these classes to their own Symfony\Component\Form\Test\Type namespace, instead of the current Symfony\Component\Form\Tests\Extension\Core\Type\.
The text was updated successfully, but these errors were encountered:
This PR was merged into the master branch.
Discussion
----------
[Form] Moved TypeTestCase to the Test namespace
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | yes
| BC breaks? | no
| Deprecations? | yes
| Tests pass? | yes
| Fixed tickets | #7175
| License | MIT
| Doc PR | symfony/symfony-docs#2500
Todo:
- [x] Make a Doc PR
- [x] Update the changelog and UPGRADE-3.md files
As discussed in #7175, since this class is documented as a practise to test your form types, it's good to move it to the `Test` namespace.
I am not sure about the deprecation, I thought things deprecated in 2.3 are removed in 3.0. Also, I think we shouldn't trigger a E_USER_DEPRECATED message.
Please correct me if I'm wrong, it's my first PR for the core code.
Commits
-------
8da6129 Moved FormIntegrationTestCase and FormPerformanceTestCase to the Test namespace
e46f841 Moved TypeTestCase to it's own namespace
Yesterday, a new cookbook article was merged about Unit Testing your forms1.
There was a discussion about the place of the TypeTestCase class in the current workflow. Now it is documented, I think we should move these classes to their own
Symfony\Component\Form\Test\Type
namespace, instead of the currentSymfony\Component\Form\Tests\Extension\Core\Type\
.The text was updated successfully, but these errors were encountered: