Move the tests directly related to the Tokenizer\PHP class into a PHP subdirectory.
Move the tests directly related to the Tokenizer\Tokenizer class into a Tokenizer subdirectory.
As there are five (soon three) Tokenizer classes, having the tests for each class in their own subdirectory makes it more straight forward to see what code is covered by tests.
Tests/Tokenizer/ArrayKeywordTest: split the test class
Tests/Tokenizer/DefaultKeywordTest: split the test class
Tests/Tokenizer/DNFTypesTest: split the test class
Tests/Tokenizer/EnumCaseTest: split the test class
... into two test classes, one targetting the Tokenizer\PHP class, one targetting the Tokenizer\Tokenizer class.
While this does mean there is now some duplication between these test classes, I don't think that's problematic.
It also allows for these tests to diverge based on the specific test needs for each of the classes under test.
Description
Tests/Tokenizer: move tests
Move the tests directly related to the
Tokenizer\PHP
class into aPHP
subdirectory. Move the tests directly related to theTokenizer\Tokenizer
class into aTokenizer
subdirectory.As there are five (soon three) Tokenizer classes, having the tests for each class in their own subdirectory makes it more straight forward to see what code is covered by tests.
Tests/Tokenizer/ArrayKeywordTest: split the test class
Tests/Tokenizer/DefaultKeywordTest: split the test class
Tests/Tokenizer/DNFTypesTest: split the test class
Tests/Tokenizer/EnumCaseTest: split the test class
... into two test classes, one targetting the
Tokenizer\PHP
class, one targetting theTokenizer\Tokenizer
class.While this does mean there is now some duplication between these test classes, I don't think that's problematic.
It also allows for these tests to diverge based on the specific test needs for each of the classes under test.
Suggested changelog entry
N/A