Forum Discussion
Based upon the screenshots, I'm assuming that what you're noting as "unusual" is that the test log says a particular item was selected but the visualizer shows something else happening (clicking on a different item).
What's not clear is:
1) When you look at the application after the clickitem is executed, what is actually selected? Is the correct one selected or is the wrong one selected? In other words, is the unusual behavior simply that visualizer doesn't look right or is it that the item expected is not actually being selected.
2) What type of ddl is this? Is this a particular kind of component? It would be helpful to know more about the component being operated against in case there are some known tips/tricks to work with.
I wanted to select Australian Medical Council it points to it but highlights other record and select the other institution, which is not intended. Please suggest
and for the ddl
- tristaanogre7 years agoEsteemed Contributor
Can you screenshot the properties and methods of that component? I know you're using "ClickItem" but there may be something else going on that we need to handle better. What class of DDL is it? What component type? Teleric? AngularJS? Anything you can give us to understand better the component type will go a long way. A screenshot of how it is rendered in the web browser doesn't help us help you.
- tsan1237 years agoOccasional Contributor
Screen shot of the Properties is attached , im using ClickItem the class aspNet. hope attachment helps
- tristaanogre7 years agoEsteemed Contributor
OK... I think I see something interesting.
It appears that the DDL is populated based upon the selected country, correct? So, once you select the country, there is a bit of a processing delay before the CountryCBO drop down is populated. What you may be dealing with is an issue of timing. What I would do is see if there is a way to detect when that population of data is complete... perhaps a "WaitProperty" call on the DDL to see if wItemCount matches the number of records for Australia. Once wItemCount hits that value, then try your clickItem call.
Not guarenteeing this will fix it, but it seems to be, at least, a good thing to try.