Open metzing opened 1 month ago
I was able to come up with a workaround: you can set the writeToDom
property of the CustomData to true
and access its value using control.$().getAttribute()
(https://webdriver.io/docs/api/element/getAttribute).
hey 👋 - silence for 30 days 🤐 ... anybody? 😀
Describe the bug I'm writing an E2E test for an application with complex data binding, based on 3 keys (currently). I want to verify that the right cell in the TreeTable receives the right text.
To access the three keys of the cell without scraping the UI, CustomData is added in the productive code, exposing their values. Reading this works as expected in OPA5 using the
check
function:Now I'm trying to achieve a similar verification in WDI5 as a higher-level smoke test, but the CustomData controls don't get initialised:
Expected behavior When I receive the result of
await control.getCustomData()
I expect that I can interact with the custom data objects.Logs/Console Output
Screenshots![image](https://github.com/ui5-community/wdi5/assets/20574874/a344c494-5139-423f-8dfc-d916fc2d9b47)
Runtime Env (please complete the following information):
wdi5/wdio-ui5-service
-version: 2.0.7UI5
version: 1.120.7wdio
-version (output ofwdio --version
): 8.36.1node
-version (output ofnode --version
): v20.12.2