-
Notifications
You must be signed in to change notification settings - Fork 154
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.
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
Normalizing test namespaces (and folder structure)? #529
Comments
The Usually, the test namespace structure should match that of the tested production classes. In this cases, I'm for making an exception and put the
Definitely |
Moving to 4.0 (as this is the milestone where we will remove the original Emogrifier class). |
I just found there’s a typo in the
Simply correcting this to For consistency with how their namespace (and location) corresponds to the class under test, it looks like the namespace for
But based on this comment, it's the other test classes that need changing, at least as far as the namespace name is concerned… |
The namespace prefix should be |
Currently we have a couple of different namespace structures:
emogrifier/tests/Unit/EmogrifierTest.php
:->
namespace Pelago\Tests\Unit;
emogrifier/tests/Unit/CssInlinerTest.php
:->
namespace Pelago\Emogrifer\Tests\Unit;
emogrifier/tests/Unit/Emogrifier/HtmlProcessor/AbstractHtmlProcessorTest.php
:->
namespace Pelago\Tests\Unit\Emogrifier\HtmlProcessor;
In
emogrifier/tests/Unit/Emogrifier/HtmlProcessor/HtmlNormalizerTest.php
:->
namespace Pelago\Tests\Unit\Emogrifier\HtmlProcessor;
I think we should decide between
Pelago\Emogrifier\Tests\Unit
andPelago\Tests\Emogrifier\Unit
as the prefix across all tests. Which one would you prefer?Also, to keep sync between the
src
andtests
folders,CssInlinerTest.php
should be moved into theEmogrifier
folder.What do you think?
The text was updated successfully, but these errors were encountered: