You are writing a WPF application. I hope you are using the MVVM pattern. You can easily test the Model, ViewModel and services with something like xUnit.net. https://xunit.net
Writing tests for a view is a pain. As long as all your buttons are connected to the VM and you have no binding errors. UI logic belongs in the View. Business logic can be in the ViewModel or a business layer. How I have done it in the past. I wrote test for the business logic with automation such as xUnit. The UI I had to validate manually.
Is the WPF app View first or ViewModel first? Dependency Injection is very beneficial in the C# code base.
I have written small WPF apps that work both ways.
Good luck, Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Kurt Wendt Sent: Wednesday, October 29, 2025 2:35 PM To: profoxtech@leafe.com Subject: To TEST or Not to Test...
...that is the Dilemma!
And, yes - this is related to FoxPro - in regards to our current system conversion project of porting it to C#.
I just asked my IT guy here at work (who sits on the desk opposite mine) - what he knew about doing software testing. From what he has heard, in regards to doing Automated type testing - that's mainly for Web/Browser based apps. Since, he figures - it's not so easy to do testing automation of Desktop Apps.
So, I wanted to throw this out to the Hive Mind here. Is there actually tools that allow one to do automated testing for Desktop apps? And, if so - is any of that a kind of open-source thing? Cause - I really don't think the co. where I work would actually pay for testing automation tools.
Anyway - that's it for now...
L8r G8rs, -K [excessive quoting removed by server]