Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I can't find the element using browser.asControl function #449

Closed
MikhailDryk opened this issue Apr 6, 2023 · 7 comments
Closed

I can't find the element using browser.asControl function #449

MikhailDryk opened this issue Apr 6, 2023 · 7 comments
Labels

Comments

@MikhailDryk
Copy link

Describe the bug

While I was writing tests to the one of our application Digital Twin

I faced an issue, that I am not able to find control by launching browser.as Control function.

Just below, I will give a couple of examples of how I tried to find SAPUI5 control (I highlighted on the screenshot)
image
using different selectors:

  1. I tried to find it by ID + controlType + viewName
    image
  2. I tried to find it by controlType + ancestor
    image

I show you one of several UI5 elements which I don't find in application.

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. After logging in and clicking the link, you will see the same application shown in the screenshot.

Expected behavior
I wanted to be able to find UI5 controls using the browser.asControl function.

Runtime Env (please complete the following information):

  • wdi5/wdio-ui5-service-version: [^0.9.15]
  • UI5 version: [1.108.4]
  • wdio-cli-version: [ 7.26.0]
  • node-version (output of node --version): [18.14.0]
  • OS: [Windows 10 Enterprise]
  • Browser + Version [chrome 111.0.5563.111]
@Siolto
Copy link
Collaborator

Siolto commented Apr 6, 2023

Hi @MikhailDryk,

did you already tried to use the Test Recorder to identify the controls? There is a also a special dialect for wdi5.

@MikhailDryk
Copy link
Author

Hi @MikhailDryk,

did you already tried to use the Test Recorder to identify the controls? There is a also a special dialect for wdi5.

Hello @Siolto

I have tried to use selector was provided by Test Recorder, but It didn't help me

@vobu
Copy link
Contributor

vobu commented Apr 6, 2023

as a prerequisite before we start digging deeper, please also update wdi5 to its' latest version - you're still running a pre^1 version, many improvements went in since then.

@MikhailDryk
Copy link
Author

Hello @vobu

I updated version of wdio-ui5-service to the 1.3.2
image

Without any success

@Siolto
Copy link
Collaborator

Siolto commented Apr 11, 2023

As discussed with @MikhailDryk: Most of his issues will be solved when #355 is resolved. Some other problems with identifying specific controls require more analysis.

@github-actions
Copy link

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

@github-actions github-actions bot added the stale label May 12, 2023
@github-actions
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants