just enhancement, I think setUp() function should be placed in first place

Console view manager config takes priority?

Yes in the ConsoleViewManager, better suggestions? Should be covered in the "with-console" testcase.

It's just that merging it means that console will always win over http. A bit problematic, IMO. I would try solving this problem in the ViewManagerFactory instead, no?

To clarify: we could inject multiple configs and decide (at runtime) which one to use (depending on whether we are in console context or not)

I am not sure if i got it right. I just put it in the ConsoleViewManager, because i thought its the right place for it. The ViewManagerFactory returns the ConsoleViewManager in console context. For the ConsoleViewManager the "console view manager configuration" is priority. The new configuration should not affect the HttpViewManager.

I am also not sure if runtime-merging (and thus destroying the possibility of accessing original config) is a good idea.

Another point: We should definitly use Stdlib\ArrayUtils::merge() instead of plain old array_merge() to keep full power of configuration merge (see #6899, #6903)!

Should probably check Console::isConsole() instead of checking what config was passed in, no?

Is there any use case for using ConsoleViewManager in the http context? I can´t imagine one. https://github.com/zendframework/zf2/blob/master/library/Zend/Mvc/Service/ViewManagerFactory.php#L28 is checking for the console context right now.

I thought supporting the current configuration key, will not cause a breaking change, because
The default configuration for displayNotFoundReason and displayExceptions is set to true: https://github.com/zendframework/zf2/blob/master/library/Zend/Mvc/View/Console/ExceptionStrategy.php#L25 and https://github.com/zendframework/zf2/blob/master/library/Zend/Mvc/View/Console/RouteNotFoundStrategy.php#L38. Otherwise we could just remove the $config['view_manager] check or solve it within the factory. I am not familiar how use usally handle backwardcompatibility.

Missed the fact that the view manager factory selects the correct view manager upfront: my bad. This fix is valid.