java - WebDriver PhantomJS Unable to find element, but works fine with Firefox -

-

I have been ringing my head in the wall for a long time, so I thought I would ask "experts" why down Code will not work with PhantmJs (entering password), but works fine with Firefox. The most upsetting thing is that a field entry (username) is successful, but no one else will work. Page load is fine and I've included a test code to verify other components. Has been properly loaded.

Look at the code below: 

  import java.io.File; Import org.openqa.selenium *; Import org.openqa.selenium.firefox.FirefoxDriver; Import org.openqa.selenium.phantomjs.PhantomJSDriver; Public class login {public static zero main (string [] args) {WebDriver driver; Boolean verbose = false; // Change it to the right to test with Firefox string fontpath = "../phantomjs-1.9.8-linux-i686/bin/phantomjs"; String url = "https://www.britishairways.com/travel/redeem/execclub/_gf/en_us"; If (verbose) {driver = new firefox driver (); } Other {file file = new file (phantom); String UserEgent = "Mozilla / 5.0 (Windows; U; Windows NT 5.1; CS; RV: 1.9.0.8) Gecko / 200 9 032609 Firefox / 3.0.8"; System.setProperty ("phantomjs.binary.path", file.getAbsolutePath ()); System.setProperty ("phantomjs.page.settings.userAgent", User Agent); Driver = new funmzsdriver (); } Driver.get (url); Try {Driver.findElement (By.id ("membership number")). SendKeys ("1234"); System.out.println ("ID input successful"); If (driver.findElement (By.id ("ecuserlogbutton") isDisplayed ()) {System.out.println ("login button exists"); } // This is where it fails with the PhantomJS, but works with the Firefox driver.Fed Element (by.cssSelector ("# pintr> #password")). SendKeys ("1234"); System.out.println ("Password input successful"); } Hold (exception e) {System.out.print (e.getMessage ()); } Driver.close (); }}

There is a problem with element ID in PhantomJS 1.x The site is broken , Because it uses password for two elements on the page that should never be. By changing the ID in the selector with just the element type ( input ), it is resolved. 

  driver.findElement (by.cssSelector ("#pintr"; input ")) .sendKeys (" 1234 ");

Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more