WPF elements in ObjectBrowser
I see that not all the layers that are availabe for a WPF application are displayed in Test Complete, Object Browser. I attach two screen captures, one from TestComplete and one from Snoop. ...
Forum Discussion
Hi Andrei,
Sorry for the confusion. Snoop shows a more detailed object tree than TestComplete indeed, but that's because it also shows some low-level drawing primitives. Let me explain this by an example.
WPF UI elements are complex and consist of other objects. For example, a simple button:
The component objects are used just to draw the button on screen. The users cannot actually interact with them.
Snoop is a tool mostly for developers. It shows all the objects including the drawing primitives, because they can be useful for debugging.
TestComplete, on the other hand, is a test automation tool. It filters out low-level drawing objects that aren't relevant for GUI automation to make the test object model simpler. To check an object's appearance, you can always use the object's own properties rather than work directly with the drawing primitives.
Hope this answers your question. Let me know if you need any clarification.
Sorry for the confusion. Snoop shows a more detailed object tree than TestComplete indeed, but that's because it also shows some low-level drawing primitives. Let me explain this by an example.
WPF UI elements are complex and consist of other objects. For example, a simple button:
consists of 4 objects:
<!-- XAML -->
<Button>Click me!</Button>
Button
|_ ButtonChrome
|_ ContentPresenter
|_ TextBlock
The component objects are used just to draw the button on screen. The users cannot actually interact with them.
Snoop is a tool mostly for developers. It shows all the objects including the drawing primitives, because they can be useful for debugging.
TestComplete, on the other hand, is a test automation tool. It filters out low-level drawing objects that aren't relevant for GUI automation to make the test object model simpler. To check an object's appearance, you can always use the object's own properties rather than work directly with the drawing primitives.
Hope this answers your question. Let me know if you need any clarification.
