WDI5 doesn't work correctly together with 3D model viewer

[MikhailDryk]

Describe the bug
After upgrading SAPUI5 version from 1.108 to 1.114 some specs which includes reusable component with 3D viewer go wrong.

All WDI5 locators end with an element search error after the reusable component with 3D viewer appears on the screen. As a result, the only way to locate elements is by searching through DOM elements.

I have investigated failed tests and saw that it go wrong in should navigate back to FLP step. After running all the tests, I found a common issue for all the failed tests – the 3D Viewer appeared on the screen

Added screenshots of failed tests
F3136_DigitalTwinQuery

F3136_DigitalTwinObjectReferences

F3136_DigitalTwinObjectDetails

I have already created the issue #449 related to this case before but without any updates

To Reproduce
Steps to reproduce the behavior:

1. Go to the application by link
2. Please, get in touch with me ([email protected]) to get creditionals to the application,
3. Clone repository
4. Execute in console command

$> wdio run wdio.perf.conf.js --spec ./test/specs/performance/<FILE NAME>.js --baseUrl=https://bigbuild-performance-copin.internal.cfapps.sap.hana.ondemand.com/ --params.pass=**** --params.user=**** 

I will provide --params.pass and --params.user

Expected behavior
All tests should complete successfully

Runtime Env (please complete the following information):

• wdio-ui5-service-version: ^1.5.1
• UI5 version: 1.114.1
• wdio-version (output of wdio --version): ^7.26.0
• node-version (output of node --version): 18.16.1
• OS: Linux
• Browser + Version chrome 114.0.5735.133

[vobu]

hi, thanks for the detailed error report! that makes evaluating the situation easier 👍
however, as you wrote in the opening paragraph: the failed tests seem to stem from upgrading UI5 from 1.108 to 1.114, not from wdi5 itself → your tests do work when the app bootstraps UI5 1.108, correct?
(also, internal SAP links are not accessible for us. there'll soon be commercial support available for wdi5, but we're not there yet)

[MikhailDryk]

Hello @vobu

I only see errors in tests with the 3D viewer after upgrading UI5 from 1.108 to 1.114. All other tests work as expected. I tried to add breakpoints to the code and saw that the control exists on the screen, but I wasn't able to access it using WDI5.

Tried to use it:

1. ❌ WDI5 locator This approach doesn't match any elements from screen

await browser.asControl({
			forceSelect: true,
			selector: {
				id: ID_LINK,
			},
		});

2. ✔️ DOM locator This approach match elements from screen

await $(`#${ID_LINK}`)

Also, as I mentioned, I have created ISSUE #449 which related to this problem

[dominikfeininger]

Hi, you are more than welcome to create an 3D model viewer example where this issue is reproduceable so we can investigate this issue.

[MikhailDryk]

Hello @dominikfeininger

Thanks for reply. Do you have access to the SAP environment? I can provide you login and password for the test user and you can check our 3D Viewer.

like this

[MikhailDryk]

Hello colleagues

Do you have any updates about my issue?

[vobu]

hi and sorry, currently all efforts go toward wdi5^2. Once this is done (hopefully mid next week), let's get back to your issue here. Thanks for your understanding!

[MikhailDryk]

Hello @vobu

Do you have any updates about my issue?

[vobu]

📫 "you have mail" 😸

[MikhailDryk]

Hello @vobu

Thanks for reply)

[github-actions]

hey 👋 - silence for 30 days 🤐 ... anybody? 😀

[github-actions]

closed 📴 because silencio 🤫 since an additional 14 days after staleness 📠

[MikhailDryk]

Hello (Volker)@vobu

Can we reopen this issue, because my issue wasn't fixed.

[github-actions]

hey 👋 - silence for 30 days 🤐 ... anybody? 😀

[github-actions]

closed 📴 because silencio 🤫 since an additional 14 days after staleness 📠