I need to run my test cases in internet explorer 11 using protractor.When I execute test case,s it is consume much time when compare to Firefox and Chrome.
Even to enter the "Hello" text in text box it is taking 20 secs approximately.
Is there anyway to increase the execution speed in internet explorer 11?
Following are my protractor details:
Selenium standalone server-2.47.1
Node JS-0.12.7
IE driverversion-IEDriverServer_x64_2.45.0
Please provide the details and links if we have something to increase the speed.
Thanks much.
Try to use x32 version of the driver. It may help.
http://selenium-release.storage.googleapis.com/index.html?path=2.47/
Related
Does anyone know how to capture screenshot on Nokia 8110 4G (KaiOS)?
You may follow these steps to get screenshot via Firefox WebIDE.
On the device - dial *#*#33284#*#* to enable developer mode. There will be a bug icon on the status bar.
Download Firefox 58.
[Important] Disable your internet access, this is to prevent Firefox got updated to a newer version which might break the WebIDE functionality.
Launch Firefox 58 and disable auto update.
Resume your internet access.
Launch WebIDE in Tools > Web Developer > WebIDE.
Restart the WebIDE (because the ADB helper would be downloaded automatically, and need to restart it to take effect.)
Now you should be able to see Nokia 8110 detected under "USB devices" at the right panel. (if not, see below)
Click the device, "Nokia 8110", and then click Screenshot.
See here for a sample screenshot.
Troubleshooting if you failed to see Nokia 8110 detected:
I found it might fail if your Firefox got updated to a newer version automatically, in this case you might need to leverage creating new profile to start over again, see here for details.
If the Firefox version stays correctly at 58 but after you click the device, it shows an error saying "Failed to connect", try to reboot the phone and also restart the WebIDE as this post suggested.
EDIT: Yes it is - Joelbert W's answer worked and makes the other responses a bit silly by comparison, just * and # together :-)
Unfortunately, it is currently not possible :-(
https://twitter.com/KaiHelps/status/1072446931421593603
https://twitter.com/KaiHelps/with_replies
It is possible either with WebIDE connection or with a custom ROM such as GerdaOS where you can make screenshots by pressing Power with half-open slide lid.
However, I'd only recommend installing custom ROMs for experienced users only since you can't use any official updates after installing them.
So I have a go flip 3, and i stumbled on if u press * and # almost simultaneously, it takes a screenshot.
I believe it's possible on certain devices and OS versions using the Screen Capture API as well.
I have scripted selenium web driver.. It was working fine in IE9. I have upgraded to IE11. The sendkeys command is very in typing characters. It is entering one by one character and it is really slow.. I definitely did not make any change in the script. Only I upgraded the browser.. Is there any reason for this? Can any one know the resolution please let me know
Thanks
I had similar problem with my windows 8, IE11 and webdriver 64bit.
I swapped the 64 bit webdriver to the 32bit one and then the tests just went very fast. (fast response from send_keys which used to be 4-5 secs per key...)
Hope this helps.
I've been trying to get Internet Explorer 11 to run under Protractor to complete a suite of tests I have for an new AngularJS project.
I'm running under Windows 7 - 64 Bit and have downloaded and installed the Selenium IEDriverServer.exe for 64 Bit.
When I go to launch Protractor and run the scenarios, Internet Explorer comes up and navigates to the page just fine, but when the scenario sends keys to an input field it is extremely slow, like about 15 seconds between each key press. And Selenium is not showing any type of exception being thrown.
Has anyone seen this behavior before and found a solution?
Thanks
It's a known bug or "issue" (not a bug within the IEDriver however):
http://code.google.com/p/selenium/issues/detail?id=3072 (references IE10 but the point & solution is the same fundamentally)
It is explained in the Selenium issue tracker, but the workaround will be to use the 32bit version of the driver. Realistically you don't get "much" from using the explicit 64bit version.
I'd also say you may have further problems with IE11. Selenium doesn't support IE11 fully yet.
https://code.google.com/p/selenium/issues/detail?id=6437#c7 (among other issues)
You are probably, long term, better off downgrading to IE10 and using the 32bit driver.
I have implemented the following technology stack for automated unit testing in the browser.
Mocha -> Selenium -> Phantomjs
I followed this example:
http://net.tutsplus.com/tutorials/javascript-ajax/headless-functional-testing-with-selenium-and-phantomjs/
I suspect that there might be a bug in the "send keys" command between Selenium and PhantomJs. I do not have any experience in these 2 technologies, so I suspect it is rather me making some configuration mistake.
Basically what happens is that the characters sent by Selenium is not all applied by PhantomJs.
I switched PhantomJs out with Firefox and there it works like a charm.
The Selenium output for the 2 drivers are exactly the same. So I am left with suspecting a bug in PhantomJs or Ghostdriver. But as I said it might just be me not configuring the thing correctly. Given that this is quite a big issue I really suspect that is the case.
I am also not 100% sure where to log this, if this is indeed a bug.
There were a couple of issues with sendKeys fixed recently.
https://github.com/camme/webdriverjs/issues?page=1&state=closed
Are you running the latest version?
If not I would log a bug there about it.
I am running scripts using selenium version 2.29 and IEDriverServer.exe 64 on Internet explorer 8 and 9 both of them are 64 bit.
When I run these tests on firefox it takes around 2 min but in IE its takes around 20-40 min and they dont run at all sometime just get stuck. We use a windows server 2008 r2 and java jdk jdk1.7.0_11 64 bit version.
We by pass the initial certificates using
selenium.getWebDriver().navigate().to("javascript:document.getElementById('overridelink').click()");
Is there is way to make these tests faster. I even close the instance of IEDriverServer.exe everytime I close the browser.
Is there is a way to make my tests faster?
After hearing what is happening and outside of the spawning multiple instances (Thanks Lucas) the other thing that comes to mind as a culprit is what kind of locators you are using. Using Xpath slows IE way down, though the time difference is a bit extreme for that to be the only problem.
If you are using xpath, try switching to id or name locators. If your testing is anything like mine though, those aren't always available. If that is the case, CSS works better(faster) in IE instead of xpath.
Use 32 bit Version of IE driver and Run the test suite. it will work for Sure