Passing the selector from the config file, But when the bot taking it from config if there is any spaces in the selector it is getting filled by some special characters like &%ab0, is there any solution for this ??
Why are you passing an entire selector from a config file? Usually there is no need to do that. Show us what you’re doing and why.
@postwick
Yes, This is not necessary.
In some of my activities I’m using idx in selectors, while Analyzing the file it shows idx used selectors as error warnings, So in order to eliminate this warnings, I’m getting those selectors from the config.
Getting selectors from the config file isn’t how you solve anything. It just hides the warning because it can’t directly parse the selector. If your selector works, ignore the warning. However, it’s good to edit your selectors to avoid idx if possible. Sometimes, depending upon the app/page, it’s not possible to get rid of the idx.
2 Likes
Hello @Praveen_Vs
Here you can use the ui explorer and inspect on the elements which are failing. Identify the dynamic attributes in the selector and replace the value of it with wildcard or remove that attribute and validate it in ui explorer.
Getting the selector from config is not a good practice.
1 Like
Nothing is failing. He’s just seeing the analyzer warning about idx properties in selectors and thought that moving the selector to config fixed it.
1 Like