1

I have been struggling with this issue for some time and maybe someone from here has come across it and might provide me with any suggestions or solutions.

I have a fully working Test Framework with a Test Suite written in C#. All test are executed correctly on any local machine. When I log into VM where our Jenkins is set up, I am also able to run my Test Suite from the command line using nunit3-console.exe ... Now my hard time has started when I created a working Job in Jenkins which triggers my automation tests each time one of the development builds is done.

Each time when my Automation Jenkins Job is run, it finished as a failed run on the same test case over and over which is executed correctly either on the local machine or by command line.

The error message is always the same which is "unknown error: Element ... is not clickable at point (735, 91) . Another element would receive the click:..." I have tried to use explicit and implicit waits because I thought that maybe this is connected with some sort of a driver timeouts. Nothing really helped. I do not quite understand why this test case passed each time on local or run via command line on VM where Jenkins is but not when the Jenkins job is actually run.

Thank you for your time and answers,

2

When Selenium returns "Element is not clickable at the point" it usually means that the element is present on UI (in DOM) but it is covered with some other UI element that catches the click and handles it.

This could be a layout issue that might be caused by different screen sizes of the browsers when they run on your run and on Jenkin's run. So smaller size makes the elements overlap each other and thus the element that is on top intercept the action.

To troubleshoot I would recommend to introduce screen-shot saving on fail so that you can analyse how the user view looked like when failure happened.

  • Thank you for your reply Alexey R. I have thought about the same idea of implementing screen-shot saving in order to see how Jenkins triggers the execution, because as I said. When I run all test locally, they work fine, when I run all test on Jenkins machine via nunit3, they work fine as well. However, when Jenkins does the execution of them fails with the error message which I gave at the beginning. – Automation_Padawan Mar 21 '18 at 12:08
0

I think element is covered with some other element so not clickable hence execute the click via JavaScript.

WebElement element = driver.findElement(By.id("gbqfd"));
 JavascriptExecutor executor = (JavascriptExecutor)driver; 
  executor.executeScript("arguments[0].click();", element);

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.