I searched and tried several things, namely this thread:
How to test WPF user interface?
I tried to get started with Systems.Windows.Automation and TestAutomationFX (third-party tool). My opinion is that, despite being useful for simple things, a type of bomb is like TestAutomation, when it goes beyond several levels of the user interface (user control inside user control from a loaded assembly), and I may have to manually tweak their code to get what i want. System.Windows.Automation seems old, and I will have to do everything manually, which may take more time than I want to devote, since I am not fully in creating automation. I also downloaded Inspect.exe from the Windows SDK for Windows 7, which is great for displaying objects in my user interface. Both testers work fine for the simple code behind,but then when he gets a few layers down, it seems a little connected. I was also going to try "TestStack / White" on GitHub, which had migrated from the original White project.
I was curious if anyone had any recent experience in UI automation that a non-developer could use in a QA position. I was thinking about getting the VS 2013 Test Pro, but this seems like over-growth and more expense than the VS 2013 Pro from what I could see. Basically this is not load testing or a complex complex dynamic entity that changes, just a function check, I hope ten or so different variables. This is just a more confusing layout as we combine the Prism method, Microsoft.Practices.Prism, with MVVM.
I am not against developing something in VS 2013 and .NET 4.5, but I was hoping to get something for which I am not developing a number of other projects, but to save time. I am an extreme noob in unit testing projects, but the end goal is really:
- exe Click Once, WPF, Prism MVVM.
, - CSV, config , .
exe click config (Click Once , " " click once, ).
, , , , . , .NET- .NET # VS, ( VS).