From 7092e54840aa8a87624808e8ea7e5be1f5f0f56f Mon Sep 17 00:00:00 2001 From: Benedikt Heine Date: Fri, 4 Jan 2019 22:24:46 +0100 Subject: [PATCH] Control to print log messages during test The log messages are useless during general and automated testing. But while developing tests, the warning messages might be an easy debugging option to check why one's own test currently fails. --- test/test.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/test/test.c b/test/test.c index d8f907a..6232cab 100644 --- a/test/test.c +++ b/test/test.c @@ -31,8 +31,11 @@ int main(int argc, char *argv[]) { } base = dirname(prog); - // do not print out warning messages, when executing tests - dunst_log_init(true); + /* By default do not print out warning messages, when executing tests. + * But allow, if DUNST_TEST_LOG=1 is set in environment. */ + const char *log = getenv("DUNST_TEST_LOG"); + bool printlog = log && atoi(log) ? true : false; + dunst_log_init(!printlog); GREATEST_MAIN_BEGIN(); RUN_SUITE(suite_utils);