Check for extbase response type instead of current environment
It's currently not possible to run functional tests that expect frontend output of Extbase.
Extbase will check for current environment to be CLI context, which is true for functional tests.
Still the response might be a web Response which does not implement the called method.
This issue occurs in 7, 8 and master.
[TASK] Check for Extbase response type instead of environment
Functional tests always set CLI context to true. Even if Extbase returns
an Web\Response, the method getExitCode will be called, which only
exists in Cli\Response.
Therefore a check against the response type allows to run functional
tests with Web\Response in Extbase.
Reviewed-by: Benni Mack <email@example.com>
Tested-by: Benni Mack <firstname.lastname@example.org>
Reviewed-by: Markus Klein <email@example.com>
Tested-by: Markus Klein <firstname.lastname@example.org>