Why all that bloating?
As I move along with the VS add-in of DevRiot, I started to look again at the built-in features of VS.
What a mess! To end up asking the user the same information that DevRiot directly asks, there is an endless sequence of menus, options!
Orcas is following the same path. Why does the user need to deal with code? Because it executes faster? Obviously not.
That automatic code generation just works with native types. After that is back to set/get methods to set objects ready to tests. Or play PrivateObject nesting game.
Does it provide GUI testing for PC or devices? Nope.
Does it analyze build trees or AST? Nope.
Again, it is a step forward but short. Otherwise people would not still be asking "why white-box testing is ignored"
Labels: .Net desktop, .Net_compact, .Net_desktop, add-in, DevRiot, efeKctive, gui_testing, QA_Automation, Software_process_improvement, unit_testing, visual_studio



0 Comments:
Post a Comment
Links to this post:
Create a Link
<< Home