Thomas Haller 643d412688 test: setup logging during nmtst_init_assert_logging() ... Before, when having a test with nmtst_init_assert_logging(), the caller was expected to setup logging separately according to the log level that the test asserts against. Since 5e74891b58, the logging level can be reset via NMTST_DEBUG also for tests that assert logging. In this case, it would be useful, if the test would not overwrite the logging level that is set externally via NMTST_DEBUG. Instead, let the test pass the logging configuration to nmtst_init_assert_logging(), and nmtst will setup logging -- either according to NMTST_DEBUG or as passed in. This way, setting the log level works also for no-expect-message tests: NMTST_DEBUG="debug,no-expect-message,log-level=TRACE" $TEST (cherry picked from commit b6d3b98655)		2015-04-09 08:22:28 +02:00
..
leases	dhcp: make dhclient lease parsing code testable	2013-11-08 16:46:43 -06:00
Makefile.am	tests: enable valgrind tests for tests	2015-03-13 11:50:04 +01:00
test-dhclient-commented-duid.leases	dhclient: add testcases for reading DUIDs from leasefiles	2013-01-29 10:18:42 -06:00
test-dhclient-duid.leases	dhclient: add testcases for reading DUIDs from leasefiles	2013-01-29 10:18:42 -06:00
test-dhcp-dhclient.c	dhcp/tests: fix memleaks in test code for valgrind	2015-03-13 11:50:04 +01:00
test-dhcp-utils.c	test: setup logging during nmtst_init_assert_logging()	2015-04-09 08:22:28 +02:00