Thomas Haller 25ade39752 tests: use NMTST_EXPECT*() macros ... Tests are commonly created via copy&paste. Hence, it's better to express a certain concept explicitly via a function or macro. This way, the implementation of the concept can be adjusted at one place, without requiring to change all the callers. Also, the macro is shorter, and brevity is better for tests so it's easier to understand what the test does. Without being bothered by noise from the redundant information. Also, the macro knows better which message to expect. For example, messages inside "src" are prepended by nm-logging.c with a level and a timestamp. The expect macro is aware of that and tests for it #define NMTST_EXPECT_NM_ERROR(msg) NMTST_EXPECT_NM (G_LOG_LEVEL_MESSAGE, "*<error> [*] "msg) This again allows the caller to ignore this prefix, but still assert more strictly.		2018-01-08 12:38:54 +01:00
..
tests	tests: use NMTST_EXPECT*() macros	2018-01-08 12:38:54 +01:00
meson.build	build: add initial support for meson build system	2017-12-13 15:48:50 +01:00
nms-ibft-connection.c	settings: clear unsaved flag on new settings-connection	2017-12-20 15:38:57 +01:00
nms-ibft-connection.h	build: don't add subdirectories to include search path but require qualified include	2016-11-21 14:26:37 +01:00
nms-ibft-plugin.c	all: use cast macros instead of C cast	2017-12-06 10:34:28 +01:00
nms-ibft-plugin.h	ibft: rename function names for ibft plugin	2016-10-11 11:37:46 +02:00
nms-ibft-reader.c	build: don't add subdirectories to include search path but require qualified include	2016-11-21 14:26:37 +01:00
nms-ibft-reader.h	include: use double-quotes to include our own headers	2017-03-09 14:12:35 +01:00