e524724f9d
Calling rowCount inside another auto test function yields unexpected results, if rowCount fails. Without a check for QTest::currentTestFailed the failure will not stop the calling function and other functions like rowsInserted and rowsRemoved might happily continue even though their requirements are not met. That caused a crash on winrt under certain circumstances. In addition to that TRY_WAIT now does not only wait for the given amount of time, but also gives feedback about its result. Before this change TRY_WAIT was basically useless, as it gave no indication about its success/failure. Fixes: QTBUG-71121 Change-Id: Ibd3f233a0b913db799814be97c4274d510643c74 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io> |
||
---|---|---|
.. | ||
qcolordialog | ||
qdialog | ||
qerrormessage | ||
qfiledialog | ||
qfiledialog2 | ||
qfilesystemmodel | ||
qfontdialog | ||
qinputdialog | ||
qmessagebox | ||
qprogressdialog | ||
qsidebar | ||
qwizard | ||
dialogs.pro |