Introduction to TestApi – Part 1: Input Injection APIs

re: Introduction to TestApi – Part 1: Input Injection APIs

thetpaing — Mon, 04 Apr 2011 07:23:42 GMT

my test program is not wpf. it is normal window

i have error in

Mouse.MoveTo(closeButton.GetClickablePoint());

NonComVisibleBaseClass was detected

Message: A QueryInterface call was made requesting the class interface of COM visible managed class 'MS.Internal.AutomationProxies.WindowsButton'. However since this class derives from non COM visible class 'MS.Internal.AutomationProxies.ProxyHwnd', the QueryInterface call will fail. This is done to prevent the non COM visible base class from being constrained by the COM versioning rules.

how to solve this problem?

thanks.

re: Introduction to TestApi – Part 1: Input Injection APIs

ivom1 — Tue, 17 Aug 2010 00:24:37 GMT

@Neftali,

Sure! A lot of people these days talk about Model-View separation, using various different patterns (Model-View-Controller, Model-View-Presenter, Model-View-ViewModel, etc.) A central goal of these patterns is to create a system where the Views are not tightly coupled with the Model. This goal has several important implications and one of them is improved testability.

Imagine for example that you have an IM application. One way to test sending a message is by going through the UI. If you want to do that you will have to (programatically) navigate to the message textbox, type your message, navigate to the Send button, click on it, confirm somehow that your message has been successfully sent. You will have to invest in making the test you write robust so that you can handle different positions of the IM window, intermittent blocks such as another window obscuring your window, different languages and UI positioning, different display resolutions, possibly different OS-es, etc. Some of these will be bona-fide factors you need to include in your test matrix. Others would just be robustness considerations (let's call this "robustness tax"). Now, in order to test your IM message sending functionality completely, you'd have to roll out quite a few variations of the same test -- with different message sizes, languages, etc. You'd have to pay this robustness tax in every one of these variations, which can quickly turn into a maintenance nightmare.

What if you had a way to only test the UI in isolation (without actually sending messages) and only test the message sending functionality (in isolation) without having to deal with UI. Well, this is where Model-View separation comes in handy. Talking to your model without going through the UI is a lot more robust, fast and targeted (it's a method call, not combination of UI interractions AND function call) -- you can easily test for a lot of different scenarios that have nothing to do with UI but are potentially bug-prone on the backend. So clearly - a win, if you can pull that off.

Hope that elaboration makes sense.

Ivo

re: Introduction to TestApi – Part 1: Input Injection APIs

Neftali — Sun, 15 Aug 2010 17:31:35 GMT

Can you elaborate on what you mean by "UI testing is tricky and should be avoided whenever possible. It’s always preferable to design your application as a multi-tier application, with a “thin” UI layer, so that you can bypass the UI in most of your tests." ??

Announcing WPF TestAPI 0.2 release | Coded Style

Announcing WPF TestAPI 0.2 release | Coded Style — Tue, 05 May 2009 08:28:45 GMT

PingBack from http://www.codedstyle.com/announcing-wpf-testapi-02-release-16/

Announcing WPF TestAPI 0.2 release | Coded Style

Announcing WPF TestAPI 0.2 release | Coded Style — Tue, 05 May 2009 08:28:29 GMT

PingBack from http://www.codedstyle.com/announcing-wpf-testapi-02-release-15/

Announcing WPF TestAPI 0.2 release | Coded Style

Announcing WPF TestAPI 0.2 release | Coded Style — Tue, 05 May 2009 08:28:20 GMT

PingBack from http://www.codedstyle.com/announcing-wpf-testapi-02-release-14/

Announcing WPF TestAPI 0.2 release | Coded Style

Announcing WPF TestAPI 0.2 release | Coded Style — Tue, 05 May 2009 08:27:26 GMT

PingBack from http://www.codedstyle.com/announcing-wpf-testapi-02-release-9/

Announcing WPF TestAPI 0.2 release | Coded Style

Announcing WPF TestAPI 0.2 release | Coded Style — Tue, 05 May 2009 08:27:19 GMT

PingBack from http://www.codedstyle.com/announcing-wpf-testapi-02-release-8/

Announcing WPF TestAPI 0.2 release | Coded Style

Announcing WPF TestAPI 0.2 release | Coded Style — Tue, 05 May 2009 08:26:27 GMT

PingBack from http://www.codedstyle.com/announcing-wpf-testapi-02-release-2/

Announcing WPF TestAPI 0.2 release | Coded Style

Announcing WPF TestAPI 0.2 release | Coded Style — Tue, 05 May 2009 08:26:17 GMT

PingBack from http://www.codedstyle.com/announcing-wpf-testapi-02-release/