Volker Hilsheimer 54b276be0b testlib: Don't print QCOMPARE values if they lack string representation ... Before 0681a2dd5a, QCOMPARE'ing types for which no QTest::toString specialization exists did not output Actual and Expected lines on failure, as that would only print <null> for both values (which then look like the same value, confusingly). Commit 0681a2dd5a changed that behavior, and started printing the confusing <null> values. Take care of the logic in the formatFailMessage function: if both values are nullptr, then print only the variable names, but not the confusing <null> text representation of the values. Remove dead and duplicated code related to the formatting logic, add a self-test function, and update the expected_cmptest files. Fixes: QTBUG-104867 Pick-to: 6.4 Change-Id: I4be98e79f91196b14690a2cc0a68ffd50b431a45 Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>		2022-07-10 03:08:32 +00:00
..
initmain	Use SPDX license identifiers	2022-05-16 16:37:38 +02:00
outformat	Use SPDX license identifiers	2022-05-16 16:37:38 +02:00
qabstractitemmodeltester	Use SPDX license identifiers	2022-05-16 16:37:38 +02:00
qsignalspy	Use SPDX license identifiers	2022-05-16 16:37:38 +02:00
selftests	testlib: Don't print QCOMPARE values if they lack string representation	2022-07-10 03:08:32 +00:00
CMakeLists.txt	Exclude tst_selftests when feature process is disabled	2022-01-27 21:35:58 +02:00