Steve
Top achievements
Rank 1
Iron
Rank 1
Iron
Sorry,
I'm having trouble getting TTS to capture an input field. It was working earlier exactly as it should. I was thinking that I did something to the Element Repository.
Do you have any documentation about modularity of tests?
Hi Steve,
I am sorry to know you are having troubles with an element in Test Studio.
I guess that something went wrong with your post, though, as there is no text left in it. Can you, please, elaborate on the issue you are facing?
Regards,
Elena
Hello Steve,
Thank you for sharing some insight about the encountered issue.
Can you, please, describe what happens when you try to record text type action against the input element? Do you see a step added in Test Studio?
What happens if you highlight the element and find in the DOM explorer - is it defined in the html as an input? If you choose the option to add this element to the Elements repository, what is the find expression generated for this element?
What happens if try to manually add a step against this element by following the below steps:
1. Open a test in Test Studio.
2. Select the newly added element in the Elements Explorer.
3. Switch the view to the Step Builder pane - depending on the layout you use this pane can be located on different place in your Test Studio.
4. In the Step Builder select the Actions section. A list of actions appears on the right side of the pane.
5. Under Quick Actions you can find the Enter text option. This will add the step you need.
Then you can execute the test with this step and let me know if this works. I will also appreciate if you share further details on the recording experience you observe and what is the outcome of executing the recorded steps.
Thank you for your time once again. Looking forward to hearing back from you.
Regards,
Elena
First, I should probably clarify that the two inputs are from a datepicker control (not Kendo). The start date input is also being used with an id.
1. After adding them, they do show as inputs. One has tagname and id, the other is tagname and tagindex. I was able to get the DateEndText added and running in a test.
3. The start date, however, has a dynamic id on it that can not be removed. So, every time it loads a new element is generated such as:
Dp1623778329612Text
Where the numeric part is different every time. I dont know what to do about that.
Thanks,
Steve
I'm still having no luck getting fields to show in a recording. Even after the Step Builder procedure. So I am unable to give you any execution details. Am I wrong thinking that there is a linking problem between the recorder and the Elements explorer?
Steve
Hi Steve,
The elements in Test Studio are being identified on the page with their find expression. If you open the element in Edit mode, which can be both during a recording session, or without such, you can see what attributes of the element on page are used to locate it.
If the element find expression is using a dynamic attribute in its find expression - like the id, for example, it will not be found next time the application is loaded. The same can be valid if using the TagIndex, but this depends on the application structure. In general, we do not recommend to use the TagIndex.
So, based on the shared details, it seems you will need to modify the find expression - the id can use only the static part and contains for comparison. Also you can use in the find expression any other attributes of the element, including any custom for the element and page.
The basic concept when choosing which attributes to include in the find expression is to use static and unique attributes, or set of attributes, for the element.
I hope this will help you to understand how the elements are used in Test Studio.
Let me know in case of further questions.
Regards,
Elena