Test case failing while trying to run it from suit level, while same test case running fine

Archive
,
#1

Hi i have created more than 50 test case through recording mod, and while trying to run all the test cases from a suit level every test case is running fine but one test case getting fail, and showing error that “element is not clickable” but if same test case i am running single its working fine, however the test case is very simple just need to click on link that is navigating to other site.
I am not able to find any reason for that why its not working on suit level.

I would thankful if any one can help me to resolve this issue.

Thanks,

#2

Did you try to prove that the element (link) is present and visible?

https://docs.katalon.com/display/KD/[WebUI]+Verify+Element+Present

https://docs.katalon.com/display/KD/[WebUI]+Verify+Element+Visible

https://docs.katalon.com/display/KD/[WebUI]+Verify+Element+Clickable

If all of these “pass”, and the click still fails, there must be something else wrong.

#3

Russ Thomas said:

Did you try to prove that the element (link) is present and visible?

https://docs.katalon.com/display/KD/[WebUI]+Verify+Element+Present

https://docs.katalon.com/display/KD/[WebUI]+Verify+Element+Visible

https://docs.katalon.com/display/KD/[WebUI]+Verify+Element+Clickable

If all of these “pass”, and the click still fails, there must be something else wrong.

Thanks…Russ for suggestion, i have tried all but still issue occurs…

#4

What is the error?

#5

Russ Thomas said:

What is the error?

Hi Russ following are the error i am getting, i am surprised it is running fine in stand alone but only fails at suit level

est Cases/Links/CustomerPage_Links/Calculators/FinancialCalculators FAILED because (of) Unable to click on object ‘Object Repository/FinanceCalculators/Page_1517229621680/a_How much vehicle can I affor’ (Root cause: org.openqa.selenium.WebDriverException: unknown error: Element … is not clickable at point (520, 161). Other element would receive the click:

(Session info: chrome=64.0.3282.167)

(Driver info: chromedriver=2.33.506120 (e3e53437346286c0bc2d2dc9aa4915ba81d9023f),platform=Windows NT 6.1.7601 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)

Command duration or timeout: 0 milliseconds

Build info: version: ‘3.7.1’, revision: ‘8a0099a’, time: ‘2017-11-06T21:07:36.161Z’

System info: host: ‘CHETUIWK313’, ip: ‘172.16.4.119’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_102’

Driver info: com.kms.katalon.selenium.driver.CChromeDriver

Capabilities {acceptSslCerts: true, applicationCacheEnabled: false, browserConnectionEnabled: false, browserName: chrome, chrome: {chromedriverVersion: 2.33.506120 (e3e53437346286…, userDataDir: C:\Users\manisht\AppData\Lo…}, cssSelectorsEnabled: true, databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false, javascriptEnabled: true, locationContextEnabled: true, mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: XP, platformName: XP, rotatable: false, setWindowRect: true, takesHeapSnapshot: true, takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: , version: 64.0.3282.167, webStorageEnabled: true}

Session ID: 76ab127c319b068ffdfd882309c38370)

#6

have same issue…

#7

@penny peng
http://forum.katalon.com/discussion/1736/unable-to-click-on-object-other-element-would-receive-click

#8

@Mate Mrse,
Thanks, but my problem is the test case pass when executed from test case level, but failed when executed from test suit level.

#9

Hi guys,

These inconsistencies occur during test suites sometimes, or at least I have found that this is the case.

As a workaround, I have used the retry failed tests within the execution information in the test suit options. It will then run the failed test suits 3 times and if they still fail then you are sure that there is a problem.

If this does not work then it could be because of the test case before the failing test case.

#10

@Russ_Thomas
Hi, I am also facing the problem in which test case fail at test suite level while it is working fine at test case level.
One object is not identifiable at test suite level.

#11