Forum Discussion

krenevla's avatar
krenevla
Contributor
12 years ago

loosing focus from active window under certain conditions

Hello there,

I am facing not-sure-how-to-reproduce-but-very-annoying-bug.
I have tabbed view and one window undocked. In this undocked window, there are test sets which I am running.
In main window, I have Groovy test step and I am coding there. Problem is, that I looses focus from Groovy quite often and I have to reopen tab with Groovy in order to get focus and even cursor again.

Tests which I am running are modularized and they uses third Run mode option (run primary test case (wait for running to finish, thread safe))

I think that this bug appear when modularized tests I am running at undocked window are executing "run test case" test step.

How to (hopefully) reproduce on 4.5.1:
1 - use Tabbed view
2 - have a test set with modularized tests with third Run mode option selected
3 - make window with this test set floating and put it to second monitor
4 - run these tests
4 - in main window, open some Groovy step and try to write some code

I think this may lead to focus loose I am writing about
  • krenevla's avatar
    krenevla
    Contributor
    12 years ago
    update: so this happens also in single window mode and trigger is when running test in background executes other modularized test

    how to reproduce then:
    - have some test which runs other test in third run mode and run it in the loop
    - open groovy test step in other test case and try to edit it
    - you will loose focus each time modularized test is executed
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    12 years ago
    Thank you for reporting your problem.

    I have logged this as a feature request in our backlog (losing focus is not really a bug, just a behavior which some users may find unhelpful... other users may like the idea of having test windows re-gaining focus when the tests run).

    The ID of the ticket is SOAPUI-4654.

    Renato Athaydes
    SmartBear Software
  • krenevla's avatar
    krenevla
    Contributor
    12 years ago
    sorry for delay in reply.

    In my view this is not a feature but really a bug. This happens also when You have these modularized tests running and You open Property transfer from different test You are developing. Property transfer will became completely disabled when this running test runs some module so You have to close it and reopen it.

    Not sure if You reproduced it on Your own, but it is really annoying and I can't imagine how someone may like this behavior
  • krenevla's avatar
    krenevla
    Contributor
    12 years ago
    here is screenshot with disabled Property transfer step



    the same it does for Groovy test step but its not so visible there but impact is the same -- you have to reopen it
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    12 years ago
    I updated the ticket with the new information you provided.

    Thanks again for reporting this.

    Regards,
    Max
    SmartBear Software
  • krenevla's avatar
    krenevla
    Contributor
    11 years ago
    Hi,

    is there any update on this?
    It's really annoying bug for me :/

    THanks,

    Vladan
  • krenevla's avatar
    krenevla
    Contributor
    11 years ago
    Hi,

    issue is still there, at least in Linux version.
    How to reproduce -
    1 - open property transfer step or Groovy step or both
    2 - run test which runs module (last execution type (wait for finish), not sure if it's relevant)
    ---> both property transfer and Groovy are disabled, user needs to reopen them.

    This prevents of running some tests in background while working on new ones

    br, Vladan