| Procedural testing isn't hard. All that dependency crap is only a result of your AbstractTestingFrameworkMethodFactoryClassMockMethodGenerator() and similarly useless abstractions, anyway. A simple module system can be implemented in a single function and referenced from test code as easily as: test_requires('module1','module2'); Purely procedural tests are as easy as: assert_equals(function_one('example_input'),'expected_output');
assert_not_equals(function_two(true),false); Full featured test framework: function assert_equals($a,$b) { return $a==$b; }
function assert_not_equals($a,$b) { return $a!=$b; } (Edit: I don't believe I missed the point - 'dependency injection', a recent term in PHP, essentially means tightly coupling to an entire DI system instead of directly to a single dep as demonstrated above. Either way, loose coupling is a concept to strive for as far as reasonably possible - not an absolute requirement. If your code requires something else, then it requires something else. The solution is not to create a new AbstractPretenderOfTotalWorldVisibilityEvenThoughControlFlowIsNowAllOverTheShop() After all, if you carry that tight coupling argument further you could claim that by virtue of writing PHP at all you are tight coupling to a certain, if broad, class of processor architectures. There has to be a limit somewhere! Mostly, that's determined by legibility/maintaintability and programmer time, not by abstract measures of correctness.) |