[Tickets #14449] Re: Bug when calling test.php?app=ingo

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14449
------------------------------------------------------------------------------
  Ticket           | 14449
  Aktualisiert Von | webmaster at object.earth
  Zusammenfassung  | Bug when calling test.php?app=ingo
  Warteschlange    | Ingo
  Version          | 3.2.11
  Typ              | Bug
  Status           | Not A Bug
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


webmaster at object.earth (2016-08-25 14:25) hat geschrieben:

> You didn't say there was any failures in the test script, only that  
> there was an error in the log file.

The test script fails with an exception in the frontend at first call  
of https://webmail.domain.tld/test.php?app=ingo

> Furthermore, this is YOUR code, not Horde's. If you want it to
> be safe to run in the use case you are describing, YOU need
> to perform a test to be sure either there is an active session,
> or that the Mail API is available. Either way, not a bug.

I understand that the test script's purpose is to check a freshly,  
unmodified installation to be checked. It is not necessarily capable  
to run it's tests smoothly, if I changed something in the system after  
installation.
It does not matter, that my changes are valid and correct for  
production use. The test script may still fail.

If I want to ensure the test script to work correctly, after I applied  
changes to horde modules / configurations, I must test my changes  
seperately against the test script environment.