[syncope-dev] Issue 160 in syncope: selenium tests fail on windows

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[syncope-dev] Issue 160 in syncope: selenium tests fail on windows

syncope
Status: Accepted
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 160 by [hidden email]: selenium tests fail on windows
http://code.google.com/p/syncope/issues/detail?id=160

What steps will reproduce the problem?
1. Use Windows
2. Run mvn verify -Pselenium

What is the expected output? What do you see instead?
One would expect Firefox to be started, however, due to the  
setUp-construction of AbstractTest, it is Internet Explorer that is started.
Moreover, the selenium tests fail in IE (random js-errors being thrown).

If I understand the Selenium code correctly, you should provide a host and  
a browser-string to the super.setUp(x, y) method, instead of instantiating  
a DefaultSelenium.
Please find attached a proposed fix for this. This fixes the problems in  
Windows (for me at least).

Could other developers test this on other platforms to see whether it  
doesn't break things there?
(or perhaps configure a headless test in Jenkins for the selenium tests?)

Attachments:
        selenium-windows.patch  619 bytes

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[syncope-dev] Re: Issue 160 in syncope: selenium tests fail on windows

syncope
Updates:
        Status: Started
        Owner: [hidden email]

Comment #1 on issue 160 by [hidden email]: selenium tests fail on  
windows
http://code.google.com/p/syncope/issues/detail?id=160

(No comment was entered for this change.)

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[syncope-dev] Re: Issue 160 in syncope: selenium tests fail on windows

syncope
Updates:
        Status: Fixed

Comment #2 on issue 160 by [hidden email]: selenium tests fail on  
windows
http://code.google.com/p/syncope/issues/detail?id=160

This issue was closed by revision r1168.

Loading...