a961848c16
The old code used a data-driven test to check that itemAt(i), 0 ≤ i ≤ 2, was returning non-nullptr. It re-created the widgets and the layout for each data tag anew, leaking the widgets by the way. Using data-driven test machinery here is overkill. Remove it and create the widgets in a C array on the stack, so they're not leaked, and iterate over them using range-for. Also check not just for nullptr, but also that the pointer matches the widgets we put into layout, at the position we put them in. Amends the start of the public history. Pick-to: 6.8 6.5 5.15 Change-Id: Ib808aa6756c6550a61a4768edfc5021f2f6ae3b3 Reviewed-by: Axel Spoerl <axel.spoerl@qt.io> (cherry picked from commit 159029b58753ad8a76eef9ea105275001a430ef2) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>