Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Jubula » Issues When Starting/Stopping Web Browser AUTs(There appear to be some issues with starting/stopping various web browsers AUTs, some more severe than others.)
Issues When Starting/Stopping Web Browser AUTs [message #1723470] Mon, 15 February 2016 20:34 Go to next message
Drew Snader is currently offline Drew SnaderFriend
Messages: 7
Registered: February 2016
Junior Member
I am seeing different (possibly related) anomalies when I attempt to use various web browsers to run the Jubula example SimpleAdderHTML tests and would appreciate any information on how to resolve them. The issues occur when I start and stop a Chrome AUT or an Internet Explorer AUT from the Jubula ITE. My colleague is observing the same behaviors with Chrome and IE and similar issues with a Firefox AUT. I have not been able to find any mention of these issues in the Jubula forum.

Has anyone experienced anything similar to the behavior described below? Are there any actions I can take to correct the issues?

The issues are:
1. Starting the AUT from Jubula - Each browser (Chrome, IE, Firefox) exhibits different problems on startup.
2. Stopping the AUT from Jubula - Although all browsers can be shut down from Jubula, a NullPointerException is recorded in the Jubula log.

I am using Jubula 8.2.0.021 in a Windows 7 environment with Java 8, IE version 11, and Chrome version 48. My colleague's environment is the same configuration. I created a Jubula project, imported the Samples_8.2 and bound_modules_samples_8.2 projects, and made no changes to the project other than to create separate AUT configurations for Chrome and IE. I use the Jubula Embedded AUT Agent.

I am able to start the Chrome browser instance from the Jubula ITE and successfully run the example tests, however, I am not able to start the IE browser without errors. I have attached images that show screen images of both Chrome and IE.

Starting AUTs

Chrome

The Chrome AUT starts and I can run the SimpleAdderHTML tests, however the following entry appears in the rc_html.log when the Chrome AUT starts:

2016-02-12 16:21:08.717 [SocketListener0-1] WARN org.openqa.selenium.net.Urls - It looks like your baseUrl (http://www.eclipse.org/jubula/example/auts/adder/SimpleAdder.html) is pointing to a file, not a directory (it doesn't end with a /). We're going to have to strip off the last part of the pathname.

The Chrome browser's address field displays the following URL when Chrome starts:
http://www.eclipse.org/selenium-server/core/RemoteRunner.html?sessionId=38b22e17a8cc493b9061b009abf6240a&multiWindow=false&baseUrl=http%3A%2F%2Fwww.eclipse.org%2Fjubula%2Fexample%2Fauts%2Fadder%2FSimpleAdder.html&debugMode=false

Chrome has an additional issue at startup that I suspect has something to do with Jubula's interaction with Selenium. Chrome reports a problem with a command-line flag ("--disable-web-security"), but handles the issue well by simply displaying a warning message. (See the attached "Chrome AUT Startup" image file.)

Is there a way to configure Jubula/Selenium and remove that command-line flag?

One additional fact that is likely related to the disable-web-security Chrome command-line flag is that some web sites do not render in the Chrome browser. For example, the SimpleAdderHTML and www.amazon.com web pages both display properly. However, if I set the AUT configuration's AUT URL to be www.google.com or www.airtable.com, the browser fails to display the web site and reports an ERR_INSECURE_RESPONSE error. (See the attached "Chrome Insecure Response Error for Google Web Site" image file.) The SimpleAdderHTML web page uses HTML 4.01 Tranisitional, whereas the other three web sites use HTML 5, but I don't think that this difference has any bearing on the problem.

Internet Explorer

When the IE AUT starts, Jubula logs the same warning in the rc_html.log, however IE does not handle the issue well at all. The log entry for IE is:
2016-02-12 16:32:09.480 [SocketListener0-1] WARN org.openqa.selenium.net.Urls - It looks like your baseUrl (http://www.eclipse.org/jubula/example/auts/adder/SimpleAdder.html) is pointing to a file, not a directory (it doesn't end with a /). We're going to have to strip off the last part of the pathname.

When the IE AUT starts, the browser window tries to display content in a single frame and fails. In Jubula's Running AUTs view, the running IE AUT configuration appears, but the HTML tests fail immediately when I try to run them. (See the attached "Internet Explorer AUT Startup" image file.)

Firefox

When the Firefox AUT starts, it displays an HTTP 404 File Not Found error. I don't have any more details for this issue, but can provide them if needed, although I suspect that Firefox is just exhibiting different behavior for the same issue as describe above for Chrome and IE.

Stopping AUTs

Chrome

This may be unrelated to the above issues, but when I select the running Chrome AUT in the Jubula Running AUTs tab and click on the Stop AUT button, the Chrome browser instance appears to shut down properly and the Jubula GUI does not report an errors, but the following entry appears in the rc_html.log:

2016-02-12 16:25:22.793 [SocketListener0-9] ERROR o.o.s.s.commands.SeleniumCoreCommand - Exception running 'getLocation 'command on session null
java.lang.NullPointerException: sessionId should not be null; has this session been started yet?
at org.openqa.selenium.server.FrameGroupCommandQueueSet.getQueueSet(FrameGroupCommandQueueSet.java:220) ~[selenium-server-standalone-2.46.0785152283399705870.jar:na]
at org.openqa.selenium.server.commands.SeleniumCoreCommand.execute(SeleniumCoreCommand.java:55) ~[selenium-server-standalone-2.46.0785152283399705870.jar:na]
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(SeleniumDriverResourceHandler.java:611) [selenium-server-standalone-2.46.0785152283399705870.jar:na]
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleCommandRequest(SeleniumDriverResourceHandler.java:405) [selenium-server-standalone-2.46.0785152283399705870.jar:na]
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(SeleniumDriverResourceHandler.java:151) [selenium-server-standalone-2.46.0785152283399705870.jar:na]
at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1526) [selenium-server-standalone-2.46.0785152283399705870.jar:na]
at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1479) [selenium-server-standalone-2.46.0785152283399705870.jar:na]
at org.openqa.jetty.http.HttpServer.service(HttpServer.java:920) [selenium-server-standalone-2.46.0785152283399705870.jar:na]
at org.openqa.jetty.http.HttpConnection.service(HttpConnection.java:820) [selenium-server-standalone-2.46.0785152283399705870.jar:na]
at org.openqa.jetty.http.HttpConnection.handleNext(HttpConnection.java:986) [selenium-server-standalone-2.46.0785152283399705870.jar:na]
at org.openqa.jetty.http.HttpConnection.handle(HttpConnection.java:837) [selenium-server-standalone-2.46.0785152283399705870.jar:na]
at org.openqa.jetty.http.SocketListener.handleConnection(SocketListener.java:243) [selenium-server-standalone-2.46.0785152283399705870.jar:na]
at org.openqa.jetty.util.ThreadedServer.handle(ThreadedServer.java:358) [selenium-server-standalone-2.46.0785152283399705870.jar:na]
at org.openqa.jetty.util.ThreadPool$PoolThread.run(ThreadPool.java:537) [selenium-server-standalone-2.46.0785152283399705870.jar:na]
2016-02-12 16:25:22.793 [Timer-2] ERROR c.b.jubula.rc.html.WebAUTServer - ERROR Server Exception: sessionId should not be null; has this session been started yet?
com.thoughtworks.selenium.SeleniumException: ERROR Server Exception: sessionId should not be null; has this session been started yet?
at com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:111) ~[selenium-java-2.46.06786205006457391181.jar:na]
at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:105) ~[selenium-java-2.46.06786205006457391181.jar:na]
at com.bredexsw.jubula.rc.html.web.driver.RobotWebCommandProcessor.doCommand(RobotWebCommandProcessor.java:67) ~[com.bredexsw.jubula.rc.html_4.0.0.201510211315.jar:na]
at com.thoughtworks.selenium.HttpCommandProcessor.getString(HttpCommandProcessor.java:274) ~[selenium-java-2.46.06786205006457391181.jar:na]
at com.thoughtworks.selenium.DefaultSelenium.getLocation(DefaultSelenium.java:458) ~[selenium-java-2.46.06786205006457391181.jar:na]
at com.bredexsw.jubula.rc.html.WebAUTServer$1.run(WebAUTServer.java:237) ~[com.bredexsw.jubula.rc.html_4.0.0.201510211315.jar:na]
at java.util.TimerThread.mainLoop(Timer.java:555) [na:1.7.0_80]
at java.util.TimerThread.run(Timer.java:505) [na:1.7.0_80]
2016-02-12 16:25:22.793 [Connection.ReaderThread:Socket[addr=/10.0.2.15,port=50545,localport=50546]] WARN org.openqa.jetty.http.HttpServer - java.lang.InterruptedException: sleep interrupted


Internet Explorer

When I perform the same Stop AUT to shutdown the IE browser, the browser shuts down with no apparent errors, like the Chrome browser, but the following entries appear in the rc_html.log:

2016-02-12 16:34:23.136 [SocketListener0-2] WARN o.o.s.s.b.HTABrowserLauncher - Embedded iexplore seems to have ended on its own (did we kill the real browser???)
2016-02-12 16:34:23.215 [Connection.ReaderThread:Socket[addr=/10.0.2.15,port=50601,localport=50602]] WARN org.openqa.jetty.http.HttpServer - java.lang.InterruptedException: sleep interrupted
Re: Issues When Starting/Stopping Web Browser AUTs [message #1723472 is a reply to message #1723470] Mon, 15 February 2016 20:59 Go to previous messageGo to next message
Drew Snader is currently offline Drew SnaderFriend
Messages: 7
Registered: February 2016
Junior Member
...and to summarize, the two most important issues that I need to resolve first are:
1) the Chrome AUT security error that prevents access to web sites like google.com and airtable.com and
2) the inability to access any web site with an Internet Explorer AUT.
Re: Issues When Starting/Stopping Web Browser AUTs [message #1723982 is a reply to message #1723472] Fri, 19 February 2016 12:41 Go to previous messageGo to next message
Oliver Goetz is currently offline Oliver GoetzFriend
Messages: 219
Registered: May 2011
Senior Member
Hi Drew,

thank you for your detailed error description. I will take a look at it as soon as I find the time next week.
Regards
Oliver
Re: Issues When Starting/Stopping Web Browser AUTs [message #1724297 is a reply to message #1723982] Mon, 22 February 2016 21:22 Go to previous messageGo to next message
Drew Snader is currently offline Drew SnaderFriend
Messages: 7
Registered: February 2016
Junior Member
Thank you, Oliver. I look forward to your help.

I found a work-around for my issue with a Chrome web browser AUT (the security error that prevents access to some web sites), but I am not sure that it is the best way to handle the issue. Note that the work-around did not help with the Internet Explorer problem.

The fix involves adding the certificate (that the Selenium proxy server uses for SSL connections) to the Windows Trusted Root Certificate Authorities list. I obtained the certificate file by downloading the Selenium Standalone Server 2.x jar file from the Selenium web site (docs.seleniumhq.org/download/).

Inside the jar file is a directory named sslSupport. That directory contains the certificate file cyberVillainsCA.cer. (Curiously the issuer of that certificate is "CyberVillians.com" - with the i and a reversed in the domain name.) I extracted the certificate file from the Selenium jar file and installed the certificate using the procedure that is explained very clearly on the following web page:

blog.mogotest.com/2013/03/05/how-to-accept-self-signed-ssl-certificates-in-selenium2/

The web page at the following URL provides some additional insight into Selenium's use of the CyberVillains certificate:

sauceio.com/index.php/2010/10/sauce-labs-solves-real-world-selenium-issues/

Once I had installed the SSL certificate, I was able to access the problem web sites (that I mentioned in my original post) and run Jubula HTML tests using the Chrome AUT.


Regarding the --disable-web-security Chrome warning, it still appears when the Chrome AUT starts. I now believe that the warning message display is harmless for testing purposes, but I would like it to not appear in the web browser window when I am demonstrating Jubula tests. It tends to raise unnecessary questions from the audience. If there is a way to not use the --disable-web-security Chrome option, I would prefer that. Do Jubula users have the ability to modify the Selenium configuration that Jubula uses?
Re: Issues When Starting/Stopping Web Browser AUTs [message #1724376 is a reply to message #1724297] Tue, 23 February 2016 12:44 Go to previous message
Oliver Goetz is currently offline Oliver GoetzFriend
Messages: 219
Registered: May 2011
Senior Member
Hey,

I am able to reproduce the described behavior using IE11 ("When the IE AUT starts, the browser window tries to display content in a single frame and fails."). I am able to start FF 38.6 ESR but get a message right after starting the AUT ("We're Sorry - Firefox had a problem and crashed. We'll try to restore your tabs and windows when it restarts."). Unfortunately I don´t have access to the Chrome browser so I am not able to reproduce the issue using Chrome. I´ll ask the team for help.
Regards
Oliver
Previous Topic:Click succes - wrong
Next Topic:Link to download latest version of Jubula standalone
Goto Forum:
  


Current Time: Wed Feb 28 02:00:33 GMT 2024

Powered by FUDForum. Page generated in 0.02116 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top