Github Action integration with Katalon Studio 10.0.1 with no similar results

[amartinezalf]

Hi everybody,

I have purchased a KSE + KRE license pack and I´m trying to integrate my katalon analysis into github.

I have create the tests in Katalon Studio Enterprise 10.0.1 and execute in chrome browser of a windows machine. When I opened the html report it show that 9 test passed and 2 failed

Ok, perfect. Now I´m trying to get the same results in github using a windows machine, the same browser and the same katalon version.

But after the Github integration using this code to execute the katalon action:

 - name: Execute Test Suite Test
      uses: katalon-studio/katalon-studio-github-action@v4.0
      with:
         version: '10.0.1'
         projectPath: '${{ github.workspace }}'
         args: '-noSplash -retry=0 -browserType="Chrome" -testSuitePath="Test Suites/MX" -apiKey=  ${{ secrets.KATALON_API_KEY }} -executionProfile="QA_Mexico" --config -webui.autoUpdateDrivers=true'

This error is given:

Is not possible to use Katalon Studio Enterprise + Github Actions with version 10.0.1???

I Have read some posts like that - Katalon with Github Action integration and it said that “and also you need to use katalon with v9.6.0 on the github actions,
it will failed if you are using v9.7.3 or `v10.0.0”.

After reading that I have changed the katalon version in the Github Action to version: ‘9.6.0’

The execution went well, with errors but ok

but when I opened the Html report in order to compare the results with the katalon Studio, they are not what I was expecting. Only 3 Passed but 8 Failed

Could the katalon version has any influence on that?

Any Ideas to the same results on Katalon Studio Enterprise 10.0.1 and Github Action executions? because it is needed in order to validate all the tests

Thanks In advance

[kazurayam]

@amartinezalf

Only 3 Passed but 8 Failed

Have you tried to identify the reason why the 8 test cases failed?

Have you checked the error logs of the failed test cases?

Could you show us the source of the failed tests and the full error logs of the failed tests?

Unless you provide us enough information, the guys in this forum won’t be able to guess anything.

[amartinezalf]

Hi! @kazurayam,
You are right, in order to understand what is the problem is needed to show some logs.

I have been gathering all the errors, and it seems that there are problems with the HTML page. I have focused on Tests 1, 4, 5, 6, and 7, and these are the errors.

I will show you only one screenshot for Test Case 1: Test Cases/Mexico/1 - SP ASPI Pep Test, but for the rest, I will copy and paste the error and cause to avoid making the post too long.

1: Test Cases/Mexico/1 - SP ASPI Pep

Unable to click on object ‘Object Repository/Page_Solicitud de pedido/bdi_Verificar’ (Root
cause: com.kms.katalon.core.exception.StepFailedException: Unable to click on object ‘Object Repository/Page_Solicitud de pedido/bdi_Verificar’
…
…
Caused by: org.openqa.selenium.StaleElementReferenceException: stale element reference: stale element not found in the current frame

4: Test Cases/Mexico/4 - SP ASPM Pep

Unable to click on object ‘Object Repository/Page_Solicitud de pedido/bdi_Verificar’ (Root cause: com.kms.katalon.core.exception.StepFailedException: Unable to click on object ‘Object Repository/Page_Solicitud de pedido/bdi_Verificar’
…
…
Caused by: org.openqa.selenium.StaleElementReferenceException: stale element reference: stale element not found in the current frame

5: Test Cases/Mexico/5 - SP ASMI CeCo

Unable to wait for object ‘Object Repository/Page_Solicitud a Compras/bdi_Crear’ to be clickable (Root cause: com.kms.katalon.core.exception.StepFailedException: Unable to wait for object ‘Object Repository/Page_Solicitud a Compras/bdi_Crear’ to be clickable
…
…
Caused by: org.openqa.selenium.StaleElementReferenceException: stale element reference: stale element not found in the current frame

6: Test Cases/Mexico/6 - SP ASMI Pep

Unable to wait for object ‘Object Repository/Page_Solicitud de pedido/bdi_Verificar’ to be clickable (Root cause: com.kms.katalon.core.exception.StepFailedException: Unable to wait for object ‘Object Repository/Page_Solicitud de pedido/bdi_Verificar’ to be clickable
…
…
Caused by: org.openqa.selenium.StaleElementReferenceException: stale element reference: stale element not found in the current frame

7: Test Cases/Mexico/7 - PC ref contrato

Unable to click on object ‘Object Repository/Page_Ordine rif. Contratto/chechbox_ItemTable’ (Root cause: com.kms.katalon.core.exception.StepFailedException: Unable to click on object ‘Object Repository/Page_Ordine rif. Contratto/chechbox_ItemTable’
…
…
Caused by: org.openqa.selenium.ElementClickInterceptedException: element click intercepted: Element <div class=“sapMRbB sapMRbHoverable”>…</div> is not clickable at point (49, 333). Other element would receive the click: <span id=“com.abertis.mm.zpowithcontract::sap.suite.ui.generic.template.ListReport.view.ListReport::ZC_PosContractLR–listReport-Group-header-inner”>…</span>

8: Test Cases/Mexico/8 - Recep Materiales

Unable to click on object ‘Object Repository/Page_Entrada de Mercancias/bdi_Crear entrada de mercancas’ (Root cause: com.kms.katalon.core.exception.StepFailedException: Unable to click on object ‘Object Repository/Page_Entrada de Mercancias/bdi_Crear entrada de mercancas’

…
…
Caused by: org.openqa.selenium.ElementNotInteractableException: element not interactable

It seems that there are some problems loading the html or something, I would like to know if someone has had the same problems with github actions.

thanks in advance.

[kazurayam]

@amartinezalf

org.openqa.selenium.StaleElementReferenceException

Ah, you got the StaleElementReferenceException!
It is notorious.
It is very hard to debug.
Even more difficult to remotely diagnoze what’s wrong.

---

All I can do now is to point you to the following URL:

Microsoft Account Login Procedure tricks Katalon WebUI.click keyword

Sample codes are published in Problem to solve In the Katalon Community forum, there was a topic “Stale element not found, is this relate to using same Object?” originated by jirayu.s in Sep 2023. He wanted to develop a Test Case script in Katalon Studio that automates the login procedure in to Microsoft Account. Microsoft 365, Microsoft OneDrive, Azure DevOps — these services require you to have a “Microsoft Account”. Everytime you use those cloud services, you need to pass the login pro…

In this post, I descrbied a case where I encountered the StaleElementReferenceException caused by WebUI.click keyword, like you.

In my case I encountered a difficulty while my test script tried to interact with the Microsoft Account Login processing. If you trying to do the same, I believe it is highly likely you get the same insident.

I looked into the target HTML of Microsoft Account Loging processing in detail and struggle a lot to find out a way to prevent the StaleElementReferenceException. In the end I could find out a workaround. If you read this report, you would find how difficult it is to resolve a StaleElementReferenceException issue. I believe you need to change your test case script somehow, but I don’t think I can help you much remotely.

[kazurayam]

@amartinezalf

org.openqa.selenium.ElementClickInterceptedException

@amartinezalf

org.openqa.selenium.ElementNotInteractableException:

These exceptions are common. Please search this forum to find previous posts concerning these Exceptions. There are lots.

@grylion54 may say something…

[grylion54]

Now we would need to examine your test case code, to see if you have lots of wait statements before a page change, before elements become visible (especially if they were hidden beforehand). Additionally, if you are getting an “ElementNotInteractableException”, it may be because you haven’t wait-ed for it to be ready, or due to how the object is within the HTML.
So, do you have WebUI.waitForPageLoad(10) while you are changing pages?
Do you have WebUI.waitForElementVisible(yourTestObject, 10) when needed?

It looks like you have some WebUI.waitForElementClickable(), perhaps you can add WebUI.waitForElementVisible() to see if this slows your test down. I have instances where WebUI.waitForElementClickable() goes instantaneous whereas WebUI.waitForElementVisible() takes the full 2 seconds of my timeOut. The Clickable often has issues (it doesn’t select the drop-down), whereas the Visible passes all the time.

Edit: with the error message:

ElementClickInterceptedException: element click intercepted: Element <div class=“sapMRbB sapMRbHoverable”>… is not clickable at point (49, 333). Other element would receive the click:

For this, you may need to try WebUI.enhancedClick() to see if that will work or just use a javascript “click” because of the <span> at <span id=“com.abertis.mm.zpowithcontract::sap.suite.ui.generic.template.ListReport.view.ListReport::ZC_PosContractLR–listReport-Group-header-inner”>…</span>

[amartinezalf]

Thanks @kazurayam and @grylion54 for your responses with several options and alternatives. I’m in charge of GitHub Actions integration, and I’ll share this information with the QA team so they can explore the different alternatives. We might even be able to share some code.

We’ll keep in touch.

Thanks.