Thanks for the additional details.
You are correct that entering text in this Kendo dropdown control is also possible - I manage to record such step and it selected the respective item. I am not sure how you tried to record the step on your end, but the dropdown should be opened (or toggled) when entering the text - this is how it got recorded on my end. Also the target element of this step was the span, which represents the dropdown - in other words, the Kendoinput Toggle
step and the KendoInputValue 'Grey'
step are using the same element. As far as I could see from the shared details, the step you added manually is targeting another element and therefore the test is failing.
Anyways, before you go for that option, I would like to point you to some other features, which Test Studio provides as an alternative to cover this scenario. You mentioned that you need to data drive the item to select from the dropdown list to avoid adding multiple elements to the Elements repository. For such cases Test Studio allows you to data drive the find expression of an element
- in this case this should be the item to select from the list. The recorded find expression uses tagName and TextContent of the item, so you can data drive the text content to point to the different items in the list.
I have prepared a sample test for you to demonstrate this data binding and you can find it attached to this reply. You can add it as an existing test in the project and review how this is set - it uses local data for the data binding, its last two steps are disabled as they represent the scenario with entering text, but these may not be required.
I hope this will be helpful for you to tailor up the most appropriate solution to cover the requirements. Of course, in case of any questions, please do not hesitate to get back to me.