Page MenuHomeDevCentral

Fix tests to allow coverage reports for Laravel applications
Open, Needs TriagePublic

Description

Tests succeed, but coverage report fails:

[phpunit] Generating code coverage report in HTML format ...
[phpunit] Fatal error: Uncaught Illuminate\Contracts\Container\BindingResolutionException: Target [Illuminate\Contracts\Debug\ExceptionHandler] is not instantiable. in /home/app/workspace/test-notifications-php/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 748

See also https://github.com/BenConstable/phpspec-laravel/issues/31 and https://github.com/laravel/framework/issues/10808

Event Timeline

dereckson renamed this task from Fix tests for to Fix tests to allow coverage reports.Sep 20 2018, 19:17
dereckson created this task.
dereckson renamed this task from Fix tests to allow coverage reports to Fix tests to allow coverage reports for Laravel applications.Sep 20 2018, 19:34
dereckson added a project: Auth Grove.

Development moratoire

Per T1771, we're currently considering implementing Keycloak as a reference identity management and SSO login product.

This product exposes a LDAP, OIDC (OpenID Connect) and SAML capabilities to authenticate users and applications. It seems to solve our main problems.

From there, it's not clear what we do with Auth Grove:

  • Scenario A. We drop it, and as users we directly interact with Keycloak. Development is discontinued.
  • Scenario B. Auth Grove is morphed into a front-end to use Keycloak: we expose current information, and interact with Keycloak API (through a generic set of classes to allow to switch to another solution) to set credentials and metadata.
  • Scenario C. We use both Keycloak AND Auth Grove. We don't make integrate with Keycloak at all, to stay independent and not vendor-locked.

While T1771 evaluation is ongoing, a moratoire covers any development activities related to Auth Grove, with the obvious exception of security issues.
This moratoire cover fully or partly this task.