I developed my test automation using IEDriverServer 2.25.0 and C# on my machine running XP, and IE7. Everything works fine. I created a setup package of my solution and deployed into another machine (Windows7, IE8), and the webdriver cannot find the elements on my tested webpage.
I installed Visual Studio and C# in another XP, IE7 machine. When I run the code, it has the same problem as in the Windows7 machine.
I tried to set the protection mode to on/off on all zones, but it does not work either.
I'm wondering if there is any settings Firewall/Antivirus/etc... that is making the webdriver not able to find the web elements??
Thanks!
I found the problem. My test machine should be in the same network as the webserver. The IP Address of my webserver is 10.104.200.110 with mask 255.255.255.0. Although my test machine can surf the webserver, it had a different IP address. So I changed the IP to 10.104.200.100 with mask 255.255.255.0 and it worked!
I had an issue with IE7, I mean I thought this is only IE7 issue since on IE6, IE8, IE9 the web page I have to test was working fine.
The web page has broken certificate (because this is R&D environment).
The soution was to add the page address to trusted sites.
I hope this helps someone, because I was looking everywhere and didn't find anything.
Now it seems obvious but nothing indicated that the problem was because of that, google page was working ok but the page I should test did not.
Related
Browserstack has discontinued its chrome extension for local app testing and has moved to a desktop app/.exe that you have to download to do local testing.
I can't seem to get this working running Windows 10 and I'm wondering if anyone else has had this problem and resolved it.
When I download and execute their desktop app, it tells me local testing is enabled:
https://imgur.com/a/2ey7N3U
When I then use Browserstack Live to test local development I get an error message saying local testing is not enabled and it gives me the option to download their desktop app, which I have and says local testing is enabled:
https://imgur.com/a/YMd0LOj
I have tried uninstalling and reinstalling the desktop app/.exe, it gives me the same results.
I've confirmed with our network team that I am not behind a proxy which is an option to manage the desktop app (under "advanced settings" in the first screenshot above).
Our network team has also whitelisted all traffic from (asterisk).browserstack.com (the actual asterisk character is stripped here) and they're telling me "Additionally I watched his traffic on the firewall as he tried to use the browserstack software and no traffic was blocked
I've also been in contact with browserstack support but have basically been feeding their responses to our network team and our network team's responses back to browserstack. At the end of the day, I still can't get local testing working.
Does anyone have any ideas what might be happening and how I can resolve it?
I encountered the same behavior while setting up Local Testing with the BrowserStack Local Desktop app that was released after the announcement by Google about the end of support for Chrome apps (Click here). However, I was able to set-up Local Testing post configuring the proxy server details as mentioned over here.
I would suggest checking with your IT team if traffic for *.browserstack.com is being routed via a specific proxy at your end and configuring the proxy details in the 'Advanced Settings' for the desktop app.
In case this doesn't work, do contact BrowserStack Support
I can not figure this out, I've been writing web sites for a while now and never ran into anything like this. I am debugging a .Net MVC web application and trying to get to it in Internet Explorer 11. When I type in http://localhost:4718 or localhost:4718 I get the error
"No apps are installed to open this type of link(localhost)"
I am positive port 4718 is what I want it works in every other browser . This is just an IE 11 with Windows 8 thing that I can not figure out. I saw in another question to disable "Enable Enhanced Protection Mode" in advanced settings. This did not help
Typing localhost:4718 makes IE think that you're trying to open a protocol that is coincidentally named localhost. Thus you should always use the longer form http://localhost:4718/ or at least //localhost:4718/.
You absolutely shouldn't be seeing the same error for the full URL; if you are, go to a command prompt and type ping localhost and copy its results in your question.
I have to test a aspx web application with IE10; my problem is that I have a Windows 2003 server machine.
Is there any way to simulate the behavior IE10 on this kind of machine ?
I tried IETester but it doesn't allow me to run IE10.
Can be assumed that IE10 behaves similarly to some Chrome version ?
Can you please give me a hint
Thanks a lot
Marco
You could install IE10 in any other client, and test, rather than installing the browser in the server directly.
Alternatively, if you want to test for different versions of IE, you could check out Browserstack
Are there any particular settings one should optimally enable/disable/tweak when doing ASP.Net MVC development on local test machine Windows 7 using IIS 7.5 and moving in and out the debugger & recompiling refrequnetly (integration/troubleshooting stage now before TDD fantactics throw stones - although admittedly I could have more under test), I work with 64 bit edition but figure this probably applicable at both x86/x64?
I'll start with one:
Ping Period (seconds) - increase from 90 to 3000 (or something somewhat higher) so you can if unfortunately need to a good bit of time whilst debugging or disable ping on local test machine.
Credit: http://blogs.msdn.com/johan/archive/2007/09/12/my-web-application-times-out-when-debugging-in-iis7.aspx
However I see over stuff such as:
Disable Overlapped Recycle & Recycling settings etc.. that I wonder if could increase performance or make debugging less friction
Question prompted by the annoyance that I've ran across a few recent debugging issues (not apparent in production) including a random, and tempormental error "An assembly with the same simple name blah-blah-lah-assembly-definiton has already been imported . Try removing one of the references or sign them to enable side-by-side." (iisreset resovles) and generally slow debugging attaching. The points and answers to this question need not help with the above (I believe it may be related to spark view engine as that where the stacktrace ends) but figure it worth mentioning incase someone has a direct suggestion *
quick tip: if you're experiencing slow response times (~1-1.5 sec) from browsers other than internet explorer (eg: firefox, chrome, safari) while running your mvc/ other web app on your local machine using win7/vista, it is due to dns resolution with ipv6.
firefox solution: disable ipv6 in about:config (boolean cfg 'network.dns.disableIPv6')
machine wide soft solution: uncomment the good old localhost address in the hosts file (%WINDIR%\System32\drivers\etc\hosts):
# localhost name resolution is handled within DNS itself.
127.0.0.1 localhost
# ::1 localhost
machine wide hard solution: disable ipv6 completely
credit goes to this blogpost: http://weblogs.asp.net/dwahlin/archive/2007/06/17/fixing-firefox-slowness-with-localhost-on-vista.aspx
Embarcadero guys just published a fresh article on similar topic for Delphi Prism (aka Delphi for .NET), so why not take a look on their suggestions?
http://edn.embarcadero.com/article/40108
From the experience i have working with asp.net mvc, i can tell that there are no special settings for IIS 7 or IIS 7.5 for working on asp.net mvc projects. It works fine in the default form, you just need to create a new website and point it to the folder that has the files for you application.
For debugger if you ask, you can simply put a breakpoint in the code and hit that breakpoint when you run the application from visual studio. But by default the application will use the development web server that fires up when you run a web application from visual studio. If you want to the application to run using the IIS installed on your system you will have to change the project settings. See here for a screen shot of how to do so
http://blogs.bootcampedu.com/blog/post/Debugging-aspnet-mvc-application-using-IIS.aspx
Additionally you can also use System.Diagnostics.Debugger.Break(); for putting a break point in the code.
If you only want to debug your application, I recommend to use the built-in development server of Visual Studio.
If you debugged the most of it or want to do that on IIS, I recommend you the Ctrl+Alt+P shortcut, which enables you to attach a debugger. Select w3wp.exe and you can debug with IIS.
When I yesterday returned to Visual Web Developer I was no longer able to run/debug my projects. Clicking the green play button launches ASP.NET Development Server (and it shows up in the systray) but the browser only shows the error message "Firefox is not able to connect to localhost:58127" (translated from Swedish). IE7 says "Cannot show web page".
I cannot figure out why this happens. It worked a couple of weeks back. Could there be a Windows setting that mess things up? (I've tried to disable the firewall without any change.)
Are you using Vista? I've had the same issues with recent Vista updates.
Firstly, make sure Visual Studio is running "As Administrator".
Secondly, when the browser launches, replace "http://localhost:" with "http://127.0.0.1:". If that works, then its because a Windows Update messed up your hosts file.
If this is the case, make sure you hosts file has this line in it, uncommented: "127.0.0.1 localhost"
my hosts file is in this directory: "C:\Windows\System32\drivers\etc"
yours will be something similar to that.
Are you perhaps using NOD32 or any other antivirus that may cause problems?
I encountered this issue today and just wanted to elaborate because my hosts file had "127.0.0.1 localhost" already defined.
I was able to see the default IIS site by referencing localhost but when I tried debugging in my IDE it would always display "cannot display webpage" in IE and "Oops! Google Chrome cannot connect to localhost" in Chrome.
I opened a command prompt and typed "netstat -a" and reviewed the results. I saw that my port used by my debugging web server was listed as "LISTENING" on the local address of [::1] only:
TCP [::1]:64212 [ComputerName]:0 LISTENING
What's unusual to me is that debugging worked for a period of time and then it seemed like all of a sudden it stopped. The first couple times it happened I re-installed Visual Web Developer Express 2010. This became rather annoying because it was a long process and the problem continued to resurface after what seemed to be an arbitrary period of time.
This latest time I changed my hosts file to include "::1 localhost" (the opposite of this solution and numerous others I found online) and that has resolved my issues with my debugging environment.
I'm grateful this resolved my issue but am still curious as to why and how my debugging environment seems to change. Additionally, I'm curious why there are multiple loopback addresses other than 127.0.0.1. Is "::1" an ip6 standard? If so, shouldn't localhost be routing to 127.0.0.1 and interpreted by the tcp/ip stack as the same as ::1?
I had this problem with Visual Studio 2013. I have set the Firewall system manually. This means that, at the time of communication by programs Firewall notify me. Incorrectly linked to "devenv.exe" was blocked by the Firewall. Correct mode of communication "devenv.exe" will solve the problem. in your case cheeck Firewall options and filtered communications.