ServiceManager can't find classes by full namespace when testing with phpunit

Question

I'm retrieving instances from the ServiceManager by their full class names in some cases, for example:

$someThing = $serviceManager->get('MyModule\Some\Nice\Lib\SomeThing');

This works pretty well for HTTP MVC requests, however, when using phpunit, the ServiceManager can't find it. (It throws a Zend\ServiceManager\Exception\ServiceNotFoundException exception with message "Zend\ServiceManager\ServiceManager::get was unable to fetch or create an instance for ...")

I'm using the default testing bootstrap example from the docs and I experience this issue in two different projects on different mashines, so I guess this is a general problem.

My first guess was that it has something to do with MVC or application, becuase this is most likely the only real difference between testing and http. I even dumped the SM instances in both modes and compared them with each other, looked through the sources and searched the web.

Unfortunately, I can't paste any code due to my labor contract. However, as I said, I think this is a general problem so you should be able to easily reproduce it.

Does anybody know what is causing this issue and how to solve it?

score 0 · Answer 1 · answered Jan 04 '13 at 08:05

0

make sure you added your module to test config:

return array(
    'modules' => array(
        'MyModule',
        //...
    ),
    //...
);

otherwise ModuleManager will not try to load it, hence module autoloader will not be registered

answered Jan 04 '13 at 08:05

Xerkus

2,695
1
19
32

The module is loaded, I can also instantiate it directly using the `new` keyword. – Daniel M Jan 04 '13 at 08:21
then probably configuration for your service is in application level config and not loaded during tests? – Xerkus Jan 04 '13 at 12:22

score 0 · Accepted Answer · answered Jan 07 '13 at 11:14

0

I managed to locate the problem.

When you create an instance with its full class name using ServiceManager, it won't in fact be able to create it by default. However, if possible, it delegates the task to the abstract factories that are attached to it.

Now, when you create a Di instance using the DiFactory, the factory registers a DiAbstractServiceFactory to SM. And, you guess it, this abstract factory is able to instantiate classes by their full class names.

I've rarely used Di in this project (because I didn't really feel comfortable with it and used it wrong in the beginning; I know better now), which is why the only point where I instantiate Di is inside the onBootstrap() method of a module. This is fine in MVC context, however, as onBootstrap() is an HTTP MVC event handler, it won't be invoked in my testing application. Thus, no Di is instaniated at any time, thus, ServiceManager hasn't got the DiAbstractServiceFactory attached to it, thus it can't delegate the get() call, thus it fails to instantiate classes by their full class names.

It's as simple as that! :-)

The obvious solution: Create a Di instance inside the testing application.

answered Jan 07 '13 at 11:14

Daniel M

3,369
20
30

you forgot to mention most important part in your question: that you used Zend\Di and SM was merely a proxy. :P – Xerkus Jan 08 '13 at 00:00
Can you share the sample code. I also have the same problem and couldn't get over it. – Beniston Jan 10 '13 at 11:00
1

There is not much sample code to share. Simply invoke `$serviceManager->get('Di');` somewhere. – Daniel M Jan 10 '13 at 11:02
I have written the code based on http://zf2.readthedocs.org/en/latest/user-guide/unit-testing.html So in this can you please tell where and all the changes has to be done so that we can overcome the issue? – Beniston Jan 10 '13 at 11:49
So have I. Just put it somewhere where it's always being executed (for example in the Bootstrap.php). – Daniel M Jan 10 '13 at 12:43

ServiceManager can't find classes by full namespace when testing with phpunit

2 Answers2