Contributions
Parameterizing Property Checkpoints in keyword test
In "Keyword test" i want to use a parameter for a "Property Checkpoint". Here you can find the instructions: https://support.smartbear.com/testcomplete/docs/testing-with/checkpoints/property/parameterizing.html#KDT (Step 2.) According to the documentation it should work. But I don't get an [...]-option under "Values". When I double click on the cell, only the "Edit Property Checkpoint" window opens, which does not give me the possibility to set a parameter, only a hard-coded value. Is there a solution to this?Solved1.8KViews0likes5CommentsRe: Capture objekt tree structure of elements that disappear
I do not use keyword testing. The contents of the context menu are dynamic and the parameters are passed dynamically to a function, which then identifies and addresses the element using FindChild or FindAllChildren. I'm looking for exactly the parent element, but the information is inconsistent. I'm not looking for a workaround, because this was just an example for better understanding. The requirement is: If I have an object, I want to be able to uniquely identify its parent element and its exact position in the object tree. This is not a problem with objects that remain on the sceen, but with objects that disappear when you switch to Testcomplete or Object spy. In my example I want to use 'TestObj.FindChild(PropNames, PropValues, Depth, RefreshTree)' with as little depth as possible. If 'TestObj' is the direct parent then 'Depth' can be '1'. But because of the inconsistency of the information and the inaccessibility of the object tree it is difficult to find out who the parent element is. (Object spy says one thing, mapping another thing and Object Tree says nothing.) In this example, the (sub) context menu on the right side is not a child of the context menu on the left side. Then it would be easy.2.1KViews0likes2CommentsRe: Capture objekt tree structure of elements that disappear
This is my object on the screen: This is Object Spy with Ctrl+Shift+A on this object: 'Aliases' and 'FullName' say that 'Popup("Rahmen") is the parent element. Now I click on 'parent' -> '[...]. But there are no information. Ok, then I map the object: Right click -> Map object... And this is the result in the Mapped Objects. The Object is placed under a new "Item". But it was supposed to be the child of "Rahmen"? This inconsistency of information is a problem at work. Precisely because the tree structure cannot be seen. This would not be a major problem if you could view the object tree, even if the object no longer exists on the screen. Keyword: Snapshot of object tree. Edit: The button at the top right "Highlight Object in Object tree" (window object spy) gives me the error message, that the object doesn't exist.2.1KViews0likes5CommentsRe: Capture objekt tree structure of elements that disappear
NewEnum contains the child elements, if available. And the procedure has little to do with an understandable object tree structure. I have an object and do not know where it is in the tree. Who are its parents, grandparents? I do not know. But there are hundreds of elements in my app object tree. I need the parent of a object and I can't go the way from any parent element to child elements because my target object doesn't exist when I use the object spy or other windows. I have a context menu and wants to know who is the parent element of "Rahmen hinzufügen". Is it "Rahmen", app main windows or a completely different object? Everything is possible. The object spy gives different information. - Aliases says: Popup("frame") - FullName says: "Popup("frame") - Parent -> [...]: is empty And when I map the object, an "Item" is inserted in the name mapping tree. This is a lot of different information and none of it leads to a working solution. I would just use 'Highlight Object in Object tree', but: The question is, who is the real parent of my object and how can I easily find out?2.1KViews0likes7CommentsCapture objekt tree structure of elements that disappear
How can I capture properties and objekt tree structure of elements that disappear when clicking in object spy or testcomplete? The tested app uses custom context menus. These can be captured with object spy (Ctrl+Shift+A). But, when I want to view the object tree structure, it is not available, because the context menus disappears as far as you click into the object spy or other window (""Unable to hightlight this object in the object tree, because it does not exist."). The Context menus are only available until you click outside of them. The context menus with submenus look like parents and children on the screen, but are not in the object structure. My goal was to access the objects via FindChild and FindAllChildren (The values of the properties should be passed dynamically to a function via parameters. Therefore, name mapping is not an option here.). To make this work faster, I wanted to study the object structure. This way I could better understand the structure and relationships of the objects. But that didn't work. Other tools can take a snapshot of the object structure or at least show the object structure further (for example Inspect.exe or Appium). So you can view the structure (and properties) of the elements, even if the elements and structure are no longer exist on screen. With TestComplete, however, this information are only available as long as the element is present on the screen. As a quick solution I wrote my own function (Recursive loop, FindAllChildren, etc.) that automatically captures all elements on the screen and writes the structure in an XML-like file. So I got what I need. But it's very slow and inconvenient. I would assume that Testcomplete could do something basic like that natively and I just didn't find it. How can I do that? PS: I work with script test cases and Python.Solved2.1KViews0likes9Comments