Functional routing tests
Some important routing features urgently need functional tests
Updated by Christopher Hlubek about 9 years ago
I get errors in an HTTP functional test for FLOW3 1.1 after this change. I know this worked last week in a demo application:
Uncaught Exception in FLOW3 #1301650951: No controller object was found for package "myvendor.mypackage", subpackage "Tests\Functional\Mvc\Fixtures", controller "login" in route "FLOW3 :: Functional Test: controller route parts are case insensitive". thrown in file .../Data/Temporary/Testing/Cache/Code/FLOW3_Object_Classes/TYPO3_Fluid_ViewHelpers_Link_ActionViewHelper_Original.php in line 90
I'm just generating a link inside a Fluid template (
<f:link.action action="index" controller="Login">Login</f:link.action>) of a Standard controller in an indexAction.
The problem seems to be the route "FLOW3 :: Functional Test: controller route parts are case insensitive" which throws an exception after merging the given route values (which do not contain a subpackage) on the defaults (which define a subpackage Tests\Functional\...) because a controller with that name could not be found (which is correct, since the LoginController does not exist for subpackage Test\Functional\Mvc\Fixtures).
So either we have to fix the subpackage override (no or NULL subpackage overrides a given subpackage) or disable the exception and just return FALSE in
resolves(...) if the controller object is not found.