Stopping RIDE test runs cause execution problems

[Dada Dadai]

Hi All,

I have a problem in RIDE test runs. When I stop test execution in between, sometimes it causes stop working test execution function of the RIDE. The run button is not available.
I face with this issue all the time if I stop tests press "Stop" button 2 times.
WA: I have to restart ride to make it work again fully functional. I use Selenium and Selenium2Library test libaryries for my tests. I think that could be issue around these libraries.

Version numbers:
-- Robot Framework 3.0.2, RIDE 1.5.2.1, Selenium2Library 1.8.0, Selenium 2.53.6
-- Python 2.7.1, wx 2.8.12in win32

What do you think? Could you help me? 
Thank in advance!
Dániel

[Tatu Aalto]

Ugh

This was already a problem with RIDE 5 years ago, when I was using RIDE. Also back then, the solution was to restart RIDE. And it's not a problem with a libraries I was using, it is a problem with RIDE.

As a more permanent solution, you could run your test from command line and not from RIDE. Also there a many other editors, which may suite you better than RIDE. More details in: http://robotframework.org/#tools and click editors.

-Tatu
Send from my mobile

--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-users+unsub...@googlegroups.com.
To post to this group, send email to robotframework-users@googlegroups.com.
Visit this group at https://groups.google.com/group/robotframework-users.
For more options, visit https://groups.google.com/d/optout.

[Dada Dadai]

Hi,

Thanks for the information Tatu! So it is a RIDE issue. We use ride right now, I found quite fine for our purposes. Does anybody has a solution
to step over this issue?

I checked the editors again follow your link Tatu. I found RED there. It looks fine checking it functionality. It might be a "new" tool I skipped earlier (less than one years old).
What is the experince with it?

BR,
Dani

To post to this group, send email to robotframe...@googlegroups.com.

[adam.wyp...@gmail.com]

Hi Dani,

RED has 2 years it was started in March 2015 ;) 

BR,

-Adam.

[Krzysztof Jozefowicz]

Hi
Although latest RED is on 0.7.6 version it is fully functional Robot editor it is developed since 2 years. From feature standpoint it already surpass RIDE, especially on source editor (validation,code assistance,debug etc.).
Give it a try.

br
K

[Hélio Guilherme]

Sometimes (in Windows) the webdriver is still running and that is why the Run or Log buttons are disabled.

Below is my dramatic keyword to run at Suite Teardown:

Kill WebDriver

    Import Library    OperatingSystem

    ${os}=    OperatingSystem.Run and Return RC    ver

    ${webdriver}=    Set Variable If    ${os} == 0 \ and "${BROWSER.lower()}" in ('chrome', 'gc', 'googlechrome')    chromedriver.exe

    ${command}=    Set Variable If    ${os} == 0    taskkill /f /im

    ${command}=    Catenate    ${command}    ${webdriver}

    OperatingSystem.Run    ${command}

[Kevin O.]

I also suggest not hitting stop very quickly after you hit start. Wait until you see activity in the message window. Otherwise the spawned process will continue on in the background and cause problems with the listener that RIDE uses. To recover from that you can kill the Python processes not related to RIDE.

Kevin

[Dada Dadai]

Hi Adam and Krzysztof,

@Adam: Ok. It looks I followed RED not carefully.
@Krzysztof: Thanks for the hit, I am going to give it a try.

BR,
Daniel

[Dada Dadai]

Hi,

Thanks guys for the help. I modified your code Hélio for firefox. I have not found any spec. process related to firefox Webdriver, yet.
Therefore I killed the firefox.exe's. do you have anybetter solution? I put it my "kill browser" keyword to both suite setup and teardown,
it works fine. :)

Dániel