Clemens Sielaff 2a24c3c268 Fixed Bug in QVariant comparison when containing QStringLists ... As it were, QStringLists were not handled explicitly when comparing QVariants. If both QStringLists contained only a single entry, they were treated as QStrings - if both QStringLists were empty, there were equal (correctly so) - but if one of the QStringLists had more than one entry, the compare function fell through to returning always 1. As discussed here: https://stackoverflow.com/a/38492467/3444217 Added rich comparison tests for all non-numerical, non-recursive QVariants that support them (except QModelIndex and QPersistentModelIndex) Task-number: QTBUG-54893 Change-Id: Icc5480d9ba056ee5efe83da566c5829caa1509d7 Reviewed-by: Jędrzej Nowacki <jedrzej.nowacki@theqtcompany.com>		2016-08-03 11:16:35 +00:00
..
stream	Split the QGuiVariant test from the Core one.	2012-07-25 00:48:33 +02:00
.gitignore	Moving relevant tests to corelib/kernel	2011-09-01 12:42:14 +02:00
qvariant.pro	Add C++11 if available for QVariant autotest	2014-11-13 15:21:07 +01:00
qvariant.qrc	Cleanup mess in public type ids.	2012-01-25 21:08:08 +01:00
tst_qvariant.cpp	Fixed Bug in QVariant comparison when containing QStringLists	2016-08-03 11:16:35 +00:00