Jim Harris 56d35c5d13 test: forbid use of CU_ASSERT_FATAL ... Static analyzers don't see CU_ASSERT_FATAL as truly fatal, and will complain that code later in the function may try to dereference a NULL pointer. So we added SPDK_CU_ASSERT_FATAL which should be used instead. This still trips people up sometimes though - the static analyzer complains and then the developer will add other checks that pointers are not NULL. So instead, forbid use of CU_ASSERT_FATAL through check_format.sh and explain why. While here, fix up all of the existing CU_ASSERT_FATAL usages to either CU_ASSERT or SPDK_CU_ASSERT_FATAL. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I7974c8c85ddb89ed1b7d882db3a2eb0882ea0217 Reviewed-on: https://review.gerrithub.io/418111 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>		2018-07-06 18:35:03 +00:00
..
.gitignore	test: move JSON library unit tests to test/unit	2017-06-20 13:46:07 -04:00
json_write_ut.c	test: forbid use of CU_ASSERT_FATAL	2018-07-06 18:35:03 +00:00
Makefile	test: use spdk.unittest.mk for json unit tests	2018-02-14 10:40:40 -05:00