TheAverageDev

[...] A useful addition to Function Mocker. The problem Mocking self returning methods used in client classes is possible in PHPUnit [...]

[...] This entry is part 12 of 13 in the series Function Mocker It’s good enough a function mocker to be released. The giants who lent the shoulders The whole function and method mocking thing [...]

[...] if Patchwork could make it: it does very easily as seen in this PHPUnit tests The function mocker While function mocking is not the way I will be walking as I will not mock interfaces I [...]

[...] This entry is part 3 of 3 in the series Function Mocker An update on the things to come for the function mocking project. Unified API Current release [...]

[...] as a client. What the two bullets above tell me is that, the same way I will have to update my test code as the WPSchedule_Time_Factory adds more cases, I will have to do the same for any other client [...]

[...] the WPSchedule_Time_Factory class I add a field and a method and this allows me to rewrite the test code to freeing the test code from the knowledge of the default class returned. A bigger thought [...]

[...] be tested like this using the Dependency Mocker class and providing some inline documentation: Test code could be slimmed down even more with refactoring and DRY principles. Next I’m thinking about [...]

[...] @depends notation in each DocBlock then I’ve just moved the effort somewhere else from the test code; since I can automate the generation of those @depends notations using live templates or [...]

[...] This entry is part 6 of 6 in the series Dependency Injection Container for PHP 5.2 An addition for a clearer interface to the dependency injection container. [...]

[...] This entry is part 4 of 4 in the series Dependency Injection Container for PHP 5.2 Adding post construction method calls to the PHP 5.2 dependency injection [...]

[...] calls will be used while developing with TDD methods to be swapped, maybe using a Dependency Injection Container, with the ad-hoc adapter in production code. All this with as little overhead as [...]

[...] This entry is part 2 of 2 in the series Dependency Injection Container for PHP 5.2 Laying out a PHP 5.2 compatible dependency injection container. A coding [...]

[...] to allow more flexibility since I’m already using it with a degree of satisfaction. The post Function mocking with Patchwork 02 appeared first on theAverageDev. [...]

[...] is called. For instance methods that’s pretty much the same melody More to come soon. The post Function mocking with Patchwork 04 appeared first on theAverageDev. [...]

[...] test result and contribute to the test passing/failing condition. Kudos to PHPUnit. The post Function mocking with Patchwork appeared first on theAverageDev. [...]

[...] think the soon-to-ship version 0.2.0 will sport that interface to keep things simple. The post Function mocking with Patchwork 06 appeared first on theAverageDev. [...]

[...] defined functions (optional) inject call to adapter methods in place of direct calls to WordPress functions in class to test scan a class calling an adapter and generate its custom adapter class Long [...]

[...] A first working version of the WordPress functions dumper. At least it does something useful now I’ve pushed a working version of the plugin [...]

[...] process I do not want to lose any possibility a “normal” evaluation would allow. In WordPress functions a recurring case is the one where a value might be a string or a boolean, an array or a [...]

[...] about the whole process I’m thinking about a stream wrapper like Patchwork to log calls to WordPress functions made by the target code. That would allow me to create ad-hoc adapters taking dynamic [...]

[...] This entry is part of 2 in the series TDDing with function-mocker Where I start TDDing a small WordPress component using function-mocker. [...]

[...] This entry is part 2 of 2 in the series TDDing with function-mocker Nailing down the basics. Set up I will use Composer to deal with th [...]

[...] This entry is part 3 of 3 in the series TDDing with function-mocker Where I pick up with TDD WordPress components using Codeception and [...]

[...] This entry is part 4 of 4 in the series TDDing with function-mocker Function-mocker uses closures to set return values: need I say more? No [...]

[...] to trigger Route Pages functions. The problem Route pages offer is two-fold: on one side the WordPress plugin wraps WP Router methods and hooks in a Laravel-like fashion to allow for easy and [...]

[...] into function call logging. The idea I’d like to be able to provide myself with a tool, a WordPress plugin specifically, to be used in staging environment and that would allow me to create ad-hoc [...]

[...] I’ve embarked on the quest to create some custom field types for the Custom Meta Boxes 2 WordPress plugin and I’ve had a measure of success in implementing a nested sortable list control based on [...]