DB/RestrictedClasses: remove redundant call to parent::setUpPrerequisites()
#2578
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Calling
AbstractSniffUnitTest::setUpPrerequisites()
manually insideRestrictedClassesUnitTest::enhanceGroups()
is not necessary, as this method already executes via its@before
tag and results in the method running twice.Originally,
RestrictedClassesUnitTest::enhanceGroups()
was namedRestrictedClassesUnitTest::setUp()
and calledparent::setUp()
(WordPress/Tests/DB/RestrictedClassesUnitTest.php#L34-L35). But later it was renamed, and then it probably didn't make sense to continue callingparent::setUp()
(which was later renamed tosetUpPrerequisites()
): 00b895c.I found this in the context of the work to prepare this codebase for PHPCS 4.0 as
AbstractSniffUnitTest::setUpPrerequisites()
was renamed in 4.0 (PHPCSStandards/PHP_CodeSniffer@92cf10f#diff-91ba2a2a923bbfdaa61dcd31051d783bd0e7ff99f979f6e1a2917cae7dde3eb2L58).