Hi! Thanks a lot for your reply!

As for the testing part, I had checked those modules indeed, but had the following thoughts about them:

• their use seem to be very sequential, where I would prefer an object approach
• I will need some "common" mocked services to use with all my different tests, and I don't want to duplicate mocking codes for each test, even though I could factorize the mocking in some shared methods

In the end, I can see this advantage of using Test::MockObject over using mocking by inheritance as I was suggesting:

• gain ability to check the program's behaviour vis-a-vis the mocked class (via methods like call_pos, call_args, next_call, etc.)

What other advantages would I gain?
Is there any caveats at mocking by inheritance as I was suggesting?

PS: oh, about your comment, I may have misused the word 'environnement' in my question: I didn't mean architecture environment but rather meant 'test situation' (I corrected it in the text).