Michael Urman wrote:
On 10/25/06, Tim Janik <timj imendio com> wrote:- GLib based test programs should never produce a "CRITICAL **:" or "WARNING **:" message and succeed.It would be good not to make it impossible to test WARNINGs and CRITICALs. After all, error cases are often the least tested part of an application, so it's important to make sure the base library detects and handles the error cases correctly.
Testing those is like testing segfault handling, i.e. just nuts. The behavior is undefined once they print. (Well, for critical anyway. g_warning seems to be less consistently used)
Havoc