Update dependencies. Rename tests. Fix deprecations

Author: iobrado

.gitignore

@@ -2,6 +2,7 @@ composer.phar
 /vendor
 phpcs-report.xml
 composer.lock
+.phpunit.result.cache
 
 # Mac OS custom attribute store and thumbnails
 *.DS_Store

CHANGELOG.md

@@ -10,6 +10,13 @@ The semantic versioning started from version 0.2.1.
 
 _No documentation available about unreleased changes yet._
 
+## [3.0.1](https://github.com/infinum/eightshift-coding-standards/compare/3.0.0...3.0.1)
+
+### Changed
+- Updated dependencies. PHPUnit had a security vulnerability that needed to be addressed. More recent versions of PHPUnit (v10+) introduced breaking changes that would require a major version bump. Priority of this release was to fix the security vulnerability.
+- Added exclude to deprecated ruleset since WordPressCS v3.3.0. Covered by PHPCompatibilityWP.
+- Renamed tests.
+
 ## [3.0.0](https://github.com/infinum/eightshift-coding-standards/compare/2.0.0...3.0.0)
 
 ### Changed
@@ -60,7 +67,7 @@ _No documentation available about unreleased changes yet._
 - Add ignoreComments property for the line length sniff
 
 ### Fixed
-- Fixed the edge case with overwriting libs classes. 
+- Fixed the edge case with overwriting libs classes.
 
 ### Changed
 - Code cleanup in EightShift ComponentsEscape sniff
@@ -76,22 +83,22 @@ _No documentation available about unreleased changes yet._
 
 ### Fixed
 - Fixed `Eightshift.Security.ComponentsEscape` sniff
-  - There was a case where the next string token caused issue because there was no guard clause 
+  - There was a case where the next string token caused issue because there was no guard clause
     to check if the string is actually a Components class or not.
 
 
 ## [1.4.0](https://github.com/infinum/eightshift-coding-standards/compare/1.3.0...1.4.0) - 2022-03-09
 
 ### Added
-- EightShift ruleset: add rules for use statements 
+- EightShift ruleset: add rules for use statements
   - Adds a new dependency on the Slevomat Coding Standard library.
   - Adds four sniffs from this coding standard to the ruleset:
       1. Forbidding unused `use` statements.
       2. Enforcing fully qualified global functions and constants.
       3. Enforcing import `use` statements for everything else.
   - Includes fixing up the EightShift coding standards code base for these new rules.
   - Ref: https://github.com/slevomat/coding-standard
-- Add new EightShift FunctionComment sniff 
+- Add new EightShift FunctionComment sniff
   - This sniff overloads the `Squiz.Commenting.FunctionComment` sniff which normally comes included via the `WordPress-Docs` ruleset and makes an allowance for the `__invoke` method in the CLI classes.
   - Includes:
     - Unit tests.
@@ -157,7 +164,7 @@ A huge thanks to Juliette Reinders Folmer (@jrfnl) for amazing help in fixing to
 
 ### Changed
 - Updated sniffs namespace
-  
+
 ### Fixed
 - Fix docblocks in the sniffs
 
@@ -181,7 +188,7 @@ We renamed the package from `infinum/coding-standards-wp` to `infinum/eightshift
 
 This is the official release of the Eightshift coding standards for WordPress. It contains breaking changes, mostly in
  regard
- of the naming scheme. 
+ of the naming scheme.
 To equate the way we write our PHP and JS we opted to follow a modified PSR standards.
 What this means is that we will remove liberal spacing, add some PSR12 modifications regarding arguments placing in closures, change snake_case with CamelCase for classes (for autoload puropses) and some other minor changes that will be documented below.
 If you wish to use the old standards, be sure to modify your projects `composer.json` file with the appropriate version.

…cs/Security/ComponentsEscapeStandard.xml …/Docs/Security/HelpersEscapeStandard.xmlEightshift/Docs/Security/ComponentsEscapeStandard.xml renamed to Eightshift/Docs/Security/HelpersEscapeStandard.xml Eightshift/Docs/Security/ComponentsEscapeStandard.xml renamed to Eightshift/Docs/Security/HelpersEscapeStandard.xml

@@ -111,8 +111,17 @@ public function process_token($stackPtr)
 				}
 			}
 
-			// Check for Helpers string token.
-			$helpersClassNamePtr = $phpcsFile->findNext(\T_STRING, ($stackPtr + 1), null, false, 'Helpers');
+			// Check for Helpers string token that is followed by the double colon (static method call).
+			// We need the class name "Helpers", not a namespace segment "Helpers".
+			$helpersClassNamePtr = false;
+			$searchPtr = $stackPtr;
+
+			while (($searchPtr = $phpcsFile->findNext(\T_STRING, ($searchPtr + 1), null, false, 'Helpers')) !== false) {
+				if (isset($tokens[$searchPtr + 1]) && $tokens[$searchPtr + 1]['code'] === \T_DOUBLE_COLON) {
+					$helpersClassNamePtr = $searchPtr;
+					break;
+				}
+			}
 
 			if (!$helpersClassNamePtr) {
 				// If there is no Helpers down the line, just run the regular sniff.
@@ -180,7 +189,10 @@ public function process_token($stackPtr)
 					$checkedClassName = \explode('\\', $className);
 					$firstNamespacePart = $checkedClassName[0];
 
-					if ($lastNamespacePart === $firstNamespacePart) {
+					// For partial imports, the className must contain multiple parts (e.g. Helpers\Helpers::method())
+					// A single-part className like Helpers::method() with a partial import to the namespace
+					// would resolve to the namespace, not the class.
+					if ($lastNamespacePart === $firstNamespacePart && \count($checkedClassName) > 1) {
 						// Correctly used class name.
 						$methodNamePtr = $phpcsFile->findNext(
 							\T_STRING,