4 Answers, 1 is accepted
Thank you for your question.
Please find in the available documentation articles on how to locate DOM elements in a coded step. There are certain find expressions that you might find useful as well. There are a DOM navigation samples available too. I believe you could find further more interesting samples in the product documentation and in the forums related to the topic you are interested in.
I hope this information is helpful.
Thanks for your response.. I have gone through the documentations. But still unable to solve my problem.
I have a HTML5 application - My Requirement is to write some text in the Input Text Box which is a Dropdown.
Steps Followed :
Name - (This is a Text box which has a dropdown of list of names) - I need to Search a particular name(eg:xxx) by typing in the Text box.
=> I Highlighted the Element (Name) by using the recorder, and added to my Test step.
=> The Recorded element consists of id and tagindex in the find settings
"id and Tag index "
=> When I Right click - Edit in Live - It says "Unable to find out the Element"
=> I changed the find settings using
"Class and Tagname" - I am able to find the element.
=> But when I run the step separately, it get passed. When I run it in the Test, it failed...
Could you please clarify the below questions
1. What are the components (eg : id, tagname, tagindex, class) should I use to find out the correct element
2. Why the step is failing when run in a test ?
Generally speaking if the element has an ID - it is always best property to use in the find logic. If the element does not have one there a two approaches here:
- to find a set of properties that uniquely describe the element
- to create a chained find logic using the closes to this element that has an ID
There is an exception message that indicates the reason for the step failure that you could check in the execution log after the test completes.
I hope these pointers are useful to you.