unit test focus behavior with QTest

[MarekR22]

This should look like this (simple version):

void test_my_ctrl::test_lose_focus()
{
    my_ctrl ctrl;
    ctrl.setFocus(Qt::TabFocusReason); // first you make sure that focus is in correct place
    ctrl.selectAll(); // just in case if it is not selected, so old content will be replaced
    QTest::keyClicks(&ctrl, "1.23456789", Qt::NoModifier, 10); // then you type
 
    QCOMPARE(ctrl.text(), QString("1.23456789"));
    ctrl.clearFocus();
    QTest::qWait(100); // this may be needed to process some of posted events - it may be not needed
    QCOMPARE(ctrl.text(), QString("Focus Out"));
}

void test_my_ctrl::test_lose_focus()
{
    my_ctrl ctrl;
    ctrl.setFocus(Qt::TabFocusReason); // first you make sure that focus is in correct place
    ctrl.selectAll(); // just in case if it is not selected, so old content will be replaced
    QTest::keyClicks(&ctrl, "1.23456789", Qt::NoModifier, 10); // then you type

    QCOMPARE(ctrl.text(), QString("1.23456789"));
    ctrl.clearFocus();
    QTest::qWait(100); // this may be needed to process some of posted events - it may be not needed
    QCOMPARE(ctrl.text(), QString("Focus Out"));
}

To copy to clipboard, switch view to plain text mode 

Focus in event should be done in similar manner.
Advanced version should be data driven.

[bob_smith]

Nope, gave it up to a second (QTest::qWait(1000)) and still no good. Did you actually try your suggestion and, if so, using what platform and version? I ask because I went through a long conversation about a problem in wxWidgets (the framework that I'm moving from) that ended up being just a difference in event propagation behavior on different platforms.

[MarekR22]

We both forgot about little detail. To have focus widget HAS TO BE VISIBLE and I'm sure that this is the problem.
So just add ctrl.show() on front (or give parent which is visible) .

[bob_smith]

Sure enough that works. The only downside is that now the control is visible when the tests are run, of course. Originally I was hoping to have something that works in the same way as QTest::keyClicks in that the control is never actually visible to whoever is running the test when the keystrokes are entered. However now at least I have something that works, I’ll just have to see if it acceptable for use in our build process.

Thank you for your help.

[yunuscanemre]

Sure enough that works. The only downside is that now the control is visible when the tests are run, of course. Originally I was hoping to have something that works in the same way as QTest::keyClicks in that the control is never actually visible to whoever is running the test when the keystrokes are entered. However now at least I have something that works, I’ll just have to see if it acceptable for use in our build process.

Thank you for your help.

I know this is an old thread but I am posting this in case anyone else comes across it. I was able to get the focus events working during tests without having to show the widget. I called "QApplication::setActiveWindow(patient_);", where patient is my main widget which holds other widgets in it like line edits etc. After this focus events propagated properply.