We have existing selenium tests in many projects but these were turned off
due to problems running selenium on the server. Selenium has been updated
a few times since then but it may be that the underlying problem is that
we were continually re-launching firefox.
i want to know if there is any other browser which i can keep running at backend and no need to open every time which sometime slow the server and at worse hang it.
please suggest some solutions.
Related
I have a simple C# Windows Forms application I'm trying to create. on Form1_Load I query my database with a simple request to fill a DataGridView.
If I debug the application, the query executes immediately without issue.
If I "Start without debugging," the connection to the database times out every time with SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
This is affecting multiple different projects which used to work flawlessly before today, so I'm pretty certain it's an issue with Visual Studio and not my code. Here's hoping someone knows what could be causing this.
After a fresh install of VS2008 on a new machine, I'm still experiencing the issue. I was able to run the project without debugging, and the first time connecting to the database worked fine, but now it always fails as described above. Possibly some kind of weird connection pool issue in VS?
Check your antivirus software.
My antivirus was flagging every new application I tried to run without debugging, but I had alerts for my antivirus turned off so I had no idea.
I turned on alerts and suddenly when I ran my app I got a notice from my antivirus. I just allowed it permanently and now everything runs smoothly.
Has anyone seen the issue when debugging an Asp.Net 5 (core) application where the application seems to just go to sleep. Selecting another function/page in the browser just says "Waiting for LocalHost" (as I am running it locally on IIS Express).
We have a staged version of the Asp.Net app and it has no such problem. It runs wonderfully, but in Debug mode, it can have serious delay issues in executing code. Nothing is reported in the output window, during the time it appears to be doing nothing. Nothing on the Diagnostic tools windows either
A lot of the time - it will ultimately come back if you let it do its thing. But sometimes it can take up to 15-30 seconds.
The issue seems to become more prevalent when you change the Razor or javascript client files while the app is running?
Soemtimes pressing F5 on the web page makes it get out of its sleep mode (but not always, and it seems the more times you do this it, the slower it gets). Is it perhaps rebuilding the page that changed? but why the delay?
Again this works fine in Staging or Production (as none of the back end client side files would be changing). But it can be very annoying
Any ideas?
For me it was my Anti Virus. As soon as I disable AVG all requests get immediately run by the debugger.
So I found I didn't have the web tool extensions even installed - and after I installed it - the Freeze disappeared, but a colleague of mine still has the problem (as he already had the extension loaded and there is no way to uninstall it once its loaded
I'm running an automated test in Firefox browser using Selenium Web Driver and TestNG, but I'm encountering this error:
org.openqa.selenium.internal.seleniumemulation.WaitForPageToLoad handleSeleneseCommand
WARNING: Cannot determine whether page supports ready state. Abandoning wait.
This has only recently been occurring, so I think it might have to do with Firefox updates. Does anyone know what might be causing this issue?
I am currently writing features to upload an image using the file exploer in ie.
Locally this works fine and opens the file explorer and locates the image without any problems. However when i run it as part of the acceptance run ont he server it self it fails to open the file explorer, It will just sit there waiting for it, it doesnt even time out at the usual 60 seconds so i assume something is trying to happen behind the scenes but is failing silently.
Has anyone had this issue and found a fix or work around for it?
Most servers have IE very locked down by default since very little browsing is typically done from servers, and the browser itself represents a significant attack surface. See here for more info http://msdn.microsoft.com/en-us/library/ms537180(v=vs.85).aspx
The result is that unless you disable this enhanced security there are a number of things that just flat out won't work. If you are running your test from the same server where the website is installed, then you will need to disable all the enhanced security stuff on IE.
This would be a violation of best practices for a production system, but is an understandable expedient for a test system as an alternative to having a pair of systems with different OS's (client and server) for your testbed and running the tests on the client. (more realistic, but requires another system or VM be created and maintained)
Does anybody have any idea why Selenium RC server takes a long time to run tests? A simple test of just opening a webpage (php) and asserting the title takes an unforgiving 4 minutes!
The tests are being run on Ubuntu server and using headless (XFrame Buffer) Selenium RC server. Does the fact that XFrame Buffer is being used make a difference?
Another alternate to this problem is to use "Selenium" bundled within the PHPUnit package.
i have currently moved my code from using Testing_Selenium package to using selenium interface within PHPUnit.
I had a similar problem. Downgrading Testing_Selenium to 0.4.3 from 0.4.4 helped.
Is the web page local or remote? The simplest answer could be that you're connecting to a slow host, or the connection between client and server is slow.
Can you provide any more details about the server configuration that's running RC? As far as I have read Xfvb should be faster.
There's something about your environment that's causing this. We run a suite of about 700 tests several times a day, and most of the (sometimes very complex) tests complete in under 30 seconds. Our environment is Windows running in an EC2 virtual machine with everything on the same machine - database, browser, appserver, test scripts, and Selenium. We avoid some network delays that way, but the flip side is that we have heavy CPU and memory pressure.