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

[Need support]: New element locator have not been found. There is a lack of reference data. #76

Open
AdarshSingh003 opened this issue Aug 9, 2023 · 6 comments
Assignees
Labels
help wanted Extra attention is needed

Comments

@AdarshSingh003
Copy link

Describe the problem

I ran the pure tests first and made changes to element id and ran the tests again, unfortunately tests are failed. When i took a look at the proxy logs i noticed following log.

WARN 3940 --- [nio-8085-exec-4] c.e.h.processor.HealingProcessor : New element locator have not been found. There is a lack of reference data.

Also Wheni check in my postgres Selector table no locator is updated before and after the pure as well as healening script. and also need help how we can select hlm backend and hlm web version

Healenium Web version

3.2.5

Healenium Backend version

3.2.2

Selenium version

4.6.0

Platform

java

Logs appeared during using Healenium

New element locator have not been found. There is a lack of reference data.

Additional context

No response

@AdarshSingh003 AdarshSingh003 added the help wanted Extra attention is needed label Aug 9, 2023
@Alex-Reif
Copy link
Contributor

Hello @AdarshSingh003 , Firs off check our FAQ. We describe here root cause.
Could you clarify, do you use hlm-web or hlm-proxy approach?
We released new version, try to reproduce on actual version hlm-web:3.4.4 or hlm-proxy:1.3.5

@adarsh12308
Copy link

Hello @Alex-Reif I am using hlm-web approch

@kherath17
Copy link

kherath17 commented Nov 10, 2023

Hi @adarsh12308 were you able to resolve this issue?

@Alex-Reif @ElenaStepuro I'm also facing a similar issue, even though the db has the selector value successfully stored it doesn't heal or even attempt to heal

Proxy Log:

2023-11-09 13:30:15.748 WARN 1 - [8085-exec-8] healenium : New element locators have not been found.\n Score property = 0.7 is bigger than healing's locator score

I even set the score property to 0.1, still not healing.

@adarsh12308
Copy link

Hello @kherath17 you can use the selfhealedriver for run the pure test and then after that you can run the another test

@Alex-Reif I have successfully healed the locators but got issue in report it is empty every time I am using healenium-web version 3.4.2 selenium version 4.8.0 hlm-backend version 3.3.2 and immitator version is 1.2 can you help me to resolve it

@kherath17
Copy link

Hi @adarsh12308 can you please elaborate more? " selfhealedriver for run the pure test and then after that you can run the another test "

@adarsh12308
Copy link

adarsh12308 commented Nov 10, 2023

Hi @kherath17 The driver which you use to find the locator use that driver for the first time when the locators are found so that it can store it to the postgresql table then you can change the locators from your end and run you test again so it can heal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants