How to solve Selenium error Element is not clickable at point (x, y) Other element would receive the click

The error message looks like this:

Solution:
The clickable element is not ready, it might not be visible or clickable.
Sometimes the element is covered by another html element. (hide the covering element first).

Steps:
1. Wait for element to be visible
2. Wait for element to be clickable
3. Click with javascript

If this still this doesn’t work insert an implicit wait between step 1 and 2. (Thread.Sleep() in c#)

C# driver code to solve problems:
Wait for element to be visible and clickable (ElementToBeClickable = element is visible AND enabled.)

Click with javascript:

 

How to Increase build agent execution time? (VSTS)

When running long running tests (perhaps UI tests with Selenium)
I got this error:

The job running on agent xAgentNamex has exceeded the maximum execution time of 01:00:00.

The default timeout for VSTS Agent is 60 minutes.
The solution was to increase Build job timeout in minutes, under settings of build definition in the VSTS dashboard.

Solution found here:
Source: tfsbuild – How to Increase build vnext build agent execution time? – Stack Overflow

Problem with remote Selenium IE driver “Unable to find element with css selector”

Running my Selenium tests locally against IE11 works fine, but when calling remote Selenium server running the same browser and Selenium drivers setup I get this:

The problem is connected to the fact that the IEDriverServer.exe runs the server IE11 version. In my case this is a Windows Server 2016 which has a higher security restriction.

For me the solution was to disable the Internet Explorer Enhanced Security Configuration. Follow this guide for the Windows Server 2016 version.

Disable Internet Explorer Enhanced Security Configuration in Windows Server 2016

The same error could also be caused by javascript not enabled for the driver:

or need driver to switch to the correct frame/window

More info here:
https://github.com/SeleniumHQ/selenium/issues/3611

.net – NUnit 3.2.1 + TeamCity: Could not load file or assembly ‘nunit.framework’ – Stack Overflow

21 down vote I had the same problem with TeamCity 10.0.1 (build 42078) and NUnit 3.4.1. And it turned out to be completely my fault. I’m posting it here as someone else can stumble into the same problem and this can save them some time. It turned out that the problem was in the “Run tests from: ” setting in my build configuration. I had **\*.Test.dll. That was accidentally picking up dlls for \obj\**\ directories (where there is no nunit.framework.dll present). Once I changed the setting to **\bin\%Bui

Source: .net – NUnit 3.2.1 + TeamCity: Could not load file or assembly ‘nunit.framework’ – Stack Overflow

Error when starting EPiServer 7.5+ site on server environments – Could not load file or assembly ‘JetBrains.Annotations, Version=

[FileNotFoundException: Could not load file or assembly ‘JetBrains.Annotations, Version=8.0.5.0, Culture=neutral, PublicKeyToken=1010a0d8d6380325’ or one of its dependencies. The system cannot find the file specified.] EPiServer.Framework.Initialization.InitializationModule.Initialize(HostType hostType) +1508 EPiServer.Framework.Initialization.InitializationModule.FrameworkInitialization(HostType hostType) +84 EPiServer.Global..ctor() +91 ASP.global_asax..ctor() +9

The workaround is to include the JetBrains.Annotations.dll in the bin folder of the application. 

Use Nuget package manager console to install the exact version missing. Select the Web project as the default project (to install into that project) in Package Manager Console and enter this command:

The above is for version 9.1.1.0, for more info regarding downloading old versions of nuget packages, see this link:
http://stackoverflow.com/questions/5628689/download-old-version-of-package-with-nuget

Read more here: Error when starting ASP.NET website – Language Agents / .NET Agent – New Relic Community Forum

Log4net not logging fix – asp.net mvc – Application does not log – Stack Overflow

How to track down log4net problems:
http://stackoverflow.com/questions/756125/how-to-track-down-log4net-problems

My web application is an ASP.NET MVC one with a separate log4net.config file in the web root. After a lot of googling and hair-pulling I resorted to initializing log4net through code in Application_Start (in Global.asax): protected void Application_Start() { var logConfigFilePath = Server.MapPath(“~/log4net.config”); log4net.Config.XmlConfigurator.ConfigureAndWatch(new System.IO.FileInfo(logConfigFilePath)); } This solved the problem for me and log4net started logging correctly.

Source: asp.net mvc – Application does not log – Stack Overflow

Error “Exception has been thrown by the target of an invocation” when trying to connect to TFS / show team explorer in vs 2013

Problems with error “Exception has been thrown by the target of an invocation” when trying to connect to TFS / show team explorer window in Visual Studio 2013?

Solved by downloading and reinstalling Team Explorer 2013:
Download Team Explorer for Microsoft Visual Studio 2013 from Official Microsoft Download Center.

You can find more info on errors in Visual Studio 2013 in this logfile:
%userprofile%\AppData\Roaming\Microsoft\VisualStudio\12.0\ActivityLog.xml