Is UI Automation really a good choice for the WPF application testing? -


when talking automating ui tests conversation ends ui automation. option?

i don't 1 main reason - complexity. designed universal types of applications. such universality never comes free. uia introduces layer of abstraction , rather complicated api. standard patterns limited. custom controls support requires lot of coding. wonder why considers option?

wpf has brilliant , rich abstraction ui hierarchical tree of visual elements. these elements expose lots of methods, events , properties. tree supports various ways of referring (relative source syntax instance). , loose might in uia. what? compatibility old-school apps , web? well, realistically, need that? jack of trades master of none.

tools snoop can inject running application , full control on it. can change values of control properties , raise events. won't enough? nope. you'd want test interact ui user - using mouse , keyboard. that's problem can solved.

so wonder, there don't joy of uia?


Comments

Popular posts from this blog

get url and add instance to a model with prefilled foreign key :django admin -

android - Keyboard hides my half of edit-text and button below it even in scroll view -

css - Make div keyboard-scrollable in jQuery Mobile? -