Further to this.
problem solved.
The steps to make it work are:
1. during recording, click to open the drop down menu, then use the "Point and press the shortcut (Shift + Ctrl + A)" checkpoint to get to/open the drop down menu.
Cheers.
A checkpoint is a check point, not a player of actions. It checks for a state/value of something.
If you want to check for your dropdown menu you can :
- check the class of the element, allow to check without clicking, but this method is close on underlying dev and not focus on ihm so if the tested object is under development, it's risky.
- do the click action before the check.
Web or not web ? Keyword or scripting ?
Hey,
It's a Keyword test for a GUI based application.
Maybe I am failing to understand the aim purpose of the "Point and press the shortcut (Shift + Ctrl + A)" checkpoint. During recording I perform all the necessary actions to get to/open the menu I want to make the comparison, I then press the Shift + Ctrl + A to indicate it is that particular menu. I was expecting TestComplete during replay to repeat those actions and get to the menu to make the comparison.
Isn't that the main point of the "Point and press the shortcut (Shift + Ctrl + A)" functionality?
The "Select window region" checkpoint couldn't be used in this case because the dropdown menu collapses when the user clicks away from the GUI.
What are the main use case difference(s) between the two checkpoints?
Cheers.
Further to this.
problem solved.
The steps to make it work are:
1. during recording, click to open the drop down menu, then use the "Point and press the shortcut (Shift + Ctrl + A)" checkpoint to get to/open the drop down menu.
Cheers.
Yes, was that i said 😉
The Point and shift method is only a secondary method to use to select object to inspect when they appears/disappears at any input (click, keys). Dropdown menu are typically on this case.
