Steve-Dee-Designs
/
woocommerce
mirror of https://github.com/woocommerce/woocommerce.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
woocommerce/tests/Tools/CodeHacking/Hacks/BypassFinalsHack.php

33 lines
723 B
PHP
Raw Normal View History

Barebones implementation of a code hacker for unit tests. The "code hacker" is a class that hooks on filesystem events (using stream_wrapper_unregister) in order to allow for dynamically modifying the content of PHP code files while they are loaded. The code hacker class allows registering hacks, which are functions that take source code as input and return the modified code. A hack can be a standalone function or a class with a "hack" method. A few hacks are provided off the shelf. One allows mocking standalone PHP functions (WP, WOO or not), another one allows mocking static methods, and there's the one that removes the "final" qualifier from a class definition. This helps unit testing stuff that would otherwise be quite hard to test.
2020-04-09 14:32:40 +00:00
<?php
Fix code sniffer errors in CodeHacker and related classes.
2020-04-16 13:03:15 +00:00
/**
* BypassFinalsHack class file.
*
* @package WooCommerce/Testing
*/
// phpcs:disable Squiz.Commenting.FunctionComment.Missing
Barebones implementation of a code hacker for unit tests. The "code hacker" is a class that hooks on filesystem events (using stream_wrapper_unregister) in order to allow for dynamically modifying the content of PHP code files while they are loaded. The code hacker class allows registering hacks, which are functions that take source code as input and return the modified code. A hack can be a standalone function or a class with a "hack" method. A few hacks are provided off the shelf. One allows mocking standalone PHP functions (WP, WOO or not), another one allows mocking static methods, and there's the one that removes the "final" qualifier from a class definition. This helps unit testing stuff that would otherwise be quite hard to test.
2020-04-09 14:32:40 +00:00
Move testing tools to the tests/Tools directory The testing tools (only the code hacker at this time) have been moved from 'src' to 'tests/Tools', since many opcode cache plugins load the whole src folder in production. Also, an extra autoloader is set in the tests bootstrap so that the 'tests/Tools' directory corresponds, using PSR4, to the 'Automattic\WooCommerce\Testing\Tools' namespace.
2020-05-18 09:31:59 +00:00
namespace Automattic\WooCommerce\Testing\Tools\CodeHacking\Hacks;
Barebones implementation of a code hacker for unit tests. The "code hacker" is a class that hooks on filesystem events (using stream_wrapper_unregister) in order to allow for dynamically modifying the content of PHP code files while they are loaded. The code hacker class allows registering hacks, which are functions that take source code as input and return the modified code. A hack can be a standalone function or a class with a "hack" method. A few hacks are provided off the shelf. One allows mocking standalone PHP functions (WP, WOO or not), another one allows mocking static methods, and there's the one that removes the "final" qualifier from a class definition. This helps unit testing stuff that would otherwise be quite hard to test.
2020-04-09 14:32:40 +00:00
/**
* Code hack to bypass finals.
*
* Removes all the "final" keywords from class definitions.
*/
final class BypassFinalsHack extends CodeHack {
public function hack( $code, $path ) {
if ( stripos( $code, 'final' ) !== false ) {
$tokens = $this->tokenize( $code );
$code = '';
foreach ( $tokens as $token ) {
$code .= $this->is_token_of_type( $token, T_FINAL ) ? '' : $this->token_to_string( $token );
}
}
return $code;
}
}
Fix code sniffer errors in CodeHacker and related classes.
2020-04-16 13:03:15 +00:00
// phpcs:enable Squiz.Commenting.FunctionComment.Missing